Integration
Connect Planning Center to Apexverify
When something happens in Planning Center, your agent does the next thing in Apexverify. 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 Apexverify 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 Apexverify
Triggers and actions 6 triggers ยท 6 actions
Trigger
New DonationTriggers when a donation is received.
Trigger
New Form SubmissionTriggers when a form submission is received.
Trigger
New List ResultTriggers when the specified List has a new Person added.
Trigger
New PlanTriggers when a new plan is created in the selected service type.
Trigger
New ProfileTriggers when a new Profile is created.
Trigger
New Workflow CardTriggers when a new workflow card is created in a specific workflow.
Action
Add batchUploads a list of email addresses or phone numbers as a new verification batch in Apexverify, and returns the new batch's id.
Action
Get batch detailsGet detailed metadata/results summary for a batch by id. Endpoint: GET /v1/batch/{batch_uuid}/details.
Action
Get batch statusGet the processing status of a batch by id. Endpoint: GET /v1/batch/{batch_uuid}.
Action
List batchesList all verification batches on the account. Endpoint: GET /v1/batch.
Action
Normalize formatNormalize/standardize the format of a data item (e.g. phone/email) without full verification. Endpoint: POST /v1/format.
Action
Update batch parametersChanges the verification settings on an Apexverify batch before it is launched, such as the contact type, target country, audience and caching rules.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.