Dex uses OAuth 2.0 token-based authentication. Acquire an access token with the scope ‘contacts.readonly’ to securely call the API.
Dex follows standard OAuth flows to obtain access tokens, refresh tokens, and to request the Contacts API scope required for operations.
– GET /contacts/:contactId — Retrieve a single contact and related data – 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 specific note – GET /contacts/:contactId/appointments — Retrieve a contact’s appointments – GET /contacts/ — List contacts – GET /contacts/business/:businessId — Retrieve contacts by business – contacts.write — Permission flag for write operations – POST /contacts/ — Create a new contact – PUT /contacts/:contactId — Update a contact – DELETE /contacts/:contactId — Delete a contact – POST /contacts/:contactId/tasks — Create a new task for a contact – PUT /contacts/:contactId/tasks/:taskId — Update a task – PUT /contacts/:contactId/tasks/:taskId/completed — Mark a task as completed – DELETE /contacts/:contactId/tasks/:taskId — Delete a task – POST /contacts/:contactId/tags — Add tags to a contact
Trigger: Retrieve a specific contact and pull related data (tasks, notes, appointments) on demand.
Actions: Get contact, fetch related tasks, notes, and appointments; optionally update contact fields as part of the workflow.
GET /contacts/:contactId
Key fields: contactId, fields to return, related data inclusion.
Trigger: New or updated contact detected in Dex through Zapier.
Actions: Create or update contacts, create tasks, add notes in Dex, and synchronize data across apps.
Multiple methods: GET /contacts/:contactId and POST /contacts/ to create new contacts.
Key fields: contactId, taskId, data payload for creates/updates.
Trigger: Webhook notifications when a contact record changes in Dex.
Actions: Update contact details, append notes, create related tasks, or tag the contact based on events.
POST /contacts/:contactId/tasks
Key fields: contactId, task details (title, dueDate, status).
Faster setup with drag-and-drop workflow builders and pre-built templates.
Low maintenance thanks to reusable components and ready-to-use data mappings.
Easily scale from prototype to production with robust error handling and logging.
A concise glossary of concepts you’ll encounter when connecting Dex to the Contacts API, including endpoints, authentication, and data fields.
A defined URL path used to perform a specific operation against the API.
The process of proving identity to obtain access tokens for API calls.
An authorization framework that issues access tokens to clients after proper authentication.
Limits on how many API requests can be made in a given time period to protect services.
Automatically generate follow-up tasks when a contact’s status changes, ensuring timely engagement.
Fetch recent notes and activity and append them to the contact profile for richer context.
Use webhooks to push updates to tasks and notes in real time across connected apps.
Obtain an access token for the Contacts API using Dex credentials and the proper scope.
Select the necessary endpoints (GET, POST, PUT, DELETE) and map data fields to Dex.
Test calls in a sandbox, review logs, and deploy to production with monitoring.
No extensive coding is required. Dex provides simple triggers, actions, and mappings to connect with the Contacts API. For advanced use cases, you can add custom scripts, but many common workflows can be built with no-code tools. Start with the basic GET and POST operations to fetch contacts and create tasks, then extend as needed.
Dex supports OAuth 2.0 token-based authentication using client credentials. You may also work with API keys if your setup requires them. Always scope to the minimal permissions needed (e.g., contacts.readonly) to enhance security. Refresh tokens are available to maintain long-running integrations without re-authentication.
Common endpoints include GET /contacts/:contactId for a contact, GET /contacts/:contactId/tasks for related tasks, and POST /contacts/:contactId/tasks to create new tasks. Notes, appointments, and tag management are also frequently used in workflows.
Yes. You can create tasks from Dex using POST /contacts/:contactId/tasks and associate notes or tags as needed. This enables task-driven follow-ups directly from contact records.
Yes. The API enforces rate limits to protect resources. Plan back-off strategies and implement retries with exponential backoff in your integration to handle limits gracefully.
You’ll find ready-to-use templates and example workflows in the Dex + Contacts API integration guide, plus community resources and sample requests for common use cases.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
