To access custom values and fields, use API keys or OAuth tokens with the required scopes for locations and values.
Ensure your Active Knocker account has the needed permissions to read and write data via the Custom Fields API and that your integration uses secure headers.
GET /locations/:locationId/customValues — Retrieve all custom values for a location.\nGET /locations/:locationId/customValues/:id — Retrieve a single custom value.\nPOST /locations/:locationId/customValues — Create a new custom value.\nPUT /locations/:locationId/customValues/:id — Update a custom value.\nDELETE /locations/:locationId/customValues/:id — Delete a custom value.\nGET /locations/:locationId/customFields — List custom fields for a location.\nGET /custom-fields/:id — Retrieve a specific custom field.\nGET /custom-field/object-key/:key — Retrieve field by key.\nPOST /locations/:locationId/customFields — Create a new custom field.\nGET /locations/:locationId/tags — List tags for a location.\nGET /locations/:locationId/customFields/:id — Retrieve a specific custom field by id.
Trigger: Need to fetch current custom values to map fields into Active Knocker workflows
Actions: Use GET /locations/:locationId/customValues to sync; update Active Knocker contact fields for campaigns.
GET /locations/:locationId/customValues
Key fields: id, locationId, value, valueType
Trigger: When you need to adjust how fields appear in Active Knocker dashboards
Actions: POST /locations/:locationId/customFields and PUT /locations/:locationId/customFields/:id
POST /locations/:locationId/customFields
Key fields: id, locationId, fieldKey, label, valueType
Trigger: Organize data by tags to enable segmenting in Active Knocker workflows
Actions: GET /locations/:locationId/tags and GET /locations/:locationId/customFields to enrich metadata
GET /locations/:locationId/tags
Key fields: tags list, tagId
Fast integration without coding: connect endpoints via REST and automate data flows.
Real-time data syncing to keep your Active Knocker dashboards up to date.
Flexible mapping of custom values to contact fields to tailor campaigns.
A quick glossary of essential terms to help you implement the integration confidently.
Individual data points stored per location, such as preferences or notes, exposed via the Custom Values API.
A specific account location within GHL where views, fields, and values are stored for sync with Active Knocker.
Structured fields that can be created and updated for each location to capture data used in campaigns.
Labels assigned to locations to enable grouping and targeting in Active Knocker workflows.
When a new custom value is created for a location, automatically push matching fields in Active Knocker to keep campaigns in sync.
Use location tags to drive targeted flows in Active Knocker, updating lists as tags change.
Export key custom fields to a report-ready format for executives reviewing campaign performance.
Obtain an API key or OAuth token with the locations/customValues.readonly and related scopes.
Link GET and POST endpoints to your Active Knocker sequences to drive data in real time.
Test data flows, enable logging, and set up alerts for sync issues.
First, the API exposes endpoints to read and manage values and fields for each location. Use endpoints like GET /locations/:locationId/customValues and GET /locations/:locationId/customFields to retrieve current data. Second, secure your requests with proper authentication and the right scopes.
Reading and writing endpoints include GET /locations/:locationId/customValues, POST /locations/:locationId/customValues, PUT /locations/:locationId/customValues/:id, and the corresponding customFields variants. These endpoints let you keep Active Knocker in sync with GHL data.
Authentication typically uses API keys or OAuth tokens. Include the token in the Authorization header and request the correct scope (locations/customValues.readonly or locations/customFields.write, etc.).
Yes. By polling or using webhooks (where supported) you can keep data refreshed in Active Knocker as changes occur in GHL.
No heavy coding required. Use REST calls and mapping rules to sync values and fields to Active Knocker.
You can map custom values and fields like location notes, customer preferences, and tags to corresponding Active Knocker fields for richer campaigns.
Plan a consistent naming scheme, document field keys, and implement error handling and retries to ensure reliable data flows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
