Authenticate SaaS API using OAuth with a focused scope and store tokens securely for reuse in Zapier App Connector.
The App Connector uses OAuth 2.0 or token based methods to securely authorize access to SaaS API resources.
Endpoint1 GET /oauth/installedLocations; Endpoint2 oauth.write; Endpoint3 POST /oauth/locationToken; Endpoint4 saas/location.write; Endpoint5 PUT /update-saas-subscription/:locationId; Endpoint6 POST /enable-saas/:locationId
Trigger when a new location is installed or when a location token is refreshed
Actions include fetching installedLocations and obtaining a locationToken to store tokens for future calls
GET /oauth/installedLocations; POST /oauth/locationToken
locationId, accessToken, refreshToken, expiresIn, scope
Trigger when a location is created or a subscription needs updating
Actions include saas/location.write to create locations and update-saas-subscription to manage plans
POST /saas/location.write; PUT /update-saas-subscription/:locationId
locationId, subscriptionId, planId
Trigger when a location needs to enable SaaS access
Actions include enabling SaaS via enable-saas
POST /enable-saas/:locationId
locationId, status
Fast setup with OAuth and no code required to connect your SaaS API to Zapier
Centralized access to endpoints and smooth management of tokens and subscriptions
Scalable automations for Act-On workflows with minimal maintenance
A quick glossary of core terms used in this guide to help you implement the integration smoothly
OAuth is a standard authorization framework that enables secure token based access to APIs without exposing user credentials
A location token authorizes access to a specific SaaS location and is issued via the OAuth flow
An API endpoint is a URL path that performs an action or returns data in the SaaS API
A subscription represents the active service plan for a SaaS location and can be updated via the API
Automatically create a SaaS location in SaaS API when a user signs up in Zapier App Connector and assign a default subscription
Set up a token renewal flow to avoid auth disruption and securely store refresh tokens
Create dashboards to monitor endpoint health, rate limits and failed syncs
Authorize SaaS API in the App Connector and save the access token
Connect installedLocations locationToken and saas endpoints to your Zapier workflows
Create Zaps that trigger on location updates and subscription changes to automate tasks in Act-On
The SaaS API supports a scoped OAuth flow to grant access securely without exposing credentials. Use the oauth.readonly scope for read operations and elevate as needed for write actions. Store tokens securely and rotate them regularly to maintain access. If you run into token expiry, use the locationToken endpoint to refresh tokens.
Authentication and token management are performed via the endpoints in the list: GET /oauth/installedLocations for discovery, POST /oauth/locationToken to obtain a token, and saas/location.write along with update-saas-subscription to manage locations and subscriptions.
Location tokens expire and should be refreshed using the locationToken endpoint. Implement a refresh strategy and securely store tokens. Build error handling that retries on expiry with minimal user impact.
Yes. The saas location write and update subscription endpoints allow no code configurations inside the App Connector to create and manage SaaS locations and their plans. Use Zapier to map fields and automate workflows without writing code.
No code means you can connect SaaS API quickly, monitor endpoints visually, and automate common tasks such as enabling SaaS or updating subscriptions without writing code. This reduces time to value and makes maintenance easier for teams.
The endpoint list and parameters are described in this page. Use the endpoint names and path placeholders to configure your Zapier actions and triggers. Validate with test calls in the App Connector.
Test by using the App Connector test actions, simulate token expiry, and verify each endpoint returns expected data. Use sandbox environments when available and monitor logs for failures.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
