Givebutter
Manage Givebutter campaigns, contacts, transactions, funds, households and webhooks — the nonprofit fundraising and donor-CRM platform.
About
Givebutter ships in the w6w first-party pack. It declares 43 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.givebutter- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Commerce & Payments · Communication
Overview
Givebutter is a nonprofit fundraising platform: campaigns (donation pages, peer-to-peer, ticketed events), the transactions and recurring plans they collect, and the contacts (donor CRM) and households behind them. This app covers that core surface end to end — full CRUD on campaigns, contacts (including tag management), funds and webhooks; creating and updating transactions for offline/manual gift entry; and read access to the resources the API exposes read-only: payouts, pledges, recurring plans, tickets and outbound messages.
Givebutter’s own API reference disagrees with the API’s actual wire behavior in two ways this app works around rather than repeats: every documented error response is shown as a flat {"message": ...} object, but a live 401 actually answers {"error": {"message": "Unauthorized"}} — this app’s error formatter reads both shapes. And the Rate Limits page states 500 requests/minute, but every live response measured during development carried x-ratelimit-limit: 200 — the quota health check reports the header, not the doc.
One more thing worth knowing before scripting against resource paths directly: {campaign} and {fund} path parameters accept only the numeric id. A slug or any other non-numeric value in that position doesn’t reach the API layer at all — it falls through to Givebutter’s public marketing site, which answers its own branded 404 HTML page instead of a JSON error. This app’s actions always take the numeric id.
Build with Givebutter
Three routes to the same 43 actions. The Workflow tab is generated from Givebutter'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.
Delete Campaign
campaign-delete Delete a campaign. Givebutter refuses this with a 409 if the campaign has already raised money.
Create Contact
contact-create Create a contact. Individual contacts need first_name/last_name; company contacts need company_name.
Add Tags to Contact
contact-tags-add Add one or more tags to a contact, keeping any tags it already has.
Remove Tags from Contact
contact-tags-remove Remove one or more tags from a contact, leaving any others untouched.
Sync Tags for Contact
contact-tags-sync Replace a contact's full tag set with exactly the tags given here — unlike Add/Remove, any tag not listed is dropped.
List Messages
message-list List outbound messages (emails/texts sent from a campaign) on the connected account.
Create Transaction
transaction-create Record a transaction (typically an offline/manual gift) against the account.
Update Transaction
transaction-update Update a transaction's editable fields. Only fields you set are changed.
Create Webhook
webhook-create Register a webhook. Only url is documented required, but a webhook with no events subscribed will never fire.
Update Webhook
webhook-update Update a webhook. Givebutter documents url and events as required on this call.
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 Givebutter's real ids.
{
"manifestVersion": "2",
"name": "givebutter-example",
"steps": [
{
"id": "campaign-create",
"uses": {
"app": "io.w6w.givebutter",
"action": "campaign-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"type": "<type>",
"title": "<title>",
"slug": "<slug>"
}
}
]
}Here are some of the things you can do
-
Create Campaign
performcampaign-create -
Get Campaign
readcampaign-get -
List Campaigns
readcampaign-list -
Update Campaign
performcampaign-update -
Create Contact
performcontact-create
+38 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 Givebutter, 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 Givebutter. 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-create",
payload: {
type: "<value>",
title: "<value>",
// subtitle: "<value>",
// description: "<value>",
// goal: "<value>",
// end_at: "<value>",
slug: "<value>",
// beneficiary_id: "<value>",
// timezone: "<value>",
// currency: "<value>",
// settings: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-create --payload '{"type":"<value>","title":"<value>","slug":"<value>"}'Give an AI agent Givebutter — without giving it Givebutter'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.givebutter#campaign-create",
"input": {
"type": "<type>",
"title": "<title>",
"slug": "<slug>"
}
}
}
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 Givebutter 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
Givebutter'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. Givebutter itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Givebutter declares its own checks, so its health is a property of the app rather than something the host guesses at.
Givebutter API status
The API component on status.givebutter.com's real feed (givebutter.statuspage.io) — not the Dashboard/Campaigns web components, which can degrade independently of the API.
API rate-limit headroom
Requests remaining in the current window, read off x-ratelimit-limit/x-ratelimit-remaining. The vendor's Rate Limits doc page states 500 req/min; every response measured live carried a limit of 200 — this check reports the header, not the doc.