Authenticate API calls with your GHL API key and the required scope: locations/customValues.readonly. Include the key in the Authorization header as a Bearer token for each request.
Use the Action Network API key or OAuth flow provided in your account. Include the token in the Authorization header when calling Action Network endpoints, and keep credentials secure.
– GET /locations/:locationId/customValues – GET /locations/:locationId/customValues/:id – locations/customValues.write – POST /locations/:locationId/customValues – PUT /locations/:locationId/customValues/:id – DELETE /locations/:locationId/customValues/:id – locations/customFields.readonly – GET /locations/:locationId/customFields – GET /locations/:locationId/customFields/:id – GET /custom-fields/:id – GET /custom-field/object-key/:key – locations/customFields.write – POST /locations/:locationId/customFields – PUT /locations/:locationId/customFields/:id – DELETE /locations/:locationId/customFields/:id – locations/tags.readonly – GET /locations/:locationId/tags
Triggered when a location value changes in Action Network, then sync with GHL to update the corresponding custom value.
Use GET /locations/:locationId/customValues to read values and POST/PUT /locations/:locationId/customValues to create or update them. Use DELETE when pruning data.
Method path: /locations/:locationId/customValues and /locations/:locationId/customValues/:id
Key fields: locationId, id, value
Triggered when you need metadata about available fields to map in Action Network.
Use GET /locations/:locationId/customFields and GET /custom-fields/:id to retrieve field definitions.
Method path: /locations/:locationId/customFields
Key fields: locationId, id
Triggered when managing the full lifecycle of custom fields for a location.
Use GET /locations/:locationId/customFields, POST /locations/:locationId/customFields, PUT /locations/:locationId/customFields/:id, and DELETE /locations/:locationId/customFields/:id as needed.
Method path: /locations/:locationId/customFields and /locations/:locationId/customFields/:id
Key fields: locationId, id
Synchronize data between Action Network and GHL without custom coding, reducing manual data entry.
Improve data accuracy by centralizing field values and definitions in one source of truth.
Automate routine workflows and triggers to save time and avoid errors.
This section defines data elements (locations, customValues, customFields, tags) and processes (CRUD, synchronization, mapping) used to connect the GHL Custom Fields API with Action Network.
A URL on the API that performs a specific action (read, write, delete, or update) and is listed in the endpoint catalog above.
Create, Read, Update, and Delete actions used to manage resources such as custom values and fields.
An HTTP header (Authorization: Bearer
A unique resource identifier for a physical or logical location within the system, used to scope API calls.
Automatically push selected Action Network attendee fields into GHL custom values to keep records aligned across apps.
Use live data from Action Network to populate Custom Fields in GHL forms and dashboards for better insights.
Set up triggers that surface key changes in custom values to your team via dashboards or notifications.
Obtain and securely store API keys for both GHL and Action Network, then configure credentials in your integration.
Map Action Network fields to GHL custom values and set up the required endpoint calls.
Run test cases, confirm data sync accuracy, and deploy the integration with monitoring.
The Custom Fields API exposes endpoints to read and manage location-based values and fields. It is designed to work with GHL to keep your data in sync across systems. Use the endpoints listed to fetch, create, update, and delete records as needed. This API enables you to model your data with location-centric custom values and fields, giving you flexibility in routing information between GHL and Action Network.
No heavy coding is required for many common tasks. You can leverage pre-defined endpoints for CRUD operations and standard HTTP methods to integrate without building from scratch. For more complex needs, you can layer in simple automation tools or a middleware like Zapier to handle orchestration.
The best endpoints for syncing custom values are the GET /locations/:locationId/customValues and PUT/POST /locations/:locationId/customValues endpoints, which handle the value lifecycle. For field metadata, use GET /locations/:locationId/customFields and GET /custom-fields/:id to map and design your flow. Always define your locationId and field IDs to ensure accurate data mapping.
Authenticate requests with a Bearer token in the Authorization header for both GHL and Action Network calls. Keep keys secure, rotate them regularly, and scope permissions to the minimum needed for the task.
Yes. You can read custom values and fields, and you can create or update them via POST and PUT operations. Delete options are available for cleanup when appropriate. Plan your access controls to avoid unexpected deletions and to maintain data integrity.
The scope for GHL is typically locations/customValues.readonly, with write access when needed. Action Network uses its own scope and permissions. Ensure each side grants explicit access for the resources you intend to sync.
If API calls fail, check the Authorization headers, endpoint paths, and locationId/ids. Review response messages for hints, verify quotas, and test with smaller data sets. Enable logging and set up alerts for failures.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
