Planning Center
Manage People, Giving, Calendar and Check-Ins records in Planning Center, the church/ministry management suite.
About
Planning Center ships in the w6w first-party pack. It declares 6 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.planningcenter- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Calendar & Scheduling · Finance & Accounting
Overview
Planning Center is the suite of church and ministry management products — People, Services, Calendar, Giving, Check-Ins, Groups, Publishing and Registrations — sharing one directory of people and one credential per organization. This app connects a workflow to that shared directory over Planning Center’s own JSON-API-conformant REST surface.
People actions search, read and create profiles in the church directory — the record every other Planning Center product hangs off of. Giving actions list donations with their date, amount and payment status, for reconciliation or reporting workflows. Calendar actions list scheduled event occurrences with real start/end times, not just the recurring event definitions they belong to. Check-Ins actions list attendance records for a service or event, without surfacing the emergency-contact and medical-notes fields the same records can carry for children’s check-in.
A single Personal Access Token (a Client ID + Secret pair from a Planning Center Developer Account) authenticates across every product a user has access to — there is no per-product scope to configure separately.
Build with Planning Center
Three routes to the same 6 actions. The Workflow tab is generated from Planning Center'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 Check-Ins
list-check-ins List attendance check-in records, optionally filtered by event or date.
List Event Occurrences
list-event-instances List scheduled event occurrences (with actual start/end times) from the Calendar module.
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 Planning Center's real ids.
{
"manifestVersion": "2",
"name": "planningcenter-example",
"steps": [
{
"id": "create-person",
"uses": {
"app": "io.w6w.planningcenter",
"action": "create-person",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"firstName": "<firstName>"
}
}
]
}Here are some of the things you can do
-
Create Person
performcreate-person -
Get Person
readget-person -
List Check-Ins
searchlist-check-ins -
List Donations
searchlist-donations -
List Event Occurrences
searchlist-event-instances
+1 more action 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 Planning Center, 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 Planning Center. 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: "create-person",
payload: {
firstName: "<value>",
// lastName: "<value>",
// birthdate: "<value>",
// gender: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-person --payload '{"firstName":"<value>"}'Give an AI agent Planning Center — without giving it Planning Center'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.planningcenter#create-person",
"input": {
"firstName": "<firstName>"
}
}
}
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 Planning Center 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
Planning Center'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. Planning Center itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Planning Center declares its own checks, so its health is a property of the app rather than something the host guesses at.