To authorize the SaaS API within the GHL connection, obtain an access token with the oauth.readonly scope, then use it to call allowed endpoints. Store tokens securely and refresh before expiry to maintain uninterrupted access.
In the ActiveTrail app context, complete the OAuth handshake to grant permissions to the SaaS API. This establishes a trusted connection and ensures tokens are managed safely within the ActiveTrail environment.
Endpoints in use include: GET /oauth/installedLocations to list locations; POST /oauth/locationToken to obtain a location token; saas/location.write to configure a location; PUT /update-saas-subscription/:locationId to update a subscription; POST /enable-saas/:locationId to enable SaaS for a location. Additional endpoints (7–17) are documented for future enhancements as needed.
Trigger: user authorizes the app in GHL and a location token is exchanged to establish the connection
Actions: exchange authorization code for access token, store credentials securely, and begin location data calls
Paths: GET /oauth/installedLocations; POST /oauth/locationToken
Key fields: locationId, access_token, refresh_token, scopes
Trigger: select a specific ActiveTrail location and grant access
Actions: enable SaaS for the chosen location and update the subscription as needed
Paths: PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Fields: locationId, subscriptionStatus, planId
Trigger: token expiry prompts refresh flow
Actions: refresh tokens, retry API calls, monitor expiry
Paths: POST /oauth/locationToken
Fields: access_token, refresh_token, expires_in, scopes
Fast setup with no code required and guided screens to connect SaaS API to ActiveTrail
Automation and data sync without custom development, reducing time to value
Secure token handling and centralized access control for all authenticated calls
Overview of elements like endpoints, OAuth flow, tokens, locations, triggers and actions that power the integration between GHL and ActiveTrail
OAuth is a standard authorization framework that grants access to resources without sharing user credentials
Location refers to a specific ActiveTrail account or workspace connected via the SaaS API
Access tokens authorize API requests within granted scopes and expire after a set period
Endpoint is a specific URL path used by the API to perform an action
Keep ActiveTrail subscriber lists in sync with SaaS API changes to ensure data accuracy across platforms
Trigger ActiveTrail automations when events occur in the SaaS API for real time workflows
Build conditional paths based on tokens and location data to tailor customer journeys
Register the SaaS API in GHL, obtain client_id and client_secret, and set redirect_uri to your app URL
Define the endpoints and request scopes such as oauth.readonly to control access
Run test calls, verify tokens, and monitor location data flow
The SaaS API connection links ActiveTrail to the GHL powered platform using OAuth. This ensures only authorized calls are made to the endpoints. You can revoke access and manage permissions from the GHL app settings.
OAuth scopes determine what the integration can access. In this setup the oauth.readonly scope is requested. Token lifetimes and refresh tokens are used to maintain access.
Tokens can be refreshed using the locationToken endpoint. Monitor expiry and set up automation to refresh before expiry.
Yes. You can connect multiple ActiveTrail locations or accounts by creating separate connections per location.
Key endpoints include GET /oauth/installedLocations, POST /oauth/locationToken, PUT /update-saas-subscription/:locationId, and POST /enable-saas/:locationId.
Yes, no code options exist via the app connector with guided screens and defaults.
If OAuth failures occur check redirect URI, client credentials, scopes and token status. Review logs in GHL and ActiveTrail.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
