Authenticate securely using tokens and OAuth to control access to contacts, tasks, notes, and appointments.
Your app should securely store credentials and rotate tokens to maintain a safe connection to the 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; contacts.write; 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: user opens a contact profile in your app
Actions: fetch the contact, load related tasks, and display status in the UI
Method/Path: GET /contacts/:contactId
Key fields: contactId, name, email
Trigger: new contact is created in the app
Actions: POST /contacts/ to create, then POST /contacts/:contactId/tags to apply tags
Method/Path: POST /contacts/ and POST /contacts/:contactId/tags
Key fields: contactId, tags
Trigger: contact information changes in the app
Actions: PUT /contacts/:contactId, PUT /contacts/:contactId/tasks/:taskId
Method/Path: PUT /contacts/:contactId
Key fields: contactId, updated fields
No-code connectors let you build and iterate quickly without traditional development cycles.
Centralized access to contacts, tasks, notes, and appointments across tools.
Automations and triggers scale across endpoints to save time.
Data elements and processes covered: contacts, tasks, notes, appointments, and tags; how they relate and flow in the API.
An individual in your CRM with identifiers like name and email.
A to-do item linked to a contact with status and due date.
A brief piece of information attached to a contact.
A specific URL path used to interact with the API.
Capture leads and create contacts, then pull related tasks to guide onboarding.
When a task is updated, push changes to your app to keep users informed.
Attach notes from support chats to contacts for a complete history.
Generate and securely store your API token for authentication.
Choose endpoints like GET /contacts and POST /contacts/ to start.
Create triggers and actions to automate workflows between your app and the API.
Most integrations can be used with minimal code using tokens. Start by generating an API token, then use the listed endpoints to perform read or write actions. If you’re new to APIs, consider using a no-code connector to map fields and build simple automations. Always follow security best practices when storing credentials.
Authentication typically uses tokens or OAuth depending on the setup. Tokens are convenient for server-to-server calls, while OAuth is common for user-based access. Ensure tokens are stored securely and rotated regularly.
API rate limits vary by plan. To avoid throttling, spread requests, queue heavy operations, and cache frequent lookups. Use webhooks where possible to receive updates instead of polling.
You can delete contacts via the API with DELETE /contacts/:contactId. Some platforms support soft delete or archiving; check your API docs for behavior and recovery options.
To fetch a contact’s tasks, call GET /contacts/:contactId/tasks. You can filter by status or due date to organize onboarding or project work.
Yes—use POST /contacts/:contactId/notes to add notes. You can also attach notes in bulk using batch endpoints if available.
Apply tags with POST /contacts/:contactId/tags. You can pass an array of tags to categorize contacts quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
