Zuora
Manage customer accounts, subscriptions, invoices, payments and orders in Zuora, across every Zuora region and cloud.
About
Zuora ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zuora- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Finance & Accounting
Overview
Zuora is a subscription billing and monetization platform. This app puts the core billing objects into a workflow: list, read, create and update customer accounts; list, read and create subscriptions; list and read invoices and payments; and create and read orders for anything beyond a single subscription’s lifecycle.
Zuora runs each tenant in one of ten hosts spanning three regions (US, EU, APAC) and, for the US, two clouds, plus developer/central and API sandboxes per region — this app’s Auth method routes every request through the tenant’s own host rather than assuming one region, because a credential minted against one Zuora data centre is unknown to any other.
Every list action goes through Zuora’s Object Query API rather than the older per-resource endpoints, because Object Query is the one part of the v1 API with a real, generic list operation (cursor pagination, field.OP:value filters) that isn’t gated behind an optional feature like Invoice Settlement or the legacy Order Metrics add-on.
Deliberately left out: standalone invoice creation/posting, payment creation/refunds/transfers, credit and debit memos, bill runs, usage/mediation, and every order-action type beyond creating a brand-new subscription — all real, documented Zuora endpoints, left out because covering them accurately would mean re-deriving a large fraction of Zuora’s object model rather than a scoped, verifiable action set. order-create’s subscriptions field is deliberately raw JSON rather than a typed form for the same reason — see that action’s own documentation for exactly what it accepts.
Build with Zuora
Three routes to the same 14 actions. The Workflow tab is generated from Zuora's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Account
account-get Retrieve a customer account's basic info, contacts and billing/payment setup.
Create Order
order-create Create an order — subscriptions and the order actions applied to them. Requires the Orders feature to be enabled on the tenant.
Create Subscription
subscription-create Create a new subscription with a single product rate plan for an existing account.
List Subscriptions
subscription-list List subscriptions, with optional Object Query filter/sort clauses.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Zuora's real ids.
{
"manifestVersion": "2",
"name": "zuora-example",
"steps": [
{
"id": "account-create",
"uses": {
"app": "io.w6w.zuora",
"action": "account-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>",
"currency": "<currency>",
"billToFirstName": "<billToFirstName>"
}
}
]
}Here are some of the things you can do
-
Create Account
performaccount-create -
Get Account
readaccount-get -
List Accounts
readaccount-list -
Update Account
performaccount-update -
Get Invoice
readinvoice-get
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Zuora, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Zuora. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "account-create",
payload: {
name: "<value>",
currency: "<value>",
billToFirstName: "<value>",
billToLastName: "<value>",
// billToWorkEmail: "<value>",
// billToCountry: "<value>",
// accountNumber: "<value>",
// crmId: "<value>",
// batch: "<value>",
// autoPay: "<value>",
// paymentTerm: "<value>",
// billCycleDay: "<value>",
// notes: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action account-create --payload '{"name":"<value>","currency":"<value>","billToFirstName":"<value>","billToLastName":"<value>"}'Give an AI agent Zuora — without giving it Zuora's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.zuora#account-create",
"input": {
"name": "<name>",
"currency": "<currency>",
"billToFirstName": "<billToFirstName>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Zuora connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Zuora's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Zuora itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zuora declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zuora platform status
The regional API cloud this connection uses, read from Zuora's own status page.