Connect SaaS API using OAuth with the scope oauth.readonly to securely access installed locations and subscription data from Zapier App Connector.
In the Zapier App Connector, configure OAuth credentials for SaaS API, then complete the authorization to obtain an access token for API calls.
Key endpoints used by the SaaS API integration with Zapier App Connector: GET /oauth/installedLocations; OAuth scope: oauth.write; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId. Additional endpoints are available in the API reference.
Trigger: when a location is connected in Zapier, exchange a location token to establish a trusted session.
Actions: retrieve installed locations, store tokens securely, and prepare the location for further API calls.
Method Path: GET /oauth/installedLocations and POST /oauth/locationToken used during the initial setup.
Key fields: locationId, accessToken, refreshToken
Trigger: SaaS subscription changes in your backend or admin panel.
Actions: call PUT /update-saas-subscription/:locationId to reflect changes across connected tools.
Method Path: PUT /update-saas-subscription/:locationId
Key fields: locationId, subscriptionId, planId, status
Trigger: an admin enables SaaS features for a specific location.
Actions: POST /enable-saas/:locationId to turn on services.
Method Path: POST /enable-saas/:locationId
Key fields: locationId, enabled, timestamp
No-code automation lets you build workflows without writing code, using triggers and actions.
Quick onboarding for new locations through OAuth and token management keeps your team productive.
Real-time data synchronization across connected apps helps you stay up to date with minimal effort.
This glossary defines core terms and processes used in the SaaS API and Zapier App Connector integration.
OAuth is an open standard for access delegation that enables apps to act on behalf of a user without sharing credentials.
A token representing an authenticated SaaS location used to authorize API calls.
An installed location is a SaaS instance registered with SaaS API that can be accessed via the integration.
A billing plan attached to a SaaS location that can be updated via the update-saas-subscription endpoint.
Use OAuth and location tokens to auto-create user accounts and permissions across connected apps.
Push subscription changes to all tools in near real time allowing teams to react fast.
Aggregate errors from endpoints into a single dashboard for quick triage.
Create a client ID and secret in SaaS API and add them to the Zapier App Connector settings.
Complete the OAuth flow to obtain an access token and refresh token.
Map endpoints to Zapier triggers and actions and run end-to-end tests.
No coding is required to connect SaaS API with the Zapier App Connector. You can set up triggers and actions using the visual editor. This keeps integrations approachable for non-developers. If you do code, you can extend capabilities with custom scripts. The combination of OAuth and token management handles secure access automatically.
Initial access typically uses oauth.readonly to fetch data like installed locations. If you need to modify data, you will switch to oauth.write or request broader scopes. Always grant the minimum scope required for your automation. Review the API reference for exact scope options.
Location tokens are issued after you complete the OAuth flow. Zapier stores the token securely and uses it to authenticate calls to endpoints such as /oauth/locationToken and /update-saas-subscription/:locationId. If tokens expire, use the refresh token flow to obtain new tokens.
Yes. Subscriptions can be updated by calling PUT /update-saas-subscription/:locationId with the relevant locationId and subscription details. This ensures downstream tools reflect current plans. Implement error handling to retry failed updates.
Yes. You can enable SaaS per location via POST /enable-saas/:locationId. This allows selective rollout and control over which locations have active SaaS features. Monitor status changes to confirm successful enablement.
Data synchronization is near real time once tokens are valid and endpoints are invoked. The exact timing depends on your workflow design and the polling or event triggers you configure in Zapier.
Endpoint references are available in the SaaS API documentation and the Zapier App Connector integration guide. Start with the main endpoints listed in the Endpoint List, then explore additional endpoints in the API reference to extend your automation.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
