[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Send Planning Center scheduling emails with AI

> Send the scheduling emails waiting on a Planning Center plan, then see who declined or has not answered, before Sunday and without opening each team.

Source: https://cotlet.dev/integrations/planning-center-api-mcp-server/send-volunteer-scheduling-emails

You pencil volunteers into Sunday's plan during the week, and nothing reaches them until a team leader sends the email. Every plan, every team, every week.

Cotlet does it in your own Planning Center account with list\_service\_plans, get\_plan\_team and send\_scheduling\_emails, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=planning-center) [All Planning Center tools](https://cotlet.dev/integrations/planning-center-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Planning Center do this on its own?

Planning Center's official MCP can read plans and teams but has no Services write tools, so it cannot send the emails (checked 22 Oct 2026). Its Zapier integration lists five triggers (New Form Submission, New Donation, New Profile, New Workflow Card, New List Result) and no scheduling action. Sending stays a click in the Teams tab.

## How you do it in Planning Center today

1. A team leader opens Plans in the top navigation, picks the folder that holds the service type, and chooses the plan.
2. On the Teams tab, a ✉️ icon marks every person whose scheduling email is still waiting. Send at the top of a team emails that team, the ✉️ beside a name emails one person, and the ✉️ at the top right of the plan emails everyone.
3. The popup lets the leader edit the message, then Send \[number of team members\] finishes it. For several plans at once, the leader uses the matrix view.
4. Replies come back later, so the leader returns to each Teams tab to see who accepted, who declined and who has not answered.
5. The ✉️ icons are easy to miss: someone added to a plan on Thursday stays invisible to them until the email goes out.

## How to send Planning Center scheduling emails with AI

Prompt

```
Look at Sunday's Sunday Gathering plan. Send the scheduling emails still waiting to the Band team, then list who declined or has not answered.
```

1. 01  
### Find the plan  
Your agent calls list\_service\_plans for the service type you named and takes the plan on the date you gave. If two plans share the date, it stops and asks which one, because emails to the wrong plan cannot be recalled.
2. 02  
### Read who is waiting  
get\_plan\_team lists every position with a status and a prepared flag. The prepared flag is the ✉️ icon: true means the first email has not gone out yet. The agent counts confirmed, declined and unconfirmed people before it sends anything.
3. 03  
### Send only what is waiting  
send\_scheduling\_emails runs for the team you named. It emails only people whose prepared notification is unsent, so someone who already got a request is not emailed twice. Each call waits for your OK by default, and shows the names first.
4. 04  
### Report the gaps  
Declined people and people who have not answered are listed by team and position, so you can fill the gaps. The agent does not reschedule anyone; that stays your decision as team leader.

### What you get back

Example data

```
Sunday Gathering, 25 Oct: 14 scheduled
Confirmed 9, declined 2, unconfirmed 3
Emailed Band (3): Dana Whitfield, Marcus Bell, Priya Nair
Declined: Tom Reyes (Sound), Lena Ortiz (Greeters)
```

### Other ways to ask

- Every Thursday at 9, send all waiting emails for the next two Sunday plans and post the gap list in this chat.
- Send the waiting email only to Marcus Bell and leave the rest of the Band team prepared.
- List unconfirmed people for the Christmas Eve plan, but send nothing.

## What Planning Center allows, and what to know first

- Planning Center marks a not-yet-emailed person as prepared, and an unconfirmed scheduled viewer in that state cannot open the plan or see it on their schedule until the email is sent.
- Conflict warnings are suppressed for plan dates where a team member has a prepared notification, so the first email also starts the conflict checks.
- The scheduling email carries the assigned times, the plan items the person leads, any custom text, Accept and Decline buttons and a plan link.
- Prepared is on by default and can be switched off per team in People > Teams > the team > Settings > Scheduling Defaults, or per person on the plan.
- The help article refers to team leaders sending the emails and links to Permissions in Services for the exact roles, so the account behind this job should lead the team.

send\_scheduling\_emails asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Planning Center Help: Send scheduling emails](https://help.planningcenter.com/en/142892-send-scheduling-emails.html) · [Planning Center Help: Manage your schedule](https://help.planningcenter.com/en/142874-manage-your-schedule.html) · [Planning Center Help: Connect AI tools to Planning Center](https://help.planningcenter.com/en/151880-connect-ai-tools-to-planning-center.html) · [Planning Center: Zapier integration](https://www.planningcenter.com/integrations/zapier)

## Call send\_scheduling\_emails from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/planning-center/plans/71234/scheduling-emails \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"team":"Band"}'
```

Example response

```
{
"plan_id": "71234",
"team": "Band",
"sent": [
{
"person_id": "48215",
"name": "Dana Whitfield"
},
{
"person_id": "48377",
"name": "Marcus Bell"
},
{
"person_id": "48642",
"name": "Priya Nair"
}
],
"skipped_already_emailed": 0
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is planning\_center\_write → send\_scheduling\_emails. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/planning-center-api-mcp-server.md#automations)

## Planning Center tools this automation uses

__Cotlet Planning Center tools used to send Planning Center scheduling emails with AI__
| Tool | Parameters |
| ------------------------ | ----------------------------------- |
| list\_service\_plans | service\_type, from, to |
| get\_plan\_team | plan\_id, status, team |
| send\_scheduling\_emails | plan\_id, team, person\_id, message |

[All 12 Planning Center tools with descriptions](https://cotlet.dev/integrations/planning-center-api-mcp-server.md#tools)

## Frequently asked questions

### Will my agent email people who already got a request?

No. Planning Center only shows the ✉️ icon for people whose first email is unsent, and send\_scheduling\_emails follows the same rule, so a second call right after the first sends nothing.

### Is it safe to connect Planning Center to Cotlet?

Yes. You sign in to Planning Center yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Planning Center once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Planning Center automations

- [Log Planning Center first-time guests with AI](https://cotlet.dev/integrations/planning-center-api-mcp-server/log-first-time-guests.md)
- [Clear Planning Center workflow cards with AI](https://cotlet.dev/integrations/planning-center-api-mcp-server/clear-workflow-cards.md)
- [Planning Center API and MCP server: every tool](https://cotlet.dev/integrations/planning-center-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Planning Center.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Planning Center.

[Sign up free](https://cotlet.dev/app/signup?app=planning-center)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.