Cloud-based subscription management platform that enables businesses to launch and monetize subscription services.
Zuora currently provides 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Create Invoice
Create a standalone invoice.
Find Customer Account
Retrieves account based on name.
Find Product Rate Plan
Retrieves product rate plan with charges.
Find Product
Retrieves product based on sku.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Use a change in Coherence to run a supported Zuora action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Invoice
Combine Zuora with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
A Coherence workflow starts
Finishes with
Create Invoice, then preserve the outcome in Coherence
The exact authentication fields depend on Zuora. The workflow structure stays straightforward:
Authorize the Zuora account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Zuora or provide a complementary trigger or action.
Zuora currently provides 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Zuora currently lists 0 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Zuora triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
