Use OAuth 2.0 tokens to authorize requests from Dub to the Contacts API. Securely store credentials and rotate keys regularly.
Dub authenticates with the Contacts API using token-based authentication. Keep tokens secret and request only the scopes you need (contacts.readonly).
GET /contacts/:contactId\nGET /contacts/:contactId/tasks\nGET /contacts/:contactId/tasks/:taskId\nGET /contacts/:contactId/notes\nGET /contacts/:contactId/notes/:id\nGET /contacts/:contactId/appointments\nGET /contacts/\nGET /contacts/business/:businessId\ncontacts.write\nPOST /contacts/\nPUT /contacts/:contactId\nDELETE /contacts/:contactId\nPOST /contacts/:contactId/tasks\nPUT /contacts/:contactId/tasks/:taskId\nPUT /contacts/:contactId/tasks/:taskId/completed\nDELETE /contacts/:contactId/tasks/:taskId\nPOST /contacts/:contactId/tags
Trigger: when a new or updated contact is detected in the Contacts API.
Actions: pull full contact details into Dub and map core fields (name, email, phone, etc.).
GET /contacts/:contactId
contactId, firstName, lastName, email, phone
Trigger: updates to a contact’s tasks in the Contacts API.
Actions: create or update tasks in Dub when tasks change.
GET /contacts/:contactId/tasks
taskId, status, title, dueDate
Trigger: new or updated notes on a contact.
Actions: attach notes to contact in Dub.
GET /contacts/:contactId/notes
noteId, content, createdAt
Create automated workflows without writing code.
Sync data in real-time across your CRM and applications.
Reduce manual data entry and errors with automated mappings.
A quick glossary of terms you’ll see when integrating the Contacts API with Dub.
A person stored in your Contacts database with associated records like notes, tasks, and appointments.
A specific URL path and HTTP method used to access a resource in an API.
The process of proving identity to access an API, typically via OAuth tokens or API keys.
A means for an API to send real-time data to another app via HTTP callbacks.
Automatically create contacts in Dub when a new contact is added via the API.
Trigger reminders in Dub when a contact’s tasks are due.
Sync notes with contact history to surface insights in Dub.
Obtain OAuth tokens for the Contacts API and grant Dub the necessary scope.
Select relevant endpoints (e.g., contact, tasks, notes) and map fields.
Test flows in your Zapier connector, then enable automatic syncing.
To connect Dub to the Contacts API, you will need credentials that authorize Dub to access your Contacts data. This typically means setting up OAuth 2.0 tokens or an API key with the required scope (e.g., contacts.readonly). Store these credentials securely and rotate them regularly. Ensure your app has permission to read contact details, tasks, and notes as needed for your workflows.\nIf you are using OAuth, you will authorize the Dub app once and then manage token refreshes automatically to keep connections active without manual re-authentication.
For a basic sync, enable endpoints that cover contacts, tasks, and notes: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes. Map essential fields such as contactId, name, email, task status, and note content. This provides a core data loop between the Contacts API and Dub without overcomplicating your setup.\nAs you scale, you can add appointments and tags as needed.
Token rotation is typically handled by your auth provider. In Zapier/Dub integrations, enable automatic token refresh if available. Keep your refresh tokens secure and implement automated alerts if a token is near expiry. Document token lifecycle policies for your team and ensure fallback procedures in case of authentication failures.\nRegularly audit scopes to ensure only required permissions are granted.
Real-time syncing is supported depending on the endpoint and your app configuration. Webhook-based notifications can help trigger updates in Dub as soon as changes occur, but some endpoints may rely on polling. Plan your workflow to balance immediacy with API rate limits.\nTest thoroughly to confirm timing and data consistency across systems.
Example payloads for mapping vary by endpoint. For a contact, you might map { contactId, firstName, lastName, email, phone }. For tasks, map { taskId, subject, status, dueDate }. Check the official API reference for sample responses and tailor your field maps to your automation needs.\nUse test data to validate your mappings before going live.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
