Integration
Connect Planning Center to WebAsk
When something happens in Planning Center, your agent does the next thing in WebAsk. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Planning Center and WebAsk to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Planning Center and WebAsk
Triggers and actions 7 triggers ยท 7 actions
Trigger
New DonationTriggers when a donation is received.
- New Form Submission
Triggers when a form submission is received.
- New List Result
Triggers when the specified List has a new Person added.
- New Plan
Triggers when a new plan is created in the selected service type.
- New Profile
Triggers when a new Profile is created.
- New Workflow Card
Triggers when a new workflow card is created in a specific workflow.
Trigger
Send ResponsesTriggers when send survey responses anywhere.
- Create survey
Create a new survey in a WebAsk folder.
- Delete survey
Delete a survey/quiz by id. DELETE /quiz/{id}.
- Get survey
Get a single survey/quiz by id, including its questions/widgets. GET /quiz/{id}.
- Get survey summary
Get aggregated summary/analytics for a survey's responses. GET /quiz/{id}/summary.
- List responses
List answers/responses submitted to a survey. GET /quiz/{id}/answers.
- List surveys
List all surveys/quizzes in the workspace. GET /quiz (supports pagination/filtering per WebAsk API v3 docs).
- List workspaces
List the account's workspaces (used to select where surveys/folders live). GET /service/workspaces.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.