Authenticate with the Snapshots API using the GHL credentials and grant the saas location.read scope to access location data
Authorize Act-On to access your GHL account by creating a connected app and granting necessary permissions
GET /locations Retrieve all locations in a single call
Trigger on demand fetch of locations from Snapshots API
Actions map location fields to Act-On records and push location data
Trigger with location filters such as type and region
Actions apply filters transform data and map to Act-On fields
GET /locations?filter={criteria}
Key fields location_type region status
Trigger scheduled bulk sync of locations
Actions batch upsert location records into Act-On
GET /locations/bulk
Key fields location_id last_updated
Rapid data synchronization between Snapshots API and Act-On
Automated workflows without coding
Scalable location management across campaigns
Definitions of common terms used to describe endpoints data flow and processing
An area or venue within your Snapshots API data set
An event that starts a workflow or data pull
Aligning API fields with Act-On fields for correct data transfer
Processing many records in a single operation
Use webhooks to push location changes to Act-On
Trigger Act-On campaigns when location data changes
Sync large lists of locations in batches
Generate API credentials in Snapshots API and connect in Act-On
Enable GET locations and optional filters
Run tests and monitor data flow after deployment
The Snapshots API provides access to location data for use in workflows and campaigns. You can pull locations using GET /locations and map fields to Act-On. This integration helps automate targeting based on location.
Authentication uses standard app connections between GHL and Act-On using the Snapshots API credentials. Ensure the saas location.read scope is granted.
Currently GET /locations is supported in this guide. You can add filters to refine results. More endpoints can be added as needed.
Yes. Use sandbox or test accounts to validate calls. Verify data mapping before moving to production.
API credentials are found in the Snapshots API dashboard. Create a new app connection to Act-On to obtain client id and secret.
No code options are available via the connector between GHL and Act-On. You can configure steps and mappings in the UI.
If you need help, contact Rankr support or open a ticket with the integration team.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
