The Contacts API uses OAuth 2.0 tokens scoped to contacts.readonly to securely access contact data from your apps.
Connect securely with OAuth 2.0 or API keys to authorize Zapier automations with the Contacts API.
GET /contacts/:contactId — Retrieve a single contact GET /contacts/:contactId/tasks — List tasks for a contact GET /contacts/:contactId/tasks/:taskId — Retrieve a specific task GET /contacts/:contactId/notes — List notes for a contact GET /contacts/:contactId/notes/:id — Retrieve a note GET /contacts/:contactId/appointments — List appointments for a contact GET /contacts/ — List contacts GET /contacts/business/:businessId — List contacts by business API Endpoint9: contacts.write API Endpoint10: POST /contacts/ API Endpoint11: PUT /contacts/:contactId API Endpoint12: DELETE /contacts/:contactId API Endpoint13: POST /contacts/:contactId/tasks API Endpoint14: PUT /contacts/:contactId/tasks/:taskId API Endpoint15: PUT /contacts/:contactId/tasks/:taskId/completed API Endpoint16: DELETE /contacts/:contactId/tasks/:taskId API Endpoint17: POST /contacts/:contactId/tags
Trigger when you need to pull details for a specific contact by ID
Actions: Retrieve contact data and map fields to destination apps
GET /contacts/:contactId
Required: contactId; Optional: include related data via query
Trigger to fetch all tasks for a contact
Actions: Create, read, or update tasks associated with a contact
GET /contacts/:contactId/tasks
Required: contactId; Optional: taskId to fetch a single task
Trigger to retrieve a particular task by ID
Actions: Retrieve, update task status, or mark complete
GET /contacts/:contactId/tasks/:taskId
Required: contactId and taskId
Automate data flow without writing a line of code
Keep data in sync across tools in real time
Reduce manual entry and human error
Core concepts and workflow steps for connecting the Contacts API with the Zapier App Connector
A person in your CRM with fields such as name, email, and phone
A specific URL you call to access or modify data in the API
A set of rules and methods that allow apps to communicate with the service
An authorization framework that grants access tokens for secure API calls
Capture form submissions and automatically create contacts in the CRM via the API
Create and assign tasks when contact status changes or a trigger fires
Keep notes in sync across tools to maintain a complete contact history
Grant access to Contacts API and the Zapier App Connector and verify credentials
Map events to actions and set data fields for seamless automation
Run tests, review mappings, and enable automation for production
Using the Zapier App Connector, you can build automations without writing code. No coding is required to connect the Contacts API to your apps and map fields using a visual editor. Set up authentication once, choose triggers, and configure actions to move data between platforms. The interface guides you step by step so non developers can automate workflows quickly.
The Contacts API exposes core data such as contact details, tasks, notes, and appointments. You can fetch a single contact, list related tasks, notes, and appointments, or pull an entire set of contacts for a business. Use filters and field mappings in Zapier to tailor the data you bring into each app and keep your workflows clean and efficient.
Connections use OAuth 2.0 tokens transmitted over TLS to protect data in transit. Tokens are scoped to the Contacts API with the required permissions and can be rotated securely. For best security, store credentials safely, enable automatic token refresh, and monitor access logs for unusual activity.
Yes, you can filter results by business or endpoint using the provided endpoints such as GET /contacts/business/:businessId. You can also scope data with query parameters where supported. This allows you to segment data for specific workflows, teams, or clients while keeping API calls efficient.
Common errors include authentication failures, missing required parameters, and rate limit hits. Zapier will retry transient errors automatically according to your settings. Implement robust error handling with clear field mappings and keep your credentials up to date to minimize failures.
Rate limits depend on your plan and usage. In general, expect a balance between read and write operations with automatic retries for transient limits. For high-volume needs, consider batching requests or scheduling triggers to spread calls over time.
Yes, the DELETE /contacts/:contactId endpoint allows you to remove a contact. Use with caution and ensure you have proper backups or archival processes. When deleting, consider preserving a record or tag to indicate historical data for auditing purposes.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
