Authenticate requests with your GHL credentials and grant the necessary scope (locations/customValues.readonly) to enable access to read operations. Use your API key or OAuth flow as configured in your GHL account.
Securely authenticate your ActiveCampaign app with the platform’s recommended method (API token or OAuth). Ensure the connection is authorized for data syncing with Custom Fields API.
The integration relies on a set of endpoints to manage location custom values, custom fields, and tags. Primary endpoints include: GET /locations/:locationId/customValues, POST /locations/:locationId/customValues, GET /locations/:locationId/customFields, POST /locations/:locationId/customFields, and GET /locations/:locationId/tags, among others listed below.
Trigger: When a location’s custom value changes, push the update to the matching ActiveCampaign contact field.
Actions: Use GET /locations/:locationId/customValues to read and POST/PUT to update values; then map to the corresponding ActiveCampaign contact field and send a write operation.
Method paths: GET /locations/:locationId/customValues, POST /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id, DELETE /locations/:locationId/customValues/:id.
Key fields: locationId, id, valueKey, value.
Trigger: When location fields are added or updated, reflect changes in ActiveCampaign.
Actions: Use endpoints 7-9 for fields, 12-15 for write operations, and 17 for tags as needed to organize fields.
Method paths: GET /locations/:locationId/customFields, POST /locations/:locationId/customFields, PUT /locations/:locationId/customFields/:id, DELETE /locations/:locationId/customFields/:id, GET /custom-fields/:id, GET /custom-field/object-key/:key.
Key fields: locationId, id, fieldKey.
Trigger: When tags are added or removed in ActiveCampaign.
Actions: Use GET /locations/:locationId/tags to read tags and PUT/DELETE to manage them.
Method paths: GET /locations/:locationId/tags.
Key fields: locationId, tag.
Automate data flow between ActiveCampaign and Custom Fields API without writing a line of code.
Keep data synchronized in real time, reducing manual updates and errors.
Leverage a robust set of endpoints to tailor workflows and reporting.
Definitions of key terms you’ll encounter: Location, Custom Value, Custom Field, Endpoint, and Tag, plus how they interact in this integration.
A Location is a logical or physical grouping within your GHL account used to organize custom values and fields.
A Custom Value is a data item attached to a Location that can be read, created, updated, or deleted via the API.
A Custom Field is a reusable data attribute that describes a person, place, or thing and can be mapped to ActiveCampaign records.
An Endpoint is a specific API URL path used to perform actions like read, write, or delete.
Automatically push changes from location custom values to the corresponding ActiveCampaign contact fields to keep records in sync.
Use location-based custom fields to segment ActiveCampaign lists and trigger targeted automations.
Maintain an auditable history of custom field changes for compliance and analytics.
Obtain credentials for both systems and grant necessary scopes to enable syncing.
Select endpoints for reading and writing location custom values and fields, then map them to ActiveCampaign fields.
Create automations and triggers to keep data in sync across systems.
No coding is required for a basic setup. The guided UI helps you authenticate and map the endpoints between Custom Fields API and ActiveCampaign. You can use prebuilt workflows to automate data sync and trigger updates without writing code.
Key endpoints include GET /locations/:locationId/customValues, POST /locations/:locationId/customValues, and PUT /locations/:locationId/customValues/:id to manage values. Additionally, manage custom fields with GET /locations/:locationId/customFields, POST/PUT/DELETE on /locations/:locationId/customFields/:id, and read endpoints like GET /custom-fields/:id and GET /custom-field/object-key/:key; tags are accessible via GET /locations/:locationId/tags.
Authenticate via API key or OAuth; ensure the correct scopes are granted for read/write operations. Securely store tokens and rotate credentials as recommended by your security policy. Include the token in the Authorization header for each request and follow the provider’s best practices for token refresh and revocation.
Yes. Depending on your scopes, you can read and write across multiple locations by mapping locationId to the target records. Plan your data model to avoid conflicts and respect rate limits. Consider batching requests for high-volume updates to maintain performance and reliability.
To manage tags, read current tags with GET /locations/:locationId/tags and add or remove tags with the appropriate write operations. Keep tag data synchronized with ActiveCampaign segments for accurate automation triggers. Use consistent tag naming conventions to avoid duplication and ensure clean analytics.
A Location is a grouping container within GHL used to organize related data. A Custom Field is a reusable data attribute that can be associated with a Location or a Contact and mapped to ActiveCampaign records. Fields describe the data type and purpose, while values populate those fields for each Location or related entity.
Refer to the API documentation and the endpoints list provided in this page for detailed usage, parameters, and example requests. The end-to-end guide above includes practical scenarios and recommended workflows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
