Authenticate to the Custom Objects API using your GHL API credentials with the scope objects/schema.readonly. Use an API key or OAuth token as configured in your GHL account.
Securely connect Active Knocker to the Custom Objects API using standard OAuth2 or API tokens and store credentials securely.
GET /objects/:key; GET /objects; GET /objects/:schemaKey/records/:id; POST /objects/:schemaKey/records; PUT /objects/:schemaKey/records/:id; DELETE /objects/:schemaKey/records/:id; objects/schema.write; objects/record.readonly
Trigger on object key updates to fetch the latest data as soon as it changes.
Synchronize the object record in Active Knocker and reflect updates in related workflows.
GET /objects/:key
key, name, updatedAt
Schedule periodic pulls to refresh the object catalog in Active Knocker.
Batch import of objects and their records into Active Knocker for bulk updates.
GET /objects
objectKey, id, lastModified
Push changes from Active Knocker to GHL when records are created or updated.
Use POST and PUT to create or update object records in GHL.
POST /objects/:schemaKey/records; PUT /objects/:schemaKey/records/:id
schemaKey, id, payload
Automate data sync without manual CSV imports or duplicative work.
Reduce errors and keep cross-system records up to date automatically.
Power workflows in Active Knocker using live object data from GHL.
A concise glossary of terms used in this integration guide, including objects, schemas, records, and endpoints.
A collection in the GHL Custom Objects API that groups related records.
A single entry within an object, representing one item’s data.
The blueprint that defines fields, data types, and validations for an object.
A URL path that performs a specific API action (GET, POST, PUT, DELETE).
Automatically sync new or updated objects from GHL to Active Knocker for instant action.
Trigger campaigns in Active Knocker when object fields meet criteria.
Centralize logs and dashboards showing API activity and object health.
Create or retrieve your GHL API key and configure Active Knocker credentials.
Define which objects to sync, map fields, and choose endpoints for your flows.
Run tests, verify data integrity, monitor logs, and go live with confidence.
The GHL Custom Objects API lets you read, create, update, and delete custom objects defined in GHL. It enables apps like Active Knocker to access your object data programmatically. Use the endpoints listed above to query objects, schemas, and records, with proper authentication and scopes.
Authentication is handled via GHL API tokens or OAuth, and Active Knocker uses secure token storage. Ensure your credentials are kept safe and rotated regularly. Grant the required scope objects/schema.readonly for read operations, and request write access only when necessary.
Supported 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-related calls like objects/schema.write. These enable full lifecycle management of objects and their records.
Yes. Active Knocker can create or update object records by calling POST or PUT on the appropriate endpoints. Be mindful of permissions, rate limits, and test in a staging environment before going live.
You can sync object keys, field values, records, and metadata between GHL and Active Knocker. The data types supported depend on your object schema and may include text, numbers, dates, and booleans.
There is a no-code path via Active Knocker workflows that can trigger API calls without custom coding. You can also use automation tools like Zapier to map fields and initiate actions.
For troubleshooting, check API call logs in both GHL and Active Knocker, verify authentication scopes, and confirm endpoint paths. Enable verbose logging and test with sample data, then contact support if issues persist.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
