Use your GHL credentials with the required scope locations/customValues.readonly to access endpoints. Store tokens securely and rotate them regularly via the App Connector.
4Degrees uses standard OAuth2 with permissions for reading and writing custom data. Keep credentials secure and refresh tokens before expiry.
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, 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
Trigger when a location is updated in 4Degrees to pull the related customValues
Actions include GET /locations/:locationId/customValues and GET /locations/:locationId/customValues/:id to read values; use POST/PUT as needed to update
Methods: GET to read, POST to create, PUT to update, DELETE to remove values
Required fields include locationId and id to target a specific value
Trigger when a location’s fields change in 4Degrees
Actions include GET /locations/:locationId/customFields, GET /locations/:locationId/customFields/:id, POST /locations/:locationId/customFields, PUT /locations/:locationId/customFields/:id, DELETE /locations/:locationId/customFields/:id
Methods: GET, POST, PUT, DELETE for customFields
Key fields include locationId, id, key
Trigger events when tags are added or fields update to drive automations
Actions include GET /locations/:locationId/tags, GET /custom-field/object-key/:key, GET /custom-fields/:id, GET /locations/:locationId/customFields/:id
Methods cover retrieving tags and fields and linking them to workflows
Key fields include locationId tagId fieldId and key
No code required for basic data sync between systems
Create powerful automations without custom scripts using endpoints and webhooks
Faster setup and easier maintenance with clear endpoint mappings
Key elements include endpoints authentication triggers actions and data fields used to connect GHL to 4Degrees
A URL and an HTTP method used to perform a specific action
The process of proving identity and gaining access to API resources
A named data point stored on a resource like a location
An event that starts a workflow or data sync
Trigger on new customer creation to push relevant custom values to GHL
Sync field changes from 4Degrees to GHL to keep data in sync
Compose endpoint combos to automate cross app tasks
Obtain API credentials and authorize the App Connector to access GHL and 4Degrees
Select and map the endpoints you will use and align fields
Run tests verify data sync and enable automation in production
You can connect without coding using the App Connector. It provides ready made actions and triggers. If you want custom behavior you can still extend using the API endpoints. The community guides and templates cover common sync patterns.
Common endpoints include locations customization read only and fields endpoints. You will map locationId and ids to ensure accurate data. Use GET for reads and POST PUT for writes.
Store tokens securely use environment variables and follow best practices. Rotate credentials regularly and apply least privilege scopes.
Yes you can revert by removing webhook triggers and deleting created values in GHL or 4Degrees. Keep a log of changes.
Latency depends on the plan but typically near real time for webhooks and within seconds for API polling.
Yes real time updates are supported via webhooks where available supported endpoints may push changes instantly.
Logs appear in the App Connector dashboard and in the API response body. Errors are surfaced with codes and messages for troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
