Use OAuth 2.0 to obtain access tokens that authorize calls to the Contacts API from your Duda app.
Configure a client in Duda to request the necessary scopes and securely handle tokens for ongoing API requests.
17 endpoints including reading, creating, updating, and deleting contacts, tasks, notes, appointments, and tags.
Trigger a contact detail panel on a Duda page when a user selects a contact
Actions: GET /contacts/:contactId to fetch details; GET /contacts/:contactId/tasks to load tasks
Method path: GET /contacts/:contactId
Key fields: id, name, email, phone, status
Trigger: show related tasks and notes for a contact in Duda
Actions: GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes
Method path: GET /contacts/:contactId/tasks
Key fields: taskId, title, dueDate, status
Trigger: create or update a contact from a Duda form
Actions: POST /contacts/, PUT /contacts/:contactId, DELETE /contacts/:contactId
Method path: POST /contacts/; PUT /contacts/:contactId; DELETE /contacts/:contactId
Key fields: contactId, name, email, phone, tags
Automate contact updates from Duda forms without writing code
Sync tasks and notes to keep teams aligned and informed
Leverage ready endpoints to craft rich, interactive contact experiences
Understand endpoints, triggers, actions, and fields to design reliable GHL-Duda integrations
A specific URL and HTTP method used to perform an operation against the GHL API.
A secure authorization protocol that grants access without sharing user credentials.
An individual record in the Contacts API containing personal and engagement data.
An item assigned to a contact, with status, due date, and related notes.
Embed a Duda form that creates or updates a contact in GHL via the Contacts API.
Display contact-linked tasks within Duda pages and link to full details in GHL.
Show the latest notes for a contact on Duda pages with quick action buttons.
Register your app in GHL to obtain client_id, client_secret, and required scopes for contacts.readonly.
Set your redirect URI in Duda and exchange authorization codes for access tokens.
Test API calls against the listed endpoints, then deploy to production.
In most cases you can start with no coding by using built-in connectors and a simple data map. If you are comfortable with basic HTTP calls, you can customize endpoints as needed.
Permissions depend on the scope you request. For read-only access, use contacts.readonly; for updates, include write permissions in your OAuth scope.
The primary read endpoints include GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes. You can expand as needed.
Yes. Use POST to create or PUT to update a contact. Deletion is available via DELETE /contacts/:contactId with appropriate safeguards.
OAuth is used to securely grant tokens. Exchange the authorization code for an access token, then include it in the Authorization header of requests.
Test environments or sandboxes can be provided by your GHL account. Use test endpoints if offered and separate test data from production.
Endpoint lists and sample payloads are typically available in your developer portal or API docs. Use sample requests to validate your setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
