Integration
Connect Planning Center to EOSL
When something happens in Planning Center, your agent does the next thing in EOSL. 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 EOSL 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 EOSL
Triggers and actions 6 triggers ยท 4 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.
Action
Find part statusLook up end-of-support/end-of-life status by part number in the lookup table. Endpoint: GET /data/lookup.json
- Get part status
Get a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups. Endpoint: GET /cell/{part}.txt
- Get product family
Get full end-of-support/end-of-life detail for one product family by its slug. Endpoint: GET /api/v1/family/{slug}.json
- List product families
List every tracked product family with its end-of-support/end-of-life status. Endpoint: GET /api/v1/families.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews