The SaaS API uses OAuth with a scoped access. In this integration, we’ll request oauth.readonly to view locations and tokens and then obtain a location token for actions.
Configure OAuth in the Zapier App Connector to securely exchange access and refresh tokens and to refresh credentials automatically.
GET /oauth/installedLocations; oauth.write; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
When a location is created or updated in SaaS API, trigger a Zap to update downstream apps.
Update the SaaS subscription in the target app using locationId and subscription data.
PUT /update-saas-subscription/:locationId
locationId, subscriptionStatus, planId
Activation of a location in SaaS API triggers a workflow in Zapier.
Call the enable endpoint to turn on SaaS features and reflect status in the app.
POST /enable-saas/:locationId
locationId, enabled
A new location token is issued and should be stored securely for API calls.
Fetch locationToken via OAuth and reuse it for authenticated requests; rotate tokens as needed.
POST /oauth/locationToken
locationId, locationToken
Automate SaaS location provisioning without writing code.
Test, map fields, and deploy workflows entirely in Zapier UI.
Centralized OAuth management improves security and refresh handling.
Understand terms used in this guide: OAuth, Installed Location, Location Token, locationId, subscription, and activation.
OAuth is an open standard for delegated access that lets Zapier App Connector securely connect to SaaS API resources without sharing passwords.
A per-location access token used to authenticate API requests for a specific SaaS location.
A SaaS location installed in the system, representing a customer site with its own settings and subscriptions.
The plan or tier assigned to a SaaS location, including its status and renewal details.
Trigger a workflow when a new location is installed to automatically provision subscriptions.
Run daily checks to ensure SaaS subscriptions match records and alert on discrepancies.
Automatically refresh location tokens before expiry and securely store credentials.
Begin by granting OAuth permissions for installed locations.
Choose the endpoints you need (locations, token, subscription updates) and configure field mappings.
Run a test in Zapier to verify data flow and then activate automation.
To connect, you’ll configure OAuth in the Zapier App Connector and authorize access to installed locations. Ensure your SaaS API subscription is active and that the required scopes are granted. The connector will securely exchange tokens and store them for use in automations. In production, monitor token lifetimes and refresh tokens as needed to maintain uninterrupted automation.
Readonly access is sufficient for viewing installed locations and tokens in most workflows. If you need to create or modify subscriptions, you’ll request write access via the OAuth flow and ensure the app has the necessary permissions. Follow least-privilege practices when configuring scopes. Regularly review permissions and rotate tokens to protect your data.
Location tokens authenticate requests for a specific SaaS location. Treat tokens like passwords and store them securely using a secrets manager. Implement a token rotation strategy to reduce risk of exposure. Use the token in API calls for location-specific actions and monitor token usage for anomalies.
Yes. Use a sandbox or test environment to validate changes before going live. In Zapier, you can map fields and run test data without impacting real customers. Once tests pass, move the integration to production with confidence. Document any schema or field mapping changes to avoid surprises in production.
Disabling a location will stop SaaS features for that location and may pause related automations. You may need to re-enable or re-provision the location to resume workflows. Consider adding notifications for admins when a location is disabled so remedial actions can be taken quickly.
No-code automation is supported via Zapier triggers and actions, letting you connect SaaS API endpoints to your workflows without writing code. You can set up triggers, map fields, and test data visually. If you need custom logic, you can extend the workflow with additional steps in Zapier or use webhooks for advanced scenarios.
Endpoint details are provided in onboarding docs and this guide. Key endpoints include installedLocations, locationToken, update-saas-subscription, and enable-saas, plus others as needed for your use case. Refer to the CSV-provided endpoint list in this page for exact paths and required parameters.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
