[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 scheduling emails

> Send the scheduling emails that are still waiting on a plan, for one team, one person or everyone. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/planning-center/send_scheduling_emails

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Send the scheduling emails that are still waiting on a plan, for one team, one person or everyone.

Planning Center API: https://cotlet.dev/docs/api/planning-center.md

`POST https://cotlet.dev/api/v1/planning-center/plans/{plan_id}/scheduling-emails`

Access: write. Confirm: waits for the user's OK before it runs.

Does what the Send button on the Teams tab does: emails people whose prepared notification is unsent, with their times, Accept and Decline buttons and a plan link. People who already got their email are skipped. Returns who was emailed. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `plan_id` | string | yes | Plan id from list_service_plans. |
| `team` | string | no | Team name, for example Band. Default: every team of the plan. |
| `person_id` | string | no | Email only this person. Overrides team. |
| `message` | string | no | Custom text added to the email. |

## Request

**cURL**

```bash
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"}'
```

**Python**

```python
result = client.call("planning-center", "send_scheduling_emails", {"plan_id":"71234","team":"Band"})
```

**Node.js**

```js
const result = await cotlet.call('planning-center', 'send_scheduling_emails', {"plan_id":"71234","team":"Band"});
```

**CLI**

```bash
cotlet call planning-center send_scheduling_emails --data '{"plan_id":"71234","team":"Band"}'
```

## Example response

```json
{
  "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
}
```

Previous: [List first-time guests](https://cotlet.dev/docs/api/planning-center/list_first_timers.md)
Next: [Respond to schedule request](https://cotlet.dev/docs/api/planning-center/respond_to_schedule_request.md)

---

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.