Authenticate using your GHL API credentials. Use OAuth or an API key as appropriate, and grant Disciple the requested scopes to read data (Scope: contacts.readonly) and, if needed, write access.
In Disciple, provide your GHL API credentials and authorize the Disciple app to access Contacts data for the configured scopes.
GET /contacts/:contactId — fetch a single contact; GET /contacts/:contactId/tasks — fetch tasks for a contact; GET /contacts/:contactId/tasks/:taskId — fetch a specific task; GET /contacts/:contactId/notes — fetch notes for a contact; GET /contacts/:contactId/notes/:id — fetch a specific note; GET /contacts/:contactId/appointments — fetch appointments for a contact; GET /contacts/ — list contacts; GET /contacts/business/:businessId — list contacts for a business; contacts.write — write permission; POST /contacts/ — create a contact; PUT /contacts/:contactId — update a contact; DELETE /contacts/:contactId — delete a contact; POST /contacts/:contactId/tasks — create a task; PUT /contacts/:contactId/tasks/:taskId — update a task; PUT /contacts/:contactId/tasks/:taskId/completed — mark task complete; DELETE /contacts/:contactId/tasks/:taskId — delete a task; POST /contacts/:contactId/tags — add tags to a contact
Trigger: a new contact is created in Disciple or an existing contact is updated, initiating a sync to GHL.
Actions: upsert the corresponding contact in GHL (create or update fields like name, email, phone, tags); maintain a stable mapping of contactId.
Method paths: GET /contacts/:contactId, POST /contacts/, PUT /contacts/:contactId
Key fields: contactId, email, firstName, lastName, phone, tags
Trigger: when a contact’s tasks change in Disciple, push updates to GHL.
Actions: create/update tasks under /contacts/:contactId/tasks; update task status; optionally call completed endpoint.
Paths: POST /contacts/:contactId/tasks, PUT /contacts/:contactId/tasks/:taskId, DELETE /contacts/:contactId/tasks/:taskId
Key fields: taskId, contactId, title, dueDate, status, completed
Trigger: notes added or updated on a contact in Disciple triggers notes sync to GHL.
Actions: create/update notes at /contacts/:contactId/notes and retrieve via /contacts/:contactId/notes/:id.
Paths: GET /contacts/:contactId/notes, POST /contacts/:contactId/notes, PUT /contacts/:contactId/notes/:id
Key fields: noteId, contactId, note, createdAt
No coding required; configure triggers and actions in a visual flow builder.
Faster time-to-value with ready-made endpoints and drag-and-drop automation.
Centralized access to contacts, tasks, and notes across Disciple and GHL.
A glossary of core terms including API endpoints, authentication, and data objects (contacts, tasks, notes) to help you understand the integration.
A specific URL and HTTP method that allows you to perform an action on a resource within an API.
The process of proving identity and obtaining access tokens or keys to call the API.
A record representing a person in the CRM with fields like name, email, and phone.
A to-do item linked to a contact, with status and due date.
Automatically tag a contact in GHL when a new contact is created in Disciple to enable targeted automations.
Create follow-up tasks in GHL when Disciple notes or properties change.
Aggregate contact activity across Disciple and GHL into a single report for insights.
Register the Disciple app in GHL and generate an API key or OAuth client.
Grant the required scopes (e.g., contacts.readonly) and set up the endpoints you will use.
Run tests to fetch a contact, then create a task or note to verify write permissions.
The required scope for Disciple is typically the Contacts API scope, such as contacts.readonly for read access. If you need to write or modify data, request elevated scopes from your GHL admin. Always follow access control policies to protect sensitive contact data. In most setups, Disciple operates under the principle of least privilege.
No coding is required to set up basic triggers and actions—our no-code workflow builder handles this. You can map fields, set up conditions, and run tests without writing code. For advanced custom logic, you may still add small scripts if your plan allows it.
Commonly used endpoints include GET /contacts/:contactId to fetch a contact and POST /contacts/ to create one. For day-to-day work, GET /contacts/:contactId/tasks and GET /contacts/:contactId/notes cover tasks and notes retrieval, while PUT and DELETE variants handle updates and removals.
Test the integration with a dry run in Disciple’s test environment or a sandbox. Verify that data maps correctly and that changes in Disciple reflect in GHL. Check logs for errors and confirm data integrity across both systems.
Yes. You can create and update tasks, add notes, and even mark tasks as completed from Disciple. The changes will sync to GHL according to your mapping and automation rules.
If a contact is deleted, you can configure the integration to soft-delete or to delete the corresponding record in GHL. Implement safeguards to prevent unintended data loss and consider archival options when needed.
The endpoint list is documented in the ENDPOINTLIST section of this page and accessible in your Disciple integration settings. You can reference the available methods and paths to configure your flows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
