Z

zapier.com

Zapier is an automation platform that connects thousands of third-party apps so users and teams can run workflows, actions, and AI-assisted tasks across their software stack. It also offers embeddable APIs and MCP-based access for developers building automation or agent experiences into their own products.

9 integrations · MCP · REST · CLI

Zapier exposes a Streamable HTTP MCP server, several HTTP APIs on api.zapier.com and nla.zapier.com (Workflow API, White Label APIs, Connection Webhooks, and NLA), plus two Node-based CLIs (`zapier` and `zapier-sdk`).

discovered 1d ago
MCP servers2
REST · OpenAPI5
CLI2
Credentials
OAuth 2.0oauth2
OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Zapier MCP connection tokenbearerGet token ↗

For unsupported MCP clients or your own code, create a server at mcp.zapier.com and generate a connection token there. Zapier shows the token once; store it immediately and treat it like a password. The docs recommend sending it as an Authorization: Bearer header, with URL ?token= only as a fallback.

Zapier Workflow API client ID and client secretbasicGet credentials ↗

Publish your app as a public integration in Zapier's App Directory, then open the Zapier Developer Platform and go to Embed → Settings → Credentials to copy your Client ID and Client Secret. These are used to obtain Workflow API tokens, and the Client ID is also used directly on some V1 endpoints.

Zapier Workflow API user access tokenoauth2$ zapier-sdk login

Acquired by the CLI — running zapier-sdk login opens the auth flow and stores the credential.

Zapier Workflow API app access tokenoauth2_ccSet up OAuth ↗

Get your app's Client ID and Client Secret from Zapier Developer Platform under Embed → Settings → Credentials, after publishing your app as a public integration. Exchange them with the client-credentials grant at POST https://zapier.com/oauth/token/ to obtain a bearer token for endpoints that act on the app's own behalf.

Zapier White Label partner-signed JWTjwtGet key ↗

White Label partners complete onboarding with Zapier, configure a JWKS URL and JWT claim mapping, and receive Zapier client credentials. Your backend then signs a short-lived JWT (for example with sub, tenant/workspace claim, iss, aud=connect.zapier.com, iat, exp, nbf) using a private key whose public key is published at your JWKS URL. Zapier verifies this JWT during token exchange.

Zapier Platform CLI deploy keybearer$ zapier login

Acquired by the CLI — running zapier login opens the auth flow and stores the credential.

Zapier Connection Webhooks bearer tokenoauth2_ccSet up OAuth ↗

After Zapier provisions your dedicated Connection Webhooks client ID and secret, use the client-credentials grant against POST https://zapier.com/oauth/token to obtain a bearer token for the Connection Webhooks API. This is partner-account level auth, not a per-user JWT exchange.

conventions · 3/8 published

Publish these signals → /publishing