Authenticate your Snapshots API connection in GHL using an API key with saas/location.read scope. This ensures AccessAlly can read location data securely.
In AccessAlly, configure the new GHL connection by entering the API endpoint, client credentials, and selecting the saas/location.read scope to enable location data access.
– GET /locations — fetches location data used in AccessAlly mappings
Trigger: when a location is created or updated in Snapshots API
Actions: create or update location-related records in AccessAlly, map fields to the right AccessAlly fields
GET /locations
Key fields: location_id, location_name, address
Trigger: when a location status changes
Actions: tag updates and segment membership in AccessAlly
GET /locations
Key fields: location_id, status
Trigger: on every sync run
Actions: log transfers in AccessAlly for compliance
GET /locations
Key fields: location_id, synced_at
Automates data sync to eliminate manual updates
Speeds up onboarding by pulling live location data into AccessAlly
Provides a unified view of locations within AccessAlly workflows
Understand endpoints, triggers, actions, and field mappings used when connecting the Snapshots API to AccessAlly.
A defined URL in the GHL API used to retrieve or modify data, e.g., GET /locations.
An authorization framework that lets apps access data without sharing user credentials.
A URL that receives real-time notifications about events from an API.
Aligning fields from the Snapshots API to matching AccessAlly fields for accurate data sync.
Push changes to AccessAlly as they happen, minimizing lag.
Use location data to segment customers in AccessAlly.
Prebuilt automations for common location workflows.
In GHL, generate an API key with saas/location.read scope.
Enter the endpoint URL and credentials into AccessAlly.
Run a test fetch and map fields to ensure data aligns.
The Snapshots API is a RESTful API that exposes location data. It allows apps like AccessAlly to read location details and incorporate them into workflows. This API is designed for fast reads and reliable delivery of location-related information.
Typically no coding is required when using the GHL App Connector to link Snapshots API with AccessAlly. You’ll use a straightforward API key setup, scopes, and field mappings. If your use case is complex, light scripting can be added, but it isn’t necessary for standard data sync.
The required scopes include saas/location.read. This enables reading location data from Snapshots API. If you need additional data access, request extra scopes from your GHL admin.
Use the Connect/Test feature in the AccessAlly connector to initiate a test fetch. Review the response payload, status codes, and sample records to confirm a successful connection.
Yes. Many common fields can be mapped automatically via built-in mappings. You can also adjust mappings manually to align with your AccessAlly schema.
Sync frequency is configurable in the connector settings. Options typically include real-time or hourly updates depending on your plan.
Logs are available in the connector’s activity panel, showing successes, errors, timestamps, and payload samples for troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
