Use your GHL credentials to authorize requests to the Custom Objects API. The required scope is objects/schema.readonly to read object schemas and records.
Accelo uses OAuth 2.0 tokens. Obtain a client ID and secret from your Accelo admin, complete the authorization flow, and securely store tokens for API calls.
GET /objects/:key – fetch a specific object by key; GET /objects – list all objects; objects/schema.write – write object schemas; objects/record.readonly – read-only access to records; GET /objects/:schemaKey/records/:id – retrieve a single record; objects/record.write – write records; POST /objects/:schemaKey/records – create a new record; PUT /objects/:schemaKey/records/:id – update a record; DELETE /objects/:schemaKey/records/:id – delete a record.
Trigger when a new object is created or an existing object key is updated in Accelo, then pull the latest object metadata from GHL to keep your schema in sync.
Actions: list objects, fetch object schemas, and map core fields to Accelo’s custom object fields for consistent data representation.
GET /objects and GET /objects/:key to read object definitions and records.
Key fields: id, key, name, schemaKey, fields
Trigger when an Accelo record is created or updated, then push the corresponding object record to GHL.
Actions: create new GHL records with POST, update existing ones with PUT, and maintain field mappings between systems.
POST /objects/:schemaKey/records and PUT /objects/:schemaKey/records/:id
Key fields: schemaKey, id, key, fields
Trigger when a record is archived or deleted in Accelo to remove or deactivate the corresponding GHL record.
Actions: delete or soft-delete GHL records, ensure audit trails, and handle error cases gracefully.
DELETE /objects/:schemaKey/records/:id and (optionally) PUT /objects/:schemaKey/records/:id for soft-delete
Key fields: id, schemaKey, status
Rapid setup: Use prebuilt endpoints and field mappings to connect without custom development.
Unified data model: synchronize objects without writing backend code, reducing maintenance overhead.
Automation and scalability: leverage triggers and actions that scale with your data volume.
Key elements include endpoints, object schemas, records, triggers, actions, and field mappings. Understanding these ensures reliable integration between GHL and Accelo.
A set of REST endpoints that allow apps to read and write data in GHL for objects, schemas, and records.
A collection of fields that define a specific data type in GHL, such as a custom object used to store account or contact information.
The blueprint that defines object fields, their types, and relationships for a GHL object.
A URL path in the API used to perform a specific action, such as reading or writing objects and records.
Automatically create a GHL object when a new Accelo lead is created. Map lead fields to the object fields to keep data aligned without manual entry.
Push status changes from Accelo to the corresponding GHL object record to reflect current engagement level and next actions.
Archive or mark as inactive old Accelo records in GHL to maintain a lean data set and improve performance.
Obtain API keys or OAuth credentials from GHL and Accelo, then securely store them in your integration platform.
Define how GHL object fields align with Accelo fields, and configure the endpoints you will call for reads and writes.
Run tests to verify data is syncing correctly, check error handling, and confirm authentication scopes.
The Custom Objects API exposes endpoints to read and write custom data objects in GHL. When paired with Accelo, you can synchronize records, read object schemas, and automate updates between systems. This setup is designed to be approachable for teams that want reliable data flow without heavy development. You can start by reading object definitions, then map fields to your Accelo custom objects and begin with small, test-first syncs.
Some endpoints can be used with no code in many integration platforms, while others may require lightweight scripting to map fields and handle upserts. Depending on your tooling, you can often implement the most common needs with point-and-click configurations, and reserve code for complex transformations.
Commonly used endpoints include GET /objects to list objects, GET /objects/:key to fetch a specific object, and POST /objects/:schemaKey/records to create records. For updating, PUT /objects/:schemaKey/records/:id is used, and for deletion, DELETE /objects/:schemaKey/records/:id. These endpoints cover the core read and write flows between GHL and Accelo.
Field mapping involves aligning GHL object fields with Accelo custom fields. You typically create a mapping table that defines source (GHL) fields to target (Accelo) fields, including data types and any required transformations. Testing the mappings with sample records helps ensure data integrity.
Security is maintained through OAuth 2.0 tokens or API keys, with scope controls such as objects/schema.readonly. Tokens should be stored securely and rotated regularly. Always use HTTPS to protect data in transit and implement least-privilege access for integrations.
For errors, enable verbose logging and implement retry strategies with backoff. Common issues include authentication failures, schema mismatches, and missing field mappings. Provide clear error messages and maintain idempotent operations where possible to avoid duplicate records.
Payload examples and schemas are typically documented in the API reference or integration guide. Many teams start with a minimal example for a read or write operation and then expand to more complex mappings as needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
