> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server. # Revenue tasks in Workflow > Zuora Workflow supports Zuora Revenue beginning with the 2026.Q3.0.1 release. Revenue customers can use out-of-the-box Workflow tasks to automate operations that are available in Zuora Revenue Workbench. Zuora Workflow supports Zuora Revenue beginning with the 2026.Q3.0.1 release. Revenue customers can use out-of-the-box Workflow tasks to automate operations that are available in Zuora Revenue Workbench. The exact task names, fields, and options displayed in your tenant are the source of truth for your enabled release and configuration. ## Before you begin Confirm the following before creating a Revenue workflow: * Your tenant has Zuora Revenue enabled. * Your tenant is on the 2026.Q3.0.1 release or a later release that includes Revenue support in Workflow. * You have access to Extension Studio and Workflow. * The Revenue configuration required by the task is complete. For example, a task that applies a hold requires an applicable Revenue hold definition, and a task that releases or defers revenue requires the target performance obligation to support the operation. * You understand the accounting impact of the Revenue operation you are automating. Test workflows in a non-production tenant before enabling them in production. ## Workflow entitlement and licensing Workflow entitlements and licensing for Zuora Revenue follow the same rules as those for Zuora Billing. For customers that use both Zuora Billing and Zuora Revenue, the entitlement is 15 active workflows in total across Billing and Revenue. This entitlement is shared between the two products. It is not 15 active workflows for Billing plus 15 active workflows for Revenue. ## Supported customer configurations Workflow is supported for both OTR customers and Revenue-only customers. Workflow is not supported in the following tenant configurations: * One Billing tenant connected to multiple Revenue tenants. * A multi-entity Billing tenant connected to one Revenue tenant. ## Recommended workflow controls * Add a validation step to confirm that the source and target belong to the expected tenant, entity, book, and accounting context. * Add a failure branch that captures the Revenue error, identifiers, and workflow run ID. Do not continue to downstream mutation tasks after a failed Link/Delink operation. * Add comments where the task exposes them so the reason for the realignment is retained in the operational history. * Remember that a manual delink makes the RC ineligible for systematic grouping rules thereafter. ## Important considerations * Revenue tasks automate supported Revenue operations; they do not make every action available in the Revenue UI available as a Workflow task. * Eligibility rules configured in Revenue still apply. A task can fail or be unavailable when the target contract, POB, line, hold, book, or accounting state does not support the requested action. * A successful Workflow task does not replace Revenue approvals, accounting controls, or period-close procedures. * Use comments, approval steps, and notifications for operations that change revenue recognition, holds, allocations, or accounting data. * Review task output and run history after each production rollout. Use the task payload and Revenue identifiers to troubleshoot failures. > Zuora Workflow supports Zuora Revenue beginning with the 2026.Q3.0.1 release. Revenue customers can use out-of-the-box Workflow tasks to automate operations that are available in Zuora Revenue Workbench. ## Docs - [Use revenue tasks in Workflow](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/use-revenue-tasks-in-workflow.md): Learn how to find and configure revenue tasks in Workflow to pass revenue data through the workflow payload. - [Configure a Revenue task](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/configure-a-revenue-task.md): Configure a Revenue task by selecting it from the library, entering a descriptive name, supplying required identifiers and values, configuring optional fields, mapping outputs to downstream logic, choosing concurrency behavior, and testing with representative data. - [Register a Workflow as a Revenue background job](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/register-a-workflow-as-a-revenue-background-job.md): Register an existing Workflow as a background job in Revenue so that its inputs are saved as job parameters. - [Supported operation families](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/supported-operation-families.md): Review the Revenue Workbench operation families supported by the Revenue task library and their typical automation uses. - [Use link and delink Revenue tasks in Workflow](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/use-link-and-delink-revenue-tasks-in-workflow.md): Use the Revenue Link/Delink task in Workflow to automate supported Revenue Workbench realignment actions at the revenue-contract (RC), performance-obligation (POB), transaction-line, or charge level. - [Workflow role access privileges in Revenue](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/workflow-role-access-privileges-in-revenue.md): Access to Workflow from the Revenue user interface is controlled through Revenue UI privileges and Platform Workflow access permissions. These controls serve different purposes. - [Example Workflow patterns for Revenue operations](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/revenue-tasks-in-workflow/example-workflow-patterns-for-revenue-operations.md): Review example Workflow patterns for Revenue holds, contract relationships, performance obligations, released lines, and operation monitoring.