> ## 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

> Embed Zapier connections and automations into your product, under your brand.

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.

<Note>
  White Label is currently in limited access. Contact [whitelabel@zapier.com](mailto:whitelabel@zapier.com) to learn more.
</Note>

***

## 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 four product surfaces. You can build one or all of them depending on your use case.

| Surface                                                                    | What your users do                                                          | Good fit if...                                                                                                |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [**Embedded triggers**](./use-cases/embedded-triggers)                     | Subscribe to real-time events from connected apps via the Trigger Inbox API | You want your product or AI agent to react to events across 9,000+ apps without building per-app integrations |
| [**Embedded actions**](./use-cases/embedded-actions)                       | Connect an app account, then your product calls actions via API             | You want to orchestrate automations yourself and just need app connectivity                                   |
| [**Embedded workflows**](./use-cases/embedded-workflows)                   | Create and manage trigger-action workflows (Zaps) inside your product       | You want users to build their own automations without leaving your app                                        |
| [**AI agent connections & automations**](./use-cases/ai-agent-connections) | Connect apps so an AI agent can call tools via Zapier MCP or SDK            | You'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](https://cdn.zappy.app/f292fd0bf34956b84d6fffb21e8f76ce.png)

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](https://cdn.zappy.app/8c4ccc84c8ffc5e606a605a009538cbf.png)

   This screen is owned by the third-party app, so branding and wording are not fully controllable.

   This also reflects why 9,000+ app connections are available to your users immediately -- Zapier maintains the OAuth client registrations across all supported apps, so you don't have to.

***

## 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.

***

## Token flow

```mermaid theme={null}
sequenceDiagram
  participant PB as Partner Backend
  participant ZAPI as Zapier (oauth/token)
  participant FE as Your Frontend
  participant CUI as Connect UI
  participant API as Zapier APIs

  PB->>ZAPI: POST /oauth/token (partner JWT)
  ZAPI-->>PB: User Access Token
  Note over PB: Server-side only. Use for all Zapier API calls.

  PB->>ZAPI: POST /oauth/token (User Access Token)
  Note over PB,ZAPI: requested_token_type: connect-token
  ZAPI-->>PB: Connect Token (6 min, single-use)
  PB->>FE: Pass Connect Token

  FE->>CUI: Open connect.zapier.com/to/{app}?token=...
  CUI-->>FE: Connection ID (after user authorizes)
  FE->>PB: Connection ID

  PB->>API: Actions / Triggers / SDK calls
  Note over PB,API: Authorization: Bearer {User Access Token} + connection ID
```

***

## Get started

Complete these steps once, in order:

1. [Partner onboarding](./implementation/partner-onboarding) — configure your JWKS URL, callback URLs, and JWT expectations; receive your client credentials
2. [Token exchange](./implementation/token-exchange) — exchange credentials for an access token, then a connect token
3. [Connection flow](./implementation/connection-flow) — open Connect UI and capture the connection identifier

Then build your surface:

* [Embedded triggers](./use-cases/embedded-triggers) — react to real-time events from 9,000+ apps via the Trigger Inbox API
* [Embedded actions](./use-cases/embedded-actions) — run actions in connected apps from your backend
* [Embedded workflows](./use-cases/embedded-workflows) — let users build and manage Zaps inside your product
* [AI agent connections & automations](./use-cases/ai-agent-connections) — connect apps so an AI agent can call tools via MCP or SDK