Zapier is an automation platform that connects apps and moves data between them with automated workflows called Zaps. Integrating Zapier with Frontegg lets your application list Zaps, search their run history, turn Zaps on and off, browse the apps available in Zapier, and read the connected user's profile on behalf of your users — all through Frontegg's integration layer (Zapier Workflow API v2). Zapier authenticates with OAuth 2.0.
Prerequisites
Prerequisites
- A Zapier account
- A public integration published in Zapier's App Directory through the Zapier Developer Platform. Your Client ID and Client Secret are only available after you have published your app as a public integration in Zapier's App Directory.
Zapier issues OAuth credentials from the Developer Platform, under your published integration's Embed → Settings page. That page provides the Client ID and Client Secret, and is where you register the redirect URI that Zapier returns users to after they authorize access.
Sign in to the Zapier Developer Platform, open your published integration, and go to Embed → Settings.
On the Embed → Settings page:
- Under Redirect URIs, add your Frontegg Redirect URL:
https://YOUR_MCP_GATEWAY_URL/integration-callback - Under Credentials, copy the Client ID and Client Secret.
Keep your Client Secret safe
Keep your Client Secret safe
The Client Secret grants access to your account through the API. Treat it like a password and never expose it in client-side code or commit it to version control. Regenerating the secret invalidates the previous one.
Once you have your credentials, configure the integration in the Frontegg portal:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Zapier.
- Enter the Client ID and Client Secret.
- Click Save.
Zapier uses the following scopes:
| Scope | Description |
|---|---|
zap:all | Read all Zaps owned by the authenticated user |
zap:runs | Read Zap run history |
zap:pause | Enable or disable Zaps |
zap | Read Zaps that use your integration |
profile | Read profile information for the authenticated user |
Keep your credentials secure
Keep your credentials secure
Never share or commit your Client Secret to version control.