Use your GHL API key and OAuth2 to authorize requests for the Custom Objects API. Keep credentials secure and rotate keys regularly.
Use app-specific credentials or OAuth to securely connect 17hats to the GHL integration and manage permissions.
GET /objects/:key — Retrieve a single object by key; GET /objects — List all objects; objects/schema.write — Update object schema; objects/record.readonly — Read-only access to records; GET /objects/:schemaKey/records/:id — Retrieve a specific record; objects/record.write — Write access to records; POST /objects/:schemaKey/records — Create a record; PUT /objects/:schemaKey/records/:id — Update a record; DELETE /objects/:schemaKey/records/:id — Delete a record. More endpoints are available in the full API docs.
Triggers when object data changes to keep 17hats and GHL in sync in near real-time.
Actions include creating, updating, or deleting object records across both systems to maintain parity.
Representative methods: GET /objects/:key to read objects; POST /objects/:schemaKey/records to create records; PUT /objects/:schemaKey/records/:id to update.
Key fields: key, schemaKey, id, and mapped object fields between systems.
Webhook triggers notify 17hats of changes in GHL, enabling instant updates.
Actions: push updates to 17hats records, map fields, and maintain history.
Representative methods: POST /objects/:schemaKey/records for creates; PUT /objects/:schemaKey/records/:id for updates; GET /objects/:schemaKey/records/:id for reads.
Key fields: id, schemaKey, and mapped data fields.
Scheduled batch jobs run during off-peak hours to sync large changes.
Methods: POST /objects/:schemaKey/records for batch creates; PUT /objects/:schemaKey/records for bulk updates.
Key fields: records array, schemaKey, batchSize.
No-code integration enables non-developers to connect systems and automate data flows.
Build automations with triggers and actions without writing code.
Scale data operations across apps while preserving consistent object schemas.
This glossary covers objects, schemas, records, endpoints, authentication, and data mappings used in the integration.
A named collection of fields representing a data type in GHL that can be read, written, and linked to 17hats records.
A single data entry within an object, identified by an ID and containing the actual data values.
Defines the structure of an object: fields, data types, and relationships.
A URL path and HTTP method used to perform operations on data.
Map 17hats client fields to GHL object fields to ensure consistent data across systems.
Configure triggers so changes in 17hats reflect in GHL in real-time.
Set up scheduled reports comparing object records across apps to spot mismatches.
Obtain API keys and grant access to both systems to enable secure requests.
Define mapping between GHL object fields and 17hats fields and select the endpoints you will use.
Test thoroughly, deploy automations, monitor logs for errors.
No coding is required for basic connections. Use your GHL API key and 17hats credentials to configure endpoints and start syncing. For more complex logic, you can layer automations via third-party tools. If needed, you can extend with custom scripts, but many teams achieve great results with no-code tooling.
For a basic sync, start with reading endpoints like GET /objects/:key and listing with GET /objects. To create records, use POST /objects/:schemaKey/records, and to update use PUT /objects/:schemaKey/records/:id. These cover core create/read/update/delete flows.
Yes. Field mapping is supported. Align 17hats fields to corresponding GHL object fields to ensure data parity across systems. This reduces duplicates and inconsistencies.
Rotate API keys regularly (e.g., every 90 days) and use OAuth tokens where possible. Store credentials securely and monitor for any suspicious activity. Implement access controls and least-privilege permissions.
Test in a staging environment with sample data. Validate data parity, error handling, and retries. Review logs and impact on related automations before going live.
Rate limits vary by plan. Monitor response headers for quotas and implement exponential backoff. If you anticipate spikes, use batch operations and scheduling to stay within limits.
Yes. The docs include sample payloads and payload format guides. You can also export example payloads to understand shapes and mappings for your data.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
