Authenticate API calls with a valid access token and the correct scope (locations/customValues.readonly and related endpoints). Use your GHL developer credentials to obtain and refresh the token as needed.
In Act!, include your GHL access token in request headers and ensure the app has permission to access custom values for the targeted location.
Primary endpoints you will use with Act! include read and write operations for location-specific custom values and fields, such as GET /locations/:locationId/customValues, POST /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id, DELETE /locations/:locationId/customValues/:id, plus related endpoints for custom fields.
Trigger: when a location is opened in Act! or when values need display.
Use GET /locations/:locationId/customValues to fetch values and render them in Act!.
GET /locations/:locationId/customValues
locationId (required); id (optional for a single value)
Trigger: user submits a value in Act!
Use POST /locations/:locationId/customValues to create; PUT /locations/:locationId/customValues/:id to update.
POST /locations/:locationId/customValues
locationId; value fields; id for updates
Trigger: cleanup or archival workflow
Use DELETE /locations/:locationId/customValues/:id to remove a value.
DELETE /locations/:locationId/customValues/:id
locationId and id (required)
Automate data flows between Act! and GHL custom fields to reduce manual entry.
Maintain consistent field values with real-time updates.
Leverage templates and triggers for scalable workflows.
A quick glossary of terms used here and how the pieces fit together in the Act! and GHL integration.
Application Programming Interface: a set of rules that lets software communicate.
A specific URL path in an API that performs an action or returns data.
The process of verifying identity before allowing access to API resources.
A customer site or account location within GHL/Act! where data is stored.
Automatically map Act! fields to GHL custom values using field-level triggers.
Build dashboards in Act! showing live custom field reads from GHL.
Use templates for batch updating of values via endpoints.
Obtain an access token with the proper scopes and ensure Act! app permissions are set.
Use the provided endpoint paths to read and write custom values for locations.
Test calls, validate responses, and implement in Act! workflows.
The Custom Fields API in GHL exposes endpoints to read and manage custom values and fields. When connected to Act!, you can pull in location-specific data and push updates back to GHL so your workflows stay in sync.
Use endpoints like GET /locations/:locationId/customValues and POST /locations/:locationId/customValues to fetch and create, with PUT and DELETE to update or remove as needed. Ensure the locationId is known and you have the correct permissions.
Authentication is handled with an access token and required scopes. Use OAuth or API keys as provided by GHL and include the token in request headers for each API call.
While some no-code automations are possible via Act! workflows and URL-based actions, most advanced data manipulation requires API calls. The integration is designed to be learner-friendly with examples.
Map Act! fields to corresponding GHL custom fields by matching field keys or IDs. Store the mapping in a configuration and use it in your API calls to translate values.
To delete a value, call DELETE on the location’s customValues endpoint with the appropriate id and locationId. Handle responses and errors in your workflow.
Visit the GHL developer docs, the Act! integration guides, and community resources for examples, best practices, and troubleshooting tips.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
