Xero
Manage Xero contacts, invoices, bank transactions, items and accounts.
About
Xero ships in the w6w first-party pack. It declares 13 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.xero- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Finance & Accounting
Overview
Xero brings core accounting data into a workflow — contacts, invoices, bank transactions, the chart of accounts and inventory items. Contact and invoice actions cover the standard create-read-update loop, letting a workflow keep customer records current and generate or amend invoices as a business process requires. Bank transaction actions read transaction history for reconciliation, while account and item actions expose the chart of accounts and product catalog invoices and transactions reference.
Because a Xero connection can be authorized for more than one organization, the app resolves and records which one a given connection acts on right after authorizing, so every subsequent action reaches the correct set of books automatically. Create and update actions accept Xero’s own field names directly, so the full breadth of what Xero’s accounting API supports on an invoice or contact is reachable without the action surface needing to enumerate every possible field.
This app deliberately leaves out credit notes, purchase orders, quotes, payments, manual journals, reports and file attachments, focusing on the core contact, invoice, bank transaction and reference-data operations most workflows need first.
Build with Xero
Three routes to the same 13 actions. The Workflow tab is generated from Xero'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.
List Bank Transactions
bank-transaction-list List spend and receive money transactions against a bank account.
Update Invoice
invoice-update Update an existing invoice's fields — most commonly its Status (e.g. to AUTHORISED).
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 Xero's real ids.
{
"manifestVersion": "2",
"name": "xero-example",
"steps": [
{
"id": "bank-transaction-get",
"uses": {
"app": "io.w6w.xero",
"action": "bank-transaction-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"bankTransactionId": "<bankTransactionId>"
}
}
]
}Here are some of the things you can do
-
Get Bank Transaction
readbank-transaction-get -
List Accounts
readaccount-list -
List Bank Transactions
readbank-transaction-list -
Create Contact
performcontact-create -
Get Contact
readcontact-get
+8 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 Xero, 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 Xero. 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: "invoice-create",
payload: {
type: "<value>",
contactId: "<value>",
lineItems: "<value>",
// additionalFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action invoice-create --payload '{"type":"<value>","contactId":"<value>","lineItems":"<value>"}'Give an AI agent Xero — without giving it Xero'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.xero#bank-transaction-get",
"input": {
"bankTransactionId": "<bankTransactionId>"
}
}
}
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 Xero 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
Xero'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. Xero itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Xero declares its own checks, so its health is a property of the app rather than something the host guesses at.
Xero platform status
Atlassian Statuspage rollup for status.xero.com, with per-component detail. Unauthenticated and unsigned.
API rate-limit headroom
Per-minute, per-day and app-wide allowances remaining, read off Xero's X-*Limit-Remaining headers on a GET /Organisation probe.