Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.zapier.com/llms.txt

Use this file to discover all available pages before exploring further.

White Label is currently in limited access. Contact whitelabel@zapier.com to learn more.
Zapier White Label lets you embed Zapier’s automation capabilities directly into your product. Your end users connect their apps and run automations without ever leaving your UI, creating a Zapier account, or receiving a bill from Zapier. You control the experience. Zapier handles third-party authentication and action execution in the background.

​
How billing works

You (the partner) are billed per task executed. Your end users have no direct relationship with Zapier and are never billed by Zapier. You can price and package the automation capability however works for your business.

​
Pick your surface

White Label supports three product surfaces. You can build one or all of them depending on your use case.
SurfaceWhat your users doGood fit if…
Embedded triggers/actionsConnect an app account, then your product calls actions or listens to triggers via APIYou want to orchestrate automations yourself and just need app connectivity
Embedded workflowsCreate and manage trigger-action workflows (Zaps) inside your productYou want users to build their own automations without leaving your app
AI agent connections & automationsConnect apps so an AI agent can call tools via Zapier MCP or SDKYou’re building an AI product and need it to act on third-party apps

​
Where Zapier branding shows up (and what you can control)

Two surfaces show Zapier or third-party branding during the connection flow:
  1. Connect UI (Zapier-hosted)
    • What users see: the hosted Connect UI where they sign in to the third-party app and grant access
    • What you control: the UI can be customized to match your design system so it feels native inside your product
    Example of a customized Connect UI
  2. Third-party OAuth consent screens (Google, Slack, etc.)
    • What users see: the consent screen from the third-party app
    • What’s important: the consent screen will show that Zapier is requesting access to the user’s third-party app account
    Example of a third-party OAuth consent screen This screen is owned by the third-party app, so branding and wording are not fully controllable.

​
Key concepts

  • Partner-signed JWT: your backend’s signed assertion of “this is user X in tenant/workspace Y”.
  • JWKS URL: a public endpoint where Zapier fetches your public keys to verify JWT signatures.
  • Access token (Bearer): used server-side to call Zapier APIs (list connections, run actions, poll results).
  • Connect token: short-lived token used client-side to open the Connect UI (often obtained by exchanging an access token).
  • Connection identifier: durable ID returned after Connect completes; you store it and use it to run actions later.

​
Get started

  1. Partner onboarding — configure your JWKS URL, callback URLs, and JWT expectations with Zapier; receive your client credentials
  2. Token exchange — exchange credentials for an access token, then a connect token
  3. Connection flow — open Connect UI (popup or redirect) and capture the connection identifier
  4. Pick your surface: Embedded triggers/actions · Embedded workflows · AI agent connections & automations