Access to the Custom Objects API requires a secure token. Use your GHL API key or OAuth tokens and ensure your app scope includes objects/schema.readonly for reading data and objects/schema.write for creating or updating records.
Configure authentication in the Zapier App Connector using OAuth or API keys to securely call the Custom Objects API endpoints from your zaps.
Endpoints include:\n- GET /objects/:key\n- GET /objects\n- objects/schema.write\n- objects/record.readonly\n- GET /objects/:schemaKey/records/:id\n- objects/record.write\n- POST /objects/:schemaKey/records\n- PUT /objects/:schemaKey/records/:id\n- DELETE /objects/:schemaKey/records/:id\nAdditional endpoints are available in the full API docs.
Triggers when a new or updated object record is created in the GHL Custom Objects API.
Actions: fetch the record, map fields, and push updates to connected apps or trigger downstream workflows.
GET /objects/:schemaKey/records/:id
schemaKey, id, lastUpdated
Scheduled pulls or on-demand batch fetch of object records from the Custom Objects API.
Actions: retrieve multiple records, transform data, and create/update records in target apps.
GET /objects
limit, offset, schemaKey
Webhook events from GHL fire when object records change, enabling near real-time updates.
Actions: propagate changes to Zapier workflows and downstream systems.
POST /webhooks/objects
schemaKey, eventType, recordId
Automate data flow between GHL Custom Objects and your apps with no code.
Create multi-step workflows using triggers, actions, and conditional logic—no development required.
Deploy quickly, test easily, and scale as your automation needs grow.
Key concepts include endpoints, triggers, actions, schemas, records, and fields that model your objects in GHL and drive automation in Zapier.
A specific URL that lets you access or manipulate a resource in the GHL API.
Defines the structure of a custom object, including its fields and data types.
A single instance of a custom object defined by a schema.
An event that starts a Zapier workflow when data changes in GHL.
Automatically create and update Custom Object records for new users across your systems.
Move records through pipeline stages automatically based on events captured via the API.
Push object data into your analytics tools on a schedule or in response to triggers.
Define the object with required fields in GHL and note the schemaKey.
Connect via API credentials in GHL and set up OAuth or API key in the Zapier App Connector.
Choose trigger endpoints, map fields, and test the workflow.
GHL supports token-based authentication via API keys and OAuth for secure access. Depending on your app’s configuration, you may grant scope such as objects/schema.readonly to read data or objects/schema.write to create or modify records. Always protect credentials and rotate keys regularly.
Endpoints include GET /objects/:key, GET /objects, GET /objects/:schemaKey/records/:id, POST /objects/:schemaKey/records, PUT /objects/:schemaKey/records/:id, DELETE /objects/:schemaKey/records/:id, and schema management endpoints like objects/schema.write. For batch reads you can use GET /objects to list schemas or records, and use query params to filter or paginate results.
Yes. The Zapier App Connector provides triggers and actions that map to GHL’s endpoints, allowing you to automate without writing code. Set up authentication, choose a trigger (e.g., new object record) and actions (e.g., create/update a record), then test and deploy.
GHL enforces API rate limits per key and per endpoint. If you hit limits, responses include retry-after headers. Design your Zapier workflows with batching, pagination, and backoff retries to stay within quotas.
A schemaKey identifies the custom object type you are reading or writing. You can view it in the GHL dashboard under Objects > Schemas. When making requests, you reference the schemaKey in the URL, such as /objects/:schemaKey/records.
Yes. You can filter or limit results using query parameters like limit and offset, and you can target specific records by id. For writes, you supply a request body with the fields defined by the schema to create or update records.
The latest API documentation is available in the GHL developer docs within your GHL account and on the official API reference site. Keep an eye on release notes for endpoint changes, new scopes, and deprecated features.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
