Manage FreshBooks clients, invoices, expenses, time entries and projects.
FreshBooks ships in the w6w first-party pack. It declares 19 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
io.w6w.freshbooksFreshBooks brings core accounting and invoicing data into a workflow — clients, invoices, expenses, logged time and projects. Client and invoice actions cover the standard create-read-update loop, and a dedicated Send Invoice action moves a draft invoice into FreshBooks’ Sent state (or emails it directly), matching how FreshBooks itself gates an invoice from accounting reports and client visibility until it is sent. Expense and time entry actions let a workflow record costs and logged hours as they happen, and project actions expose the projects those expenses and time entries roll up to.
FreshBooks spreads its REST surface across three API domains on one host: an accounting domain (clients, invoices, expenses) scoped to a legacy account id, and separate timetracking/projects domains scoped to a newer business id — neither id is on the OAuth token itself, so this app resolves and records both right after authorizing, the same way it would if FreshBooks exposed one shape instead of two. Create and update actions accept FreshBooks’ own field names directly (via an Additional fields / Fields JSON escape hatch), so more of what FreshBooks’ API supports on a resource is reachable without the action surface needing to enumerate every possible field.
This app deliberately leaves out estimates, credits, payments, taxes, bills, vendors, staff/team management, reports, webhooks and invoice attachments, focusing on the core client, invoice, expense, time-tracking and project operations most workflows need first.
Three routes to the same 19 actions. The Workflow tab is generated from FreshBooks'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.
invoice-create Create a draft invoice for a client. Invoices are created in "Draft" status — use "Send Invoice" to mark it sent.
invoice-send Mark a draft invoice as sent, or email it to a list of recipients. Draft invoices are not visible to the client or counted in reports until sent.
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 FreshBooks's real ids.
{
"manifestVersion": "2",
"name": "freshbooks-example",
"steps": [
{
"id": "client-get",
"uses": {
"app": "io.w6w.freshbooks",
"action": "client-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"clientId": "<clientId>"
}
}
]
}client-get client-create client-list client-update expense-create +14 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 FreshBooks, 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 FreshBooks. 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: "client-get",
payload: {
clientId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action client-get --payload '{"clientId":"<value>"}' Give an AI agent FreshBooks — without giving it FreshBooks'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.freshbooks#client-get",
"input": {
"clientId": "<clientId>"
}
}
}
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 FreshBooks 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.
FreshBooks'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. FreshBooks itself is MIT, and the runtime that executes it is source-available (FSL).
FreshBooks declares its own checks, so its health is a property of the app rather than something the host guesses at.
Atlassian Statuspage rollup for status.freshbooks.com, with per-component detail. Unauthenticated and unsigned.