Wave
Manage customers, products, invoices, estimates and money transactions in Wave Accounting over Wave's GraphQL API.
About
Wave ships in the w6w first-party pack. It declares 21 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.wave- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Finance & Accounting
Overview
Wave Financial’s free small-business accounting and invoicing platform, reached entirely through a single GraphQL endpoint — there is no REST surface at all. This app covers the spine a workflow author actually reaches for: customers (list, get, create, edit, delete), products/services (list, create), the chart of accounts (list, for picking the income/expense account a product posts to), invoices (list, get, create, email to a customer) and estimates (list, get, create, email to a customer), plus recording a money transaction (a bank/credit-card deposit or withdrawal, categorized against one or more accounts) the same way Wave’s own transaction entry screen does. An escape-hatch action runs any GraphQL query or mutation directly, reaching the much larger schema (sales taxes, vendors, invoice payments, invoice reminders, estimate deposits and acceptance history) that the named actions don’t model.
Good for turning a completed job or booking into a Wave invoice automatically, keeping a Wave customer list in sync with a CRM, generating estimates from an external quoting tool, or logging externally-processed payments as Wave transactions for bookkeeping.
Build with Wave
Three routes to the same 21 actions. The Workflow tab is generated from Wave'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 Accounts
account-list List the chart of accounts for a business, optionally filtered by type/subtype.
List Businesses
business-list List the Wave businesses the connected user belongs to. Every other action needs one of these ids.
Create Customer
customer-create Create a customer under a business. Fails loudly on Wave's `inputErrors`.
Delete Customer
customer-delete Permanently delete a customer. Wave rejects this with an `inputErrors` entry if the customer has existing invoices, estimates or transactions.
Edit Customer
customer-edit Update specific fields of an existing customer. Unset fields are left unchanged.
List Customers
customer-list List customers for a business, optionally filtered by email or modified date.
Create Estimate
estimate-create Create an estimate for a customer. Give a single product line via `Product ID`/`Quantity`, or a full line-item array via `Items` for multi-line estimates.
List Estimates
estimate-list List estimates for a business, optionally filtered by customer, status or number.
Run GraphQL Query
graphql-query Send an arbitrary query or mutation to Wave's GraphQL API. Returns `data`. Mutations must select and check `didSucceed`/`inputErrors` themselves.
Create Invoice
invoice-create Create an invoice for a customer. Give a single product line via `Product ID`/`Quantity`, or a full line-item array via `Items` for multi-line invoices.
List Invoices
invoice-list List invoices for a business, optionally filtered by customer, status or number.
Create Money Transaction
money-transaction-create Record a deposit or withdrawal on a bank/credit-card account, categorized against one or more accounting accounts. The line-item total must balance the anchor amount.
Create Product
product-create Create a product or service. Provide an income account to sell it, an expense account to buy it, or both.
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 Wave's real ids.
{
"manifestVersion": "2",
"name": "wave-example",
"steps": [
{
"id": "account-list",
"uses": {
"app": "io.w6w.wave",
"action": "account-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"businessId": "<businessId>"
}
}
]
}Here are some of the things you can do
-
List Accounts
searchaccount-list -
Get Business
readbusiness-get -
List Businesses
searchbusiness-list -
Create Customer
performcustomer-create -
Edit Customer
performcustomer-edit
+16 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 Wave, 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 Wave. 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-list",
payload: {
businessId: "<value>",
// types: "<value>",
// subtypes: "<value>",
// isArchived: "<value>",
// page: "<value>",
// pageSize: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action account-list --payload '{"businessId":"<value>"}'Give an AI agent Wave — without giving it Wave'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.wave#account-list",
"input": {
"businessId": "<businessId>"
}
}
}
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 Wave 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
Wave'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. Wave itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Wave declares its own checks, so its health is a property of the app rather than something the host guesses at.
Wave platform status
Atlassian Statuspage rollup for status.waveapps.com, with per-component detail (Web Application, Accounting, Invoicing, Payments, Payroll, Receipts Processing, Mobile Application). Unauthenticated and unsigned.