NationBuilder
Manage NationBuilder people, lists, events, donations and tags for campaigns, nonprofits and advocacy groups.
About
NationBuilder ships in the w6w first-party pack. It declares 23 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.nationbuilder- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Marketing · Commerce & Payments
Overview
NationBuilder is a CRM and organizing platform for campaigns, nonprofits and advocacy groups, built around one shared record of every person a nation has ever touched — a “signup” in NationBuilder’s own vocabulary, exposed here as a person. This app puts the daily loop of running a nation behind a workflow: create, look up, update and delete people; group them into lists and move people on and off a list in bulk; tag and untag them; and log a contact attempt (a canvass call, a door knock, a text) against a person’s record.
Events round out the organizing side — creating and listing events and RSVPing a person to one — and donations cover the fundraising side, creating and listing gifts against a person’s record. Custom fields can be listed so a workflow can populate a nation’s own configured fields correctly instead of guessing at what has been set up.
Every nation runs on its own {slug}.nationbuilder.com subdomain, so the nation is chosen at connect time, not baked into the app, and both of NationBuilder’s own documented ways in are offered: the public OAuth 2.0 flow (the only supported way to run against production, but gated behind either NationBuilder’s Certified Developer program or an Enterprise/Network-plan nation) and a short-lived personal API token from the control panel’s Developer settings, for a quick connection to a nation whose owner already has one.
Deliberately out of scope: NationBuilder’s fundraising pages, petitions, surveys, path/automation builders, imports, voter-file fields, memberships, precincts, ballots and elections, and its own website/CMS surfaces. Each is its own large surface, and none of it is the daily loop of managing people, lists, events, donations and tags a workflow actually touches.
Build with NationBuilder
Three routes to the same 23 actions. The Workflow tab is generated from NationBuilder'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.
Log a Contact Attempt
contact-log-create Record a contact attempt (a call, door knock, text, etc.) against a person's record. This is NationBuilder's "contact" resource, distinct from the person record itself.
Create Event
event-create Create an event. Creates a new public page for it (needs a Site ID) unless an existing Page ID is given.
Tag Person
person-tag-add Apply an existing tag to a person. Use `tag-list` or `tag-create` for the tag ID.
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 NationBuilder's real ids.
{
"manifestVersion": "2",
"name": "nationbuilder-example",
"steps": [
{
"id": "contact-log-create",
"uses": {
"app": "io.w6w.nationbuilder",
"action": "contact-log-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"signupId": "<signupId>"
}
}
]
}Here are some of the things you can do
-
Log a Contact Attempt
performcontact-log-create -
List Custom Fields
searchcustom-field-list -
Create Donation
performdonation-create -
Get Donation
readdonation-get -
List Donations
searchdonation-list
+18 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 NationBuilder, 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 NationBuilder. 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-log-create",
payload: {
signupId: "<value>",
// contactMethod: "<value>",
// contactStatus: "<value>",
// content: "<value>",
// pcInCents: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action contact-log-create --payload '{"signupId":"<value>"}'Give an AI agent NationBuilder — without giving it NationBuilder'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.nationbuilder#contact-log-create",
"input": {
"signupId": "<signupId>"
}
}
}
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 NationBuilder 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
NationBuilder'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. NationBuilder itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
NationBuilder declares its own checks, so its health is a property of the app rather than something the host guesses at.
NationBuilder platform status
Component status from status.nationbuilder.com, including the API component and the third-party services (Stripe, PayPal, Authorize.net, Facebook, Dropbox) NationBuilder itself depends on.
API rate-limit headroom
Per-10-second per-token allowance remaining, read off the RateLimit-* headers. A separate per-IP limit applies too and is not visible here.
Nation subdomain reachable
Unauthenticated request to this connection's nation subdomain. A 401 passes — it proves the nation is serving; credential validity is the auth:* check's job.