Grant access to SaaS API resources from Zapier App Connector. The integration uses oauth.readonly to read installed locations and subscriptions.
Connect Zapier App Connector to your SaaS account so it can manage locations, tokens, and subscriptions on your behalf.
Key endpoints: GET /oauth/installedLocations; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId. Additional endpoints may be configured as needed.
Trigger: When a new location is added to SaaS API, automatically provision it in Zapier and start related workflows.
Actions: Read installedLocations, generate a locationToken with /oauth/locationToken, then write location settings with saas/location.write.
Methods: GET /oauth/installedLocations; POST /oauth/locationToken; saas/location.write
Key fields: locationId, locationName, status
Trigger: SaaS subscription changes should propagate to Zapier automations.
Actions: Update subscription with PUT /update-saas-subscription/:locationId; optionally enable or deactivate with POST /enable-saas/:locationId as needed.
Methods: PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Key fields: locationId, plan, status
Trigger: When tokens are required for a location or service.
Actions: Retrieve a token with POST /oauth/locationToken, then activate with POST /enable-saas/:locationId.
Methods: POST /oauth/locationToken; POST /enable-saas/:locationId
Key fields: locationId, token, status
No coding required—build, test, and deploy automations with clicks, not code.
Leverage mature endpoints and triggers to create scalable workflows quickly.
Centralized management of locations, tokens, and subscriptions in a single UI.
This section covers OAuth scope, API endpoints, locations, tokens, and subscriptions, plus how they fit into connect, test, and deploy steps.
OAuth is the authorization framework that lets Zapier App Connector access SaaS API resources on behalf of a user without sharing credentials.
An API route that performs a defined action, such as retrieving locations or updating a subscription.
A secure string used to authenticate API requests for a user or app.
A SaaS API entity representing a client site or account within the platform.
Automatically fetch installed locations and set up associated workflows when a new client is added.
Trigger updates across systems when SaaS subscriptions change.
Tokenize and enable services on demand to minimize downtime.
Grant OAuth access (scope oauth.readonly) to read locations and subscriptions.
Map endpoints such as GET /oauth/installedLocations, POST /oauth/locationToken, and saas/location.write to your Zapier workflows.
Run tests to verify token exchange and data flow, then deploy automations across your stack.
SaaS API is a cloud service that exposes endpoints for locations, tokens, and subscriptions. Connecting via Zapier App Connector lets you automate workflows without coding. The SaaS API integration is designed to be plug-and-play with pre-built triggers and actions. By linking these systems, you can automate data flow across platforms and scale your operations with confidence. The example here uses SaaS API to manage locations and their subscriptions through OAuth-enabled calls.
You’ll need OAuth-based access with at least oauth.readonly scope to read installed locations and subscription statuses. For tokenization and subscription updates, you’ll authorize app-level tokens and use endpoints like /oauth/locationToken, saas/location.write, and /update-saas-subscription/:locationId. Always follow least-privilege practices and revoke access when the integration is no longer needed.
The integration uses endpoints such as GET /oauth/installedLocations to retrieve locations, POST /oauth/locationToken to obtain tokens, saas/location.write to configure location data, PUT /update-saas-subscription/:locationId to modify subscriptions, and POST /enable-saas/:locationId to activate services. These endpoints enable provisioning, updating, and activating SaaS resources from Zapier automations.
Tokenization starts with POST /oauth/locationToken to generate a location-specific token. Once tokens are issued, you can activate services with POST /enable-saas/:locationId. The token is used to authenticate subsequent requests for that location. Testing ensures tokens have the proper scope and access before deploying automations.
Yes. Use PUT /update-saas-subscription/:locationId to reflect changes in a location’s subscription. You can also enable or disable services with POST /enable-saas/:locationId as needed to control access.
Absolutely. This integration is designed for no-code automation inside Zapier App Connector. You can create multi-step workflows, conditional logic, and interactive dashboards without writing any code, using the built-in actions and triggers.
You can view logs and debugging information within Zapier’s task history and the SaaS API’s response payloads. Use those details to verify requests, troubleshoot authorization scopes, and confirm that endpoints return expected data during tests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
