> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Zuora Workflows with Experience Builder

> Use Experience Builder to trigger callout-based Zuora Workflows from buttons by configuring a Generic HTTP integration and per-workflow callout settings.

Use Experience Builder to trigger callout-based Zuora Workflows from buttons by configuring a Generic HTTP integration and per-workflow callout settings.

Experience Builder can start a callout-triggered Zuora Workflow from a button by using a Generic HTTP integration and a POST query.

Zuora Workflow integration Experience Builder can trigger Zuora Workflows through explicit, per-workflow setup.

## Callout-triggered workflows

A callout-triggered workflow starts when an external request is sent to the workflow endpoint. Experience Builder can send this request when a user selects a configured button on an Experience Builder page.

The request uses a Generic HTTP integration and the credentials configured for the workflow callout. It identifies the workflow by its workflow ID and supplies the input parameters that the workflow requires.

## Other considerations

Experience Builder cannot trigger the following workflow types or behaviors:

* Run on demand, scheduled, billing event, or UI action workflows from an experience. These workflow types are available only from Zuora internal tools or the Zuora Billing UI.

* Workflows that do not have per-workflow callout setup. The callout must be enabled, the correct workflow ID must be configured, authentication must be established, and the workflow inputs must be mapped.

* Zuora REST API workflows through the built-in Zuora REST data source. Callout authentication that uses an API token or basic authentication is separate from OAuth.

* Batch workflows by using callouts. Callouts support only near real-time workflows.

* Built-in workflow discovery, status polling, or approval task pages. To support these use cases, you must create custom HTTP queries and workflow tasks.

There is no built-in "Run Workflow" integration.