GHL uses token based authentication. In Dust configure an API token with the contacts.readonly scope to access read only data and upgrade scope if you need write access.
Dust securely stores your GHL access token and uses it to call endpoints on demand. Keep tokens confidential and rotate them regularly.
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 Dust to fetch current data and create or update tasks in GHL.
Actions: pull contact fields, create or update tasks, and update notes as needed to keep both systems in sync.
Key endpoints used: GET /contacts/:contactId, GET /contacts/:contactId/tasks, PUT /contacts/:contactId/tasks/:taskId
Core fields: contactId, taskId, noteId, businessId
Trigger: updates to a contact in Dust to apply or remove tags in GHL via POST /contacts/:contactId/tags
Actions: apply tags, read current tags, and adjust segmentation in Dust as needed.
Endpoints: POST /contacts/:contactId/tags, GET /contacts/:contactId
Key fields: contactId, tagId
Trigger: upcoming due dates for tasks or changes to a contact in Dust to schedule reminders in GHL.
Actions: create tasks with due dates via POST /contacts/:contactId/tasks and mark completion via PUT /contacts/:contactId/tasks/:taskId/completed.
Key endpoints: POST /contacts/:contactId/tasks, PUT /contacts/:contactId/tasks/:taskId/completed, GET /contacts/:contactId/tasks
Key fields: contactId, taskId
Faster rollout with ready to use endpoints and templates, no coding required.
Unified data between Dust and GHL reduces context switching and errors.
Better security with token based authentication and centralized access control.
This glossary explains API terms and how data flows between Dust and GHL using the endpoints listed.
A URL and HTTP method used to access or modify a resource in an API.
A URL that Dust or GHL can call to notify your system of an event.
A secure token based authorization protocol that grants Dust access to GHL resources on behalf of a user.
The set of permissions granted to the Dust app for a given token.
Trigger reminders and auto create tasks when a new or updated contact is detected in Dust.
Tag and group contacts by activity notes and recent interactions.
Maintain an audit trail of changes to contacts and tasks for compliance.
Generate and securely store your access token with the defined scope.
Use the listed endpoints to pull and push data between Dust and GHL.
Map contact fields like name, email, phone, tasks, and notes for seamless syncing.
The Dust to GHL Contacts API connection lets Dust access contact records, tasks, notes, and appointments in your GHL workspace. Use the endpoints listed to pull and push data and keep both systems in sync. This setup enables automated workflows without manual data entry.
The endpoints listed cover reading contacts, tasks, notes, and appointments as well as creating and updating contacts, tasks, and tags. If you need additional endpoints, you can map them in Dust or request access to broader scopes.
Authentication is token based. In Dust configure an API key or OAuth flow to obtain a token with the scope defined as contacts.readonly. Keep tokens secure and rotate them regularly; Dust handles token usage automatically for API calls.
The primary scope shown is contacts.readonly which allows read access. If write access is required for tasks or notes, broader scopes are needed and should be approved by your GHL administrator.
To test the connection, generate a token, connect the app in Dust, and run a few test calls against endpoints such as GET /contacts/:contactId. Look for successful responses and review any error messages in Dusts integration logs.
Yes. You can create or update tasks, notes, and tags for contacts using the endpoints listed. Map fields to ensure changes appear in both Dust and GHL.
Error logs can be found in the Dust app under the integration section for GHL Contacts API. Enable verbose logging if needed and check for rate limits or authentication issues.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
