To access the Custom Fields API, obtain an API key or OAuth token from your GHL developer portal and grant Act-On the required scope: locations/customValues.readonly.
In the app connector, follow prompts to connect Act-On to the Custom Fields API using the credentials above and select the endpoints you want enabled for sync.
Core endpoints include: GET /locations/:locationId/customValues; GET /locations/:locationId/customValues/:id; POST /locations/:locationId/customValues; PUT /locations/:locationId/customValues/:id; DELETE /locations/:locationId/customValues/:id; GET /locations/:locationId/customFields; GET /locations/:locationId/customFields/:id; POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; DELETE /locations/:locationId/customFields/:id; GET /custom-fields/:id; GET /custom-field/object-key/:key; POST /locations/:locationId/customFields; GET /locations/:locationId/tags; GET /locations/:locationId/tags (read-only); GET /locations/customFields.readonly; GET /locations/:locationId/customValues (readable).
Trigger: a change to a location’s custom value triggers a sync to Act-On.
Actions: GET /locations/:locationId/customValues and map to Act-On fields.
Method path: GET /locations/:locationId/customValues
Key fields: locationId, id, customValue
Trigger: create or update a custom field in GHL to reflect in Act-On.
Actions: POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; map to Act-On.
Method path: POST /locations/:locationId/customFields
Key fields: locationId, id, fieldKey
Trigger: tag changes in GHL update Act-On segments.
Actions: GET /locations/:locationId/tags; manage tag mappings for segmentation.
Method path: GET /locations/:locationId/tags
Key fields: locationId, tagId
Automate data flow without custom code using visual mappings and presets.
Set up connections quickly with endpoint presets and data mapping, enabling rapid deployment.
Improve personalization in Act-On by syncing accurate, up-to-date custom values and fields from GHL.
This glossary defines the core terms and processes used to connect GHL’s Custom Fields API with Act-On.
A defined URL with an HTTP method used to request or update data from an API.
The process of proving identity and obtaining access tokens or keys to use the API.
A unique identifier for a specific location in GHL.
A data point stored for a location that can be read or written via endpoints.
Keep Act-On contact records up-to-date by streaming changes from GHL Custom Values in real time.
Use endpoint events to trigger Act-On workflows when a field changes, without coding.
Leverage tags from GHL to segment audiences in Act-On campaigns for precise targeting.
Obtain API keys and set the necessary OAuth scopes for the Custom Fields API.
Enable and test endpoints such as read and write for custom values and fields.
Create field mappings in Act-On and run end-to-end tests to verify data flows.
No extensive coding is required for this integration. Use the Zapier App Connector to map endpoints and fields visually. Start by authenticating, then select the endpoints you need and create mappings to Act-On fields. You can run test flows to confirm data moves correctly.
For a basic sync, you will typically use endpoints for reading and writing custom values and fields (GET/POST/PUT). Map the common fields between GHL and Act-On and set up a simple trigger to begin syncing. You can expand with tags and more endpoints later.
The integration uses standard API authentication methods (API keys or OAuth tokens) and supports secure transport. Store credentials securely and follow least-privilege access for the Act-On connection.
Yes. You can map custom values and custom fields from GHL to corresponding fields in Act-On using field mappings. Update mappings as your data model evolves.
Test the connection by running a dry run of a workflow or a small data pull. Check logs, verify mappings, and ensure data appears in Act-On as expected.
API rate limits depend on your GHL plan. If you hit limits, stagger requests, cache results, and schedule syncs to avoid bursts.
Credentials are typically issued in your GHL developer portal and can be stored securely in the Act-On connector settings. If you need help, contact your administrator.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
