Authenticate requests using the GHL API credentials with the required scope saas/location.read to access location data.
Authorize 46elks to access Snapshots API with your app credentials and securely store tokens.
Endpoint 1: GET /locations. Other endpoints are documented in the API reference and may vary by plan.
Trigger: when a location is created or updated in 46elks, fetch and sync the latest data from Snapshots API.
Actions: map fields, create or update records in your app, and store history in Snapshots.
GET /locations
id, name, address, coordinates, last_seen
Trigger: new or updated location data in Snapshots API pushes to 46elks
Actions: upsert records, normalize fields, and alert teams on changes
GET /locations
id, external_id, status, timestamp
Trigger: location events meet thresholds or status changes
Actions: send notifications (Slack/email), start Zapier workflows, and update dashboards
GET /locations
id, event_type, timestamp, location_id
Build automations without writing a line of code.
Access real-time data from endpoints with simple, visual triggers.
Sync data across apps with no-code workflows and dashboards.
This glossary defines API, endpoint, authentication, webhook, and data mapping used in this integration.
An interface that lets software communicate and share data.
A specific URL in an API that performs a function.
A real-time data push from an app when an event occurs.
The process used to verify identity before granting access to protected resources.
Send instant alerts to Slack or email when a location changes.
Tag customers in your CRM based on their latest location.
Automate daily location activity reports and share insights.
Obtain your GHL API credentials and authorize the connection to Snapshots API.
Select GET /locations and any required endpoints in the app configuration.
Run tests, verify data mapping, and enable automations.
You can access Endpoint 1: GET /locations to fetch location data from the Snapshots API when connected to 46elks. Additional endpoints and parameters are described in the Snapshots API reference and may vary by plan. Always start with GET /locations to validate the connection. If needed, consult the API docs for endpoint availability by your subscription.
No-code integration is possible via the Zapier app connector that bridges Snapshots API and 46elks. If you need deeper customization, you can also perform API calls or use webhooks to build custom logic. The no-code path covers most common automations, while code enables advanced transformations.
Authentication uses your GHL credentials to authorize the Snapshots API connection. Exchange tokens as required and ensure the scope saas/location.read is enabled for location data access. Rotate credentials regularly and keep them secure.
By default, common fields such as id, name, location, and timestamp are mapped. You can customize field mappings in the integration settings to fit your data model. For upsert scenarios, use a unique key like id to avoid duplicates.
To test the connection, enable a sandbox or test mode, run sample GET /locations requests, and verify data is correctly mapped. Check logs for any credential or scope errors and adjust settings accordingly.
Yes, webhooks are supported to push updates to 46elks or other connected apps when events occur in Snapshots API. Configure the webhook URL in the Snapshots API settings and test with a sample event.
API documentation and usage limits are available in the Snapshots API reference. Rate limits vary by plan; monitor your quota in the dashboard and contact support if you need higher limits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
