To begin, authorize the SaaS API in your GHL app using OAuth. The SaaS API requires the oauth.readonly scope for read-only access and oauth.write for updating data. You will be redirected to the consent screen, then exchange the authorization code for access and refresh tokens.
In Zapier App Connector, start the OAuth flow to obtain an access token that allows the app to act on SaaS API on behalf of the user. Store the refresh token securely and renew tokens as needed to keep automations running.
GET /oauth/installedLocations — fetch installed locations; oauth.write — permission to write; POST /oauth/locationToken — generate a location token; saas/location.write — update SaaS location; PUT /update-saas-subscription/:locationId — update subscription for a location; POST /enable-saas/:locationId — enable SaaS for a location. Additional endpoints (7–53) are documented in the API reference and may be used as needed.
Trigger: Retrieve installedLocations to seed your workflows.
Actions: Use the returned location data to map fields in Zapier tasks and trigger downstream automations.
GET /oauth/installedLocations
locationId, locationName, status
Trigger: Grant write permissions to update location data and handle configs.
Actions: Update tokens and location records via oauth.write to keep data in sync.
oauth.write
token, scope, expiry
Trigger: Generate a new locationToken for authentication.
Actions: Obtain and store locationToken to maintain authorized sessions.
POST /oauth/locationToken
locationId, token, expiresAt
Benefit: Build powerful automations without writing code.
Benefit: Real-time data flow between SaaS API and your tools.
Benefit: Scalable workflows that grow with your business.
This glossary covers OAuth scopes, API endpoints, tokens, triggers, and actions, and explains how they work together to connect SaaS API with Zapier App Connector.
OAuth is an open standard for access delegation that allows apps to obtain limited access to user accounts on an HTTP service without sharing credentials.
An API endpoint is a specific URL path exposed by a service that performs a defined operation.
A token is a digital credential that grants access to resources for a scoped period.
Scope defines what actions an access token allows within the API.
Use GET /oauth/installedLocations to trigger onboarding sequences when a new location is detected and map data into your onboarding tasks.
Automatically push location updates to your CRM via Zapier workflows and keep records current.
Set up a token renewal workflow to keep sessions valid without manual re-authentication.
Begin by granting OAuth scopes for SaaS API in Zapier App Connector.
Choose endpoints such as installedLocations and locationToken, then map fields to Zapier actions.
Run tests, validate the token flow, and deploy automations.
OAuth is an open standard that lets SaaS apps delegate access to Zapier App Connector without sharing user credentials. It uses scopes to limit what the app can do and a consent flow to grant permissions. In this setup you request oauth.readonly for read access and oauth.write for updates, then store access and refresh tokens securely. Implementation is straightforward: configure the OAuth flow in Zapier App Connector, authorize the SaaS API, and handle token exchanges and renewals as part of your automation.
Paragraph 1: To get started you need the endpoints and scopes. For authentication and token management, begin with GET /oauth/installedLocations and POST /oauth/locationToken, with oauth.readonly and oauth.write as needed. Paragraph 2: After authorization, review additional endpoints like saas/location.write and update-saas-subscription for broader management, and ensure the Zapier App Connector is configured to refresh tokens automatically.
Paragraph 1: Zapier supports refresh tokens in OAuth projects. When an access token expires, use the refresh token to obtain a new access token without requiring the user to re-authenticate. Paragraph 2: Securely store the refresh token and implement automatic token renewal in your Zapier integration to maintain uninterrupted automations.
Paragraph 1: Yes. No-code automations let you build flows using triggers, actions, and searches without writing code in Zapier. This is ideal for prototyping integrations with SaaS API. Paragraph 2: Start with simple flows like pulling installed locations and creating a basic update to a location, then expand to multi-step automations as you gain confidence.
Paragraph 1: GET /oauth/installedLocations returns a list of locations installed for the account. Paragraph 2: Expect fields such as locationId, locationName, and status, which you can map to CRM fields or alert notifications.
Paragraph 1: If a token expires, your app will receive an authentication error. The recommended path is to use the refresh token flow to obtain a new access token. Paragraph 2: If no refresh token is available, re-run the OAuth flow to re-authorize and regain access.
Paragraph 1: The glossary and terms are included in this article and the official docs. Look for sections labeled Key Terms and Glossary for quick references. Paragraph 2: You will find definitions for OAuth, API Endpoint, Token, and Scope to help you understand the integration and how the pieces fit together.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
