Access to the Custom Fields API requires a valid GHL API key and the correct scopes for reading and writing: locations/customValues.readonly for reading values and locations/customValues.write for updates.
In Zapier, connect your Zapier account to GHL using OAuth2 or API keys supported by the connector and grant required permissions for endpoints you plan to use.
– 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
Trigger: New or updated customValues in a location triggers a Zap to sync with another app.
Actions: Use GET endpoints 1 and 2 to fetch values, POST/PUT to update as needed.
Methods: GET /locations/:locationId/customValues and GET /locations/:locationId/customValues/:id
Key fields: id, locationId, key, value, updatedAt
Trigger: Changes to customFields for a location.
Actions: Use GET/POST/PUT/DELETE for endpoints 8-9, 13-15, 12.
Methods: GET /locations/:locationId/customFields, POST /locations/:locationId/customFields
Key fields: id, locationId, fieldKey, label, type
Trigger: Updates to location tags.
Actions: Use endpoints 16-17 to read tags and attach to records.
Methods: GET /locations/:locationId/tags
Key fields: id, name, slug
Automate data flows without writing code, saving time and reducing manual errors.
Map field changes across apps in real-time and keep data consistent across systems.
Leverage a scalable no-code platform to extend GHL with external tools and workflows.
Key elements include endpoints, authentication, triggers, actions, and the data objects for custom values, fields, and tags.
A specific URL path in the GHL API that performs a defined operation (read, write, delete).
Methods used to verify your identity and permissions to access API resources (keys, OAuth, tokens).
A URL that receives pushed data from GHL when a specified event occurs.
An open standard for delegated authorization used by many apps and services.
Capture form submissions and map fields to customValues to auto-create or update fields in GHL.
Automatically push field changes from 46elks to GHL CRM to keep records in sync.
Use validation in Zapier to ensure only allowed values get written to customFields and customValues.
Connect your GHL account in the Zapier App Connector and authorize access to the Custom Fields API.
Select endpoints for customValues, customFields, and tags to map into your workflows.
Create Zaps that trigger on changes to custom fields/values and perform actions in connected apps.
The Custom Fields API provides programmatic access to your GHL data for custom values, fields, and tags. You can read existing values and fields using endpoints like GET /locations/:locationId/customValues and GET /locations/:locationId/customFields. This enables you to sync data into Zapier and other apps without manual exports. For modifying data, use the write-enabled endpoints such as POST, PUT, and DELETE variants to create, update, or remove customValues and customFields as needed.
Read-only access is controlled by scopes. To view data, ensure your GHL API key includes locations/customValues.readonly and locations/customFields.readonly where applicable. These scopes prevent write operations while allowing you to pull data into your automations. If your workflow requires updates, use the corresponding write scopes (locations/customValues.write, locations/customFields.write) to modify resources from Zapier or other connected tools.
Authentication typically relies on a GHL API key or OAuth flow supported by the Zapier App Connector. You’ll need to grant the connector permission to access the required endpoints. Always store credentials securely and rotate keys periodically. When using OAuth, ensure your app permissions align with the endpoints you intend to call.
Yes. Writing to customValues and customFields is supported via their write endpoints. Use POST to create, PUT to update, and DELETE to remove records as needed. This enables dynamic data management directly from your automation workflows. Be mindful of validation rules and allowed value ranges to maintain data integrity.
No heavy coding is required. The combination of the GHL API and Zapier App Connector provides a no-code or low-code route to connect systems. You can map fields, configure triggers and actions, and build multi-step workflows without writing custom code. If advanced logic is needed, Zapier supports simple code steps or JavaScript actions within Zaps.
Zapier can connect with any app supported by its platform, including CRMs, form builders, marketing tools, and databases. The key is mapping GHL Custom Fields API endpoints to the destination app’s fields. This enables automatic data synchronization across your stack. Review endpoint capabilities to determine which apps and actions are best suited for your use case.
Endpoint details are documented in the Endpoints section of this page. Each endpoint shows the HTTP method, path, and typical parameters. You can copy these patterns into your Zapier actions or use them in custom automation tools. If you need examples, refer to the three best-connection patterns described above and adapt them to your workflow.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
