Embedded triggers/actions
This use case is for products with an existing workflow builder or orchestration layer that want Zapier to execute individual action steps via API. This White Label use case differs from the generic Powered by Zapier docs:- You do not need to have a public Zapier integration.
- You can run actions across Zapier’s catalog (you are not limited to actions “owned by” your integration).
What you need
- an access token (server-side)
- a connection identifier for the user’s connected app account
High-level flow
- Token exchange: your backend exchanges a partner-signed JWT for an access token.
- Check existing connections: list the user’s connections for the app and reuse a valid connection when possible.
- Request a connect token (if needed): when you need to connect or reconnect, exchange the access token for a connect token. Include
resourceset to the Connect UI URL you will open (https://connect.zapier.com/to/{app}), matching Token exchange. - Connect if needed: launch Connect UI with the connect token to create/reconnect a connection and store the resulting connection identifier.
- Run the action: create an action run with the access token + connection identifier + action inputs.
- Poll for completion: poll run status until complete, then return results to your UI.
Create and retrieve Action Runs
To run an action, make aPOST request to the Action Runs endpoint.
API reference: /v2/action-runs
Create an Action Run (request example)
Retrieve an Action Run result (request example)
API reference: /v2/action-runs/Related guides
- Token exchange
- Connection flow
- AI agent connections & automations — MCP tool-calling for agents