Authenticate against GHL using the required scope locations/customValues.readonly and grant access to your Zapier App Connector.
In Zapier, configure OAuth 2.0 or an API key flow to securely connect to GHL resources via the Custom Fields API.
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; GET /custom-fields/:id; GET /custom-field/object-key/:key; POST /locations/:locationId/customFields; PUT /locations/:locationId/customFields/:id; DELETE /locations/:locationId/customFields/:id; GET /locations/:locationId/tags; GET /locations/:locationId/customFields.readonly; locations/customFields.write; GET /locations/:locationId/customFields; GET /locations/tags
Trigger when you need to fetch a location’s custom values
Actions include get values, filter by id and paginate if needed
GET /locations/:locationId/customValues
locationId and id
Trigger when a new or updated value is needed
Actions: create (POST) or update (PUT) a value
POST /locations/:locationId/customValues
locationId and id
Trigger when you need to read or write location custom fields
Actions: read fields, write fields, update field values
GET /locations/:locationId/customFields
locationId and optional field id
No coding required to connect endpoints
Automated data mapping between GHL and apps
Faster go to market with templates and prebuilt actions
Definitions of endpoints, triggers, actions, auth and data fields
A URL and HTTP method used to access a resource in GHL
An event that starts a Zap when the condition is met
An operation performed in response to a trigger
A value used to identify a resource such as locationId or id
Automatically pull custom values when a location is added or updated to keep records up to date
Push changes to your CRM when custom values change in GHL to ensure data consistency
Keep an audit trail of changes to custom values for compliance
Obtain tokens and grant access to endpoints
Select triggers and actions and map data
Run tests and set up monitoring
You can use no code connectors like Zapier App Connector to access endpoints without writing code. Start by authenticating and selecting a trigger that matches your workflow. Then choose actions to update or fetch data.
Yes. The endpoints support a no code flow via Zapier. Create a zap that uses a trigger from GHL and actions that call the desired endpoints to read or write data.
Authentication typically uses OAuth 2.0 or API keys. You will be granted access based on the GHL scope you request and the app connection you configure.
Reading is done with the GET endpoints such as locations and custom values. You can filter by locationId or id to target specific records.
Yes. Use POST to create new values or PUT to update existing ones for a location. Ensure you supply required fields and identifiers.
Map fields by aligning the GHL fields with your app fields in Zapier using a data mapping step or custom fields.
Endpoint docs cover all supported endpoints. Check the docs for method paths, required fields and error handling.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
