Donorbox
List campaigns, donations, recurring plans, donors, events, tickets and purchases on Donorbox, the nonprofit fundraising platform.
About
Donorbox ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.donorbox- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Customer Relationship Management
Overview
Donorbox is an online donation and fundraising platform built for nonprofits: campaigns (donation pages and peer-to-peer drives), the one-time and recurring donations they collect, donor records, and ticketed events with the tickets and purchases they sell. This app covers Donorbox’s full documented API v1 surface: list campaigns, donations, recurring plans, donors, events, tickets and event ticket purchases, each with the vendor’s own filters (donor identity, campaign, date range, donation amount, payment status), ordering and pagination.
The API is read-only end to end — Donorbox’s own reference documents no create, update or delete endpoint for any of these resources, only GET. Authentication is HTTP Basic: the organization’s login email as the username, and a paid API key (Donorbox charges $17/month for API access, separate from the platform subscription) as the password.
Two things worth knowing before scripting against this API directly: a list response is a bare JSON array with no {"data": [...]} envelope and no pagination metadata beyond the page you asked for, and every response — even an unauthenticated one — carries live rate-limit headers the vendor’s own docs never mention.
Build with Donorbox
Three routes to the same 7 actions. The Workflow tab is generated from Donorbox'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 Event Ticket Purchases
purchase-list List event ticket purchases on the connected Donorbox organization.
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 Donorbox's real ids.
{
"manifestVersion": "2",
"name": "donorbox-example",
"steps": [
{
"id": "campaign-list",
"uses": {
"app": "io.w6w.donorbox",
"action": "campaign-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>",
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
List Campaigns
searchcampaign-list -
List Donations
searchdonation-list -
List Donors
searchdonor-list -
List Events
searchevent-list -
List Plans
searchplan-list
+2 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 Donorbox, 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 Donorbox. 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: "campaign-list",
payload: {
// id: "<value>",
// name: "<value>",
// page: "<value>",
// per_page: "<value>",
// order: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-list --payload '{}'Give an AI agent Donorbox — without giving it Donorbox'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.donorbox#campaign-list",
"input": {
"id": "<id>",
"name": "<name>"
}
}
}
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 Donorbox 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
Donorbox'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. Donorbox itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Donorbox declares its own checks, so its health is a property of the app rather than something the host guesses at.
Donorbox API status
The grouped 'Donorbox API' component on status.donorbox.org, covering the Campaigns, Donations, Donors, Events, Plans and Tickets APIs this app reads — not the separate Stripe/PayPal payment-gateway or Donorbox App dashboard components.
API rate-limit headroom
Requests remaining in the current window, read off x-ratelimit-limit/x-ratelimit-remaining — undocumented in Donorbox's own reference but present on every response measured live, including an unauthenticated one.