Scope is readonly (contacts.readonly). Use the GHL API to obtain credentials that grant read access to contacts and related resources.
Document360 will use the provided credentials to access contact data via the GHL Contacts API within the allowed scope.
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
Trigger: A request for a contact in Document360 should fetch core fields via GET /contacts/:contactId.
Actions: pull contactId, name, email, phone, and lastActivity; no write actions permitted under readonly scope.
GET /contacts/:contactId
Key fields: contactId, name, email, phone, lastActivity
Trigger: When a contact has tasks or notes, pull latest items via GET endpoints.
Actions: list tasks and notes; cannot create or update tasks at this time due to read-only scope.
GET /contacts/:contactId/tasks and GET /contacts/:contactId/notes
Key fields: taskId, subject/title, status, dueDate; noteId, content, updatedAt
Trigger: List contacts and optionally link to a business via GET /contacts/ and GET /contacts/business/:businessId
Actions: fetch contacts; fetch business associations; read only fields
GET /contacts/
Key fields: contactId, businessId, name, email
Automate data flow without coding; bring contact data directly into Document360 workflows.
Consolidate contact activity across tasks, notes, and appointments in a single view.
Leverage standard REST endpoints for easy mapping and automation with your existing tools.
This glossary covers endpoints, triggers, actions, and fields used in the GHL Contacts API integration with Document360.
The RESTful API that enables apps to read and update data in your GHL account, subject to assigned scopes.
A specific URL path that performs a defined operation on resources, such as GET /contacts/:contactId.
An event that starts a workflow or action in an integration.
An operation executed in response to a trigger, such as POST to create or PUT to update a resource.
Fetch new contacts via GET and create onboarding tasks in Document360 automatically.
Keep notes and tasks up to date in Document360 when GHL activity happens.
Aggregate endpoint data to present a live activity feed per contact inside Document360.
Obtain API credentials with the readonly scope and configure them in Document360.
Create mappings for contact fields (id, name, email) and related data across endpoints.
Test each endpoint and verify data flows into Document360 workflows.
Yes. Write operations are not allowed with the readonly scope. You cannot create, update, or delete contacts using these endpoints. If you need write capabilities, request an upgrade to a higher scope or separate credentials with write permissions from your GHL admin. This page covers read-only data retrieval to safely pull contact information into Document360.
Authentication is handled via API credentials with the declared scope (contacts.readonly). Use OAuth2 or API keys as provided by GHL; keep tokens secure and rotate when needed. Store tokens securely in Document360, refresh as needed, and include appropriate authorization headers in each request.
Endpoints included in the read-only scope are GET endpoints for contacts, tasks, notes, and appointments, as well as listing endpoints for contacts and business associations. You may find endpoints 1-7 (and 8) detailed in the Endpoint List section; never use POST/PUT/DELETE without proper scope.
No. Creating or updating contacts requires write access. With read-only access you can only fetch data. If you need to modify data, upgrade the API credentials to include write permissions and use the corresponding endpoints.
There are rate limits for GHL API requests. Plan requests carefully and implement retry/backoff logic. Consider caching frequently accessed contact data and batch requests to stay within limits and improve performance.
Map fields consistently between GHL and Document360. For example, map contactId to your internal contact identifier and align nested fields such as tasks and notes. Test mappings with sample records to ensure data types and formats align (strings, numbers, dates).
The endpoint list and example requests are described in the Endpoint List section of this page. Look for example curl snippets and field mappings to accelerate setup and verification.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
