To authorize Snapshots API in GHL, create an API key in Snapshots API with the saas/location.read scope, then paste it into your GHL connection settings and save.
In ActiveCampaign, generate an API token or use OAuth, then connect it in GHL so requests to Snapshots API can be authenticated and authorized.
GET /locations — Retrieve location data. This endpoint is used to pull location information into ActiveCampaign.
Trigger: when a new location is added via Snapshots API.
Actions: create or update a contact field and subscribe the contact to a relevant list.
GET /locations
Key fields: location_id, name, address, region
Trigger: location update in Snapshots API.
Actions: update contact fields in ActiveCampaign and adjust segmentation.
GET /locations/{id}
Key fields: location_id, updated_at, status
Trigger: a new region is created in Snapshots API.
Actions: start an onboarding or regional campaign in ActiveCampaign.
GET /locations?region_id={region_id}
Key fields: region_id, region_name
Automate data flow without custom code.
Keep contact data up-to-date automatically.
Improve targeted campaigns with real-time location data.
Definitions for API endpoints, triggers, actions, and fields used to connect Snapshots API to ActiveCampaign.
A URL path exposed by the API used to perform actions or retrieve data.
An event in Snapshots API that starts an automation in ActiveCampaign.
A task executed in ActiveCampaign as a response to a trigger.
A data point stored on a contact or lead that can be used in automations.
Create segments in ActiveCampaign from Snapshots API location data to target region-specific campaigns.
Use webhooks to push updates to contacts when location records change.
Trigger onboarding sequences when a new location is added.
In Snapshots API, create an API key with saas/location.read scope, then copy the key.
Enter credentials in the GHL integration setup and test connectivity.
Run a test to ensure data is syncing to ActiveCampaign as expected.
You connect by provisioning API credentials in Snapshots API and adding them to the GHL connection. Ensure the scope saas/location.read is granted. Once connected, you can test by fetching /locations and verifying data appears in ActiveCampaign. The setup is designed to be straightforward and code-free.
No heavy coding is required. The integration uses standard triggers and actions that map to ActiveCampaign workflows. If you use OAuth, token refresh is handled by the platform. Basic API key handling is sufficient for most setups.
The primary endpoint used is GET /locations to retrieve location data. You can map this data to ActiveCampaign fields and lists as needed. If you need more endpoints, you can extend the mapping later in the GHL connection.
To test the connection, use the Test Connection feature in the GHL setup or perform a controlled fetch of /locations. Check for a valid response and verify that the data appears in ActiveCampaign as expected in the mapped fields.
Typically you will sync location_id, name, and region fields. Map these to corresponding ActiveCampaign contact fields or custom fields to enable precise segmentation and automation.
Data privacy depends on how you configure credentials and scopes. Keep API keys secure, limit the scope to saas/location.read, and comply with your organization’s data policy and applicable laws.
Yes. You can use ActiveCampaign automations to react to Snapshots API events, such as new locations or location updates. This enables real-time engagement based on location data.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
