To access the Custom Fields API from Actionstep, obtain an API key or OAuth token and grant permissions with the scope locations/customValues.readonly.
In Actionstep, create a connected app and authorize access to the Custom Fields API as the resource you want to connect. Store credentials securely and rotate keys regularly.
Core endpoints include: GET /locations/:locationId/customValues; GET /locations/:locationId/customValues/:id; POST /locations/:locationId/customValues; PUT /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; GET /locations/:locationId/tags; GET /locations/:locationId/customFields; GET /custom-fields/:id; GET /custom-field/object-key/:key; GET /locations/:locationId/tags
Trigger: When a location’s custom values change in GHL, fetch the latest values and update Actionstep records.
Actions: Use GET /locations/:locationId/customValues to retrieve data and map fields into Actionstep fields.
Method Path: GET /locations/:locationId/customValues
Key fields: locationId, id, value, timestamp
Trigger: New or updated value in Actionstep prompts a write to GHL.
Actions: POST /locations/:locationId/customValues and PUT /locations/:locationId/customValues/:id to sync values.
Method Path: POST /locations/:locationId/customValues
Key fields: locationId, id, value, updatedAt
Trigger: Actionstep changes in bulk to update multiple fields in GHL.
Actions: POST /locations/:locationId/customFields and PUT /locations/:locationId/customFields/:id to manage field metadata.
Method Path: POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id
Key fields: locationId, id, key, label
Build powerful automations without writing code—connect data from GHL to Actionstep in minutes.
Centralize data mappings across systems, reducing manual data entry and errors.
Fast setup with the Zapier App Connector, enabling rapid experimentation and go-live.
This glossary defines core terms and how they map to elements and processes when connecting GHL with Actionstep.
A unique identifier for a location in GHL, used to scope API calls to a specific site.
A data item stored for a location, such as a preference or note that can be read or written via the API.
A metadata label attached to a resource to capture structured data (field key, label, type).
A specific URL path and HTTP method used to perform an action against the GHL API.
Automatically pull in the latest custom values from GHL into Actionstep client profiles to keep records fresh.
Route leads to different actions in Actionstep based on custom field values in GHL.
Export custom fields data to analytics or reports for quarterly reviews.
Create or select a connected app and grant permission to the Custom Fields API in GHL, then capture the access token in Actionstep.
Define field mappings between GHL custom values/fields and Actionstep fields.
Run end-to-end tests and enable live syncing between systems.
No-code options make this accessible to non-developers. Use Zapier or the GHL App Connector to set up triggers, actions, and data mappings without writing code. If you do code, you can customize logic using endpoint responses.
Supported methods typically include API key or OAuth token-based authentication. Ensure scopes cover read and write access to locations and custom values. Rotate credentials regularly and store securely.
Common endpoints used for syncing include GET /locations/:locationId/customValues and POST /locations/:locationId/customValues, plus related customFields endpoints. They let you read, create, or update field data at the location level.
Yes. Field mappings between GHL and Actionstep can be configured in automation platforms or within app connectors. Define source fields and target fields, including data types, to avoid format mismatches.
Implement retries, log errors, and use idempotent calls where possible. Validate inputs, monitor webhook failures, and alert your team on critical failures.
Security is ensured through standard API authentication, encrypted transport (HTTPS), and least-privilege access scopes. Regularly review permissions and rotate keys.
API reference and endpoint lists are available in the GHL developer docs and via the connected app configuration in Actionstep. Bookmark the endpoints you plan to use and test them in a sandbox.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
