Use OAuth 2.0 with the required scope of contacts.readonly to obtain an access token that authorizes requests to the Contacts API.
During setup, authorize the app to access your Contacts data and store tokens securely for subsequent requests.
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: when a contact is created or updated in Contacts API to sync in Zapier.
Actions: create or update contact, add tasks, log notes.
Usage example: GET /contacts/:contactId and POST /contacts/ to manage the primary contact record.
Key fields: id, email, firstName, lastName, phone, ownerId, lastActivity.
Trigger: when a task is created or updated for a contact.
Actions: create update tasks, mark completed, assign due dates.
Paths: POST /contacts/:contactId/tasks; PUT /contacts/:contactId/tasks/:taskId; PUT /contacts/:contactId/tasks/:taskId/completed; GET /contacts/:contactId/tasks
Key fields: taskId, title, status, dueDate, priority.
Trigger: when notes are added or updated for a contact.
Actions: create notes, update notes, attach to contacts.
Paths: GET /contacts/:contactId/notes; GET /contacts/:contactId/notes/:id
Key fields: noteId, content, createdAt.
Fast setup with no code required.
Visual workflow builder reduces integration time.
Automations stay in sync across contacts, tasks, and notes.
This section defines the core data elements (contacts, tasks, notes) and the processes (auth, endpoints, triggers, actions) used by the integration.
A person in your CRM whose data is stored in Contacts API.
A to-do item associated with a contact.
A free-form text entry linked to a contact.
A URL route for a specific operation in the API.
Automatically create a new contact in Contacts API when a new lead arrives in Zapier App Connector with essential fields mapped.
Append call notes to existing contact entries to maintain a complete history.
Automatically create tasks from calendar events or tickets to ensure follow ups.
Grant access to Contacts API via OAuth and select the required scope (contacts.readonly).
Choose the endpoints you need (contacts, tasks, notes) and set triggers accordingly.
Run test in the app tester, verify data flows, then deploy to production.
The Contacts API scope controls what data you can read. In this integration we request contacts.readonly to retrieve contact data, tasks, and notes. If you need write access, adjust the scope to include write permissions and update the app settings accordingly. The app will securely store tokens and refresh them as needed.
Essential endpoints depend on your use case; for common needs start with GET /contacts/:contactId and GET /contacts/:contactId/tasks. You can extend with notes and appointments as required. This page also lists all available endpoints for reference.
Authenticate via OAuth 2.0 in APPNAME and authorize the Contacts API scope. The app stores access tokens securely and uses refresh tokens to maintain access without manual reauthorization.
Yes, you can create and update tasks using POST and PUT endpoints. Map these actions in APPNAME to attach tasks to the correct contact and update task status as work progresses.
Map fields like id, email, and name from Contacts API to corresponding APPNAME fields. Use Zapier’s mapping UI to align fields and ensure data flows correctly between systems.
Webhooks are supported to notify APPNAME of changes in Contacts API. Configure in the endpoint settings and subscribe to relevant events for real time updates.
The Endpoint List is available in the Endpoint section of this page. You can also view the full list in the API docs for detailed usage and examples.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
