Manage contacts and sales invoices in Moneybird, the Dutch online accounting service.
Moneybird ships in the w6w first-party pack. It declares 11 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
io.w6w.moneybirdMoneybird is a Dutch online accounting and invoicing service used by freelancers and small businesses across the Netherlands and Belgium. Every request goes to one fixed host (moneybird.com) but is scoped to one of the credential’s administrations — the bookkeeping entity id that shows up in Moneybird’s own web app URL — so a Connection resolves and remembers the first accessible administration at connect time, the same one-Connection-one-tenant model this pack already uses for Xero and Jira.
This app covers the two resources most integrations need first: contacts (customers and suppliers) and sales invoices, including the line items, sending an invoice by email or Peppol, and registering a payment against it via Moneybird’s current (non-deprecated) payments endpoint. A read action for the account’s own list of administrations is included so a workflow can discover or confirm which bookkeeping entity a token reaches before addressing it explicitly.
Three routes to the same 11 actions. The Workflow tab is generated from Moneybird'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.
administration-list List the Moneybird administrations (bookkeeping entities) this connection can access.
contact-update Update fields on an existing contact. Only the fields provided are changed.
sales-invoice-create Create a draft sales invoice with one or more line items. Does not send it — use Send Sales Invoice for that.
sales-invoice-get Retrieve one sales invoice by its Moneybird id, including line items and totals.
sales-invoice-list List sales invoices in an administration, filtered by state and/or period.
sales-invoice-payment-create Register a payment against a sales invoice.
sales-invoice-pdf-get Resolve a sales invoice's short-lived, pre-signed PDF download URL, without fetching the file's bytes.
sales-invoice-send Send a sales invoice by email, Peppol, or mark it as sent manually.
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 Moneybird's real ids.
{
"manifestVersion": "2",
"name": "moneybird-example",
"steps": [
{
"id": "contact-get",
"uses": {
"app": "io.w6w.moneybird",
"action": "contact-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}contact-get administration-list contact-create contact-list contact-update +6 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 Moneybird, 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 Moneybird. 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: "contact-get",
payload: {
// administrationId: "<value>",
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action contact-get --payload '{"id":"<value>"}' Give an AI agent Moneybird — without giving it Moneybird'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.moneybird#contact-get",
"input": {
"id": "<id>"
}
}
}
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 Moneybird connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
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.
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.
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.
Moneybird'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. Moneybird itself is MIT, and the runtime that executes it is source-available (FSL).
Moneybird declares its own checks, so its health is a property of the app rather than something the host guesses at.