Use your API credentials (OAuth or token-based) to securely authorize Horoshop to read and manage contact data within the Contacts API.
In Horoshop, configure API credentials and grant scoped access (read-only by default) to connect to the Contacts API.
GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/tasks/:taskId, GET /contacts/:contactId/notes, GET /contacts/:contactId/notes/:id, GET /contacts/:contactId/appointments, GET /contacts/, GET /contacts/business/:businessId, POST /contacts/, PUT /contacts/:contactId, DELETE /contacts/:contactId, POST /contacts/:contactId/tasks, PUT /contacts/:contactId/tasks/:taskId, PUT /contacts/:contactId/tasks/:taskId/completed, DELETE /contacts/:contactId/tasks/:taskId, POST /contacts/:contactId/tags
Trigger: need to pull a contact’s details to personalize a message or workflow.
Actions: fetch contact data, display in dashboards, drive tasks or notes.
Method path: GET /contacts/:contactId
Key fields: contactId, name, email, phone, tags
Trigger: syncs tasks for a contact to keep teams aligned.
Actions: list tasks, update status, create new tasks.
Method path: GET /contacts/:contactId/tasks
Key fields: contactId, taskId, taskName, status, dueDate
Trigger: fetch notes for a contact to surface context.
Actions: pull notes, attach to records, search by id.
Method path: GET /contacts/:contactId/notes
Key fields: contactId, noteId, noteText, createdAt
Rapid setup with drag-and-drop workflows and zero code to unlock data-driven automations.
Unified data view: see contacts, tasks, notes, and appointments in one place.
Scalable integration that grows with your Horoshop use case and team.
Essential concepts and processes to understand how the Contacts API connects with Horoshop.
A person in the Contacts API with identifiers like contactId, name, email, and phone.
A to-do item linked to a contact, with status, due date, and related notes.
A text comment or attachment tied to a contact for context.
Scheduled meeting or call linked to a contact in the calendar.
Automatically tag and route new contacts to the right owner and workflow.
Pre-build task templates to accelerate follow-ups on contacts.
Use notes to trigger follow-up actions and context-rich automations.
Register your Horoshop app in the API portal and generate client credentials.
Grant read-only access or full permissions to cover your use cases, then authorize the app.
Run test requests and deploy the connection to your Horoshop workflows.
The Contacts API lets you access and manage contact records, tasks, notes, and appointments from Horoshop. It enables powerful automations and unified data views. Using secure authentication, your team can read or update contact data as needed.
No-code integration is possible with tools like Zapier, enabling Horoshop to connect to the Contacts API via pre-built connectors. You can configure triggers, actions, and data mapping without writing code.
Permissions are determined by the scopes granted during authorization (for example, contacts.readonly). Ensure your app has the appropriate scope to read (and optionally write) contact data.
To revoke access, disable the app in Horoshop or revoke the OAuth token in the API portal. Rotate credentials regularly to maintain security.
Real-time sync depends on the provider and plan. Webhooks or polling can keep Horoshop updated with changes to contacts, tasks, and notes.
Start with the endpoints you use most: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes.
API credentials are issued by your API provider. Visit the developer portal for Horoshop and follow the steps to create and manage credentials.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
