Authenticate requests to the GHL Custom Fields API using your API token. Store credentials securely in Zapier and rotate keys regularly.
Rankr relies on secure OAuth 2.0 tokens or API keys to authorize access to endpoints. Keep credentials in a vault and never expose them in public workflows.
GET /locations/:locationId/customValues; GET /locations/:locationId/customValues/:id; POST /locations/:locationId/customValues; PUT /locations/:locationId/customValues/:id; DELETE /locations/:locationId/customValues; 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
Trigger: a new or updated custom value in GHL
Action: create or update the matching record in Rankr
Method paths: GET /locations/:locationId/customValues and POST /locations/:locationId/customValues
Key fields: locationId, id, name, value, updatedAt
Trigger: newly created or updated customFields in GHL
Actions: map fields to Rankr and update related records
Endpoint usage: GET /locations/:locationId/customFields and POST /locations/:locationId/customFields
Trigger: field value changed in GHL
Actions: push updated values to Rankr via the custom fields endpoints
Endpoints: GET /custom-fields/:id and GET /custom-field/object-key/:key
Key fields: id, key, value
Rapid automation without writing code
Visual workflow builder makes mappings simple and transparent
Scales across locations and numerous custom fields with ease
Key elements include endpoints, authentication, data mapping, triggers, and actions. The process: securely store credentials, select endpoints, create Zapier zaps, test thoroughly, and deploy.
A secret key used to authenticate requests to the GHL Custom Fields API.
A unique identifier for a GHL location where custom values and fields live.
A specific value assigned to a custom field for a given location.
A specific API route you call to perform actions like read, create, update, or delete.
Set up a zap that creates or updates Rankr records whenever a GHL custom value is added or changed.
Pull multiple fields from GHL, enrich Rankr profiles, and trigger downstream workflows.
Schedule nightly batch syncs to reconcile differences between GHL and Rankr records.
Collect your GHL API token and Rankr OAuth details, then store securely.
Choose the endpoints you need and define field mappings in Zapier.
Run end-to-end tests, verify data flow, then turn on automation.
No coding is required. Zapier provides a visual editor to connect GHL endpoints to Rankr actions. You can configure triggers, actions, and field mappings without writing code. For advanced scenarios, you can still insert small scripts, but most users achieve their goals with no code. The key is to define clear data mappings and test thoroughly before automating.
For a basic setup, you’ll typically need endpoints to read custom values and optionally read or write custom fields. Start with GET /locations/:locationId/customValues and POST /locations/:locationId/customValues to create values. Add GET/POST for customFields as needed. Map fields in Zapier so data flows from GHL to Rankr.
Use API tokens or OAuth credentials and store them in Zapier’s secured vault. Rotate tokens regularly and limit scopes to the minimum required. Never embed credentials in public zaps or version control. Consider using environment-based credentials for different environments (dev, staging, prod).
Yes. You can map multiple fields by creating a mapping template in Zapier. Each field from GHL can be copied to a corresponding field in Rankr. For many-to-one mappings, consider creating a composite field or using a formatter step to shape data before sending it to Rankr.
Common pitfalls include mismatched field types, incorrect locationId values, and stale credentials. Always validate endpoints with a direct API call first, then mirror the response structure in Zapier. Keep your mappings consistent across environments.
If you need more help, check the official docs for the GHL Custom Fields API, explore Zapier templates for GHL integrations, or contact Rankr support for best-practice guidance and examples tailored to your setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
