---
name: zapier-embed-guide
description: >
  Use when asking about Powered by Zapier versus White Label, the Zapier Trigger Inbox API,
  connection webhooks, partner billing for Zapier automation, or which embed option fits a partner product.
  Explains the embed options and routes to canonical documentation.
license: MIT
compatibility: >
  Applies to docs.zapier.com public documentation.
metadata:
  author: zapier
---

# Zapier embed guide

Zapier has two ways to put automation inside a partner product: Powered by Zapier (embedded Zap editor, Workflow API, sponsored automation) and White Label (Zapier connections and automations under your own brand).

## Critical rules

- **Powered by Zapier accounts:** Users still need a Zapier account, which is free. Sponsorship covers task costs so users do not need a paid plan. Zapier must enable sponsorship for your account.
- **White Label billing and accounts:** You are billed per task. Your users do not create a Zapier account and Zapier never bills them. Zapier still appears as the requester on third-party OAuth consent screens.
- **White Label access:** White Label is in limited access. Contact whitelabel@zapier.com to learn more.
- **White Label tokens:** Your backend exchanges a partner-signed JWT for an access token, which stays server-side. A connect token lasts 6 minutes, works once, and is the only token you pass to the browser.
- **Powered by Zapier tokens:** Endpoints use a user access token (OAuth 2.0), an app access token, or only a client ID.

## Which option fits

| If you want... | Use |
|---|---|
| Pre-built or pre-filled workflows, or a Zap editor inside your product | Powered by Zapier |
| Users to create and manage Zaps through the Workflow API | Powered by Zapier or White Label embedded workflows |
| Real-time events from 9,000+ apps, pulled from a queue | White Label, Trigger Inbox API |
| Notice when a user's app connection is scheduled to expire | White Label, connection webhooks |
| Actions called from your backend on connected accounts | White Label, embedded actions |
| An AI agent that calls tools through Zapier MCP or the SDK | White Label, AI agent connections |

## Canonical documentation

- [Powered by Zapier overview](https://docs.zapier.com/powered-by-zapier): embed approaches
- [Sponsor user automation](https://docs.zapier.com/powered-by-zapier/sponsor-user-automation/getting-started): who pays and who needs an account
- [Powered by Zapier authentication](https://docs.zapier.com/powered-by-zapier/authentication/getting-started): access token types
- [White Label getting started](https://docs.zapier.com/white-label/getting-started): surfaces, billing, token flow
- [White Label partner onboarding](https://docs.zapier.com/white-label/implementation/partner-onboarding): JWKS URL, callback URLs, credentials
- [White Label token exchange](https://docs.zapier.com/white-label/implementation/token-exchange): access and connect tokens
- [Trigger Inbox API](https://docs.zapier.com/white-label/trigger-inbox/what-is-trigger-inbox-api): real-time events
- [Connection webhooks](https://docs.zapier.com/white-label/connection-webhooks/what-is-connection-webhooks): connection expiry events

## Related skills

- For Zapier MCP in AI clients, use `zapier-mcp-guide`.
- For the SDK, use `zapier-sdk-guide`.