[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)

# Email Wild Apricot event attendees after the event

> Thank the people checked in at your Wild Apricot event and write a different note to no-shows, from the attendance you recorded. Runs weekly.

Source: https://cotlet.dev/integrations/wild-apricot-api-mcp-server/email-event-attendees-after-event

The event is over, the check-in list is complete, and two different emails are due: a thank-you for the people who came and a note for the ones who registered and did not show.

Cotlet does it in your own Wild Apricot account with list\_events, list\_event\_registrants and send\_email, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=wild-apricot) [All Wild Apricot tools](https://cotlet.dev/integrations/wild-apricot-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Wild Apricot do this on its own?

Wild Apricot documents one follow-up path (checked 23 Oct 2026): filter the registrants by Checked in and email them by hand. It has no automatic after-event email to attendees and no separate one for no-shows. Its API is for developers and the help center does not describe sending email through it.

## How you do it in Wild Apricot today

1. An admin opens the event under Events > Event list and goes to the Registrants & invitees tab.
2. The admin picks Checked in from the Filter dropdown and clicks the green Email registrants button to write to the attendees.
3. Wild Apricot describes no filter for the opposite group. For the no-shows the admin builds the list by hand, or runs a Contacts advanced search on Registered for specific event(s) and removes the attendees.
4. Each email goes through Communication > Email steps: template, preview, recipients, subject, Reply to, then Send it now or Schedule for later.
5. The whole routine happens for every event, and the no-show note is the first thing to slip.

## How to email Wild Apricot event attendees after the event

Prompt

```
Find the Wild Apricot event that ended yesterday. Email everyone who was checked in a thank-you with the photo album link, and send a short "sorry we missed you" to registrants who were not checked in.
```

1. 01  
### Find the event  
list\_events returns the events list with the Attendance numbers Wild Apricot shows. The agent picks the event you named, or the latest one that already took place, and stops if no check-in was recorded, because then there are no attendees to separate.
2. 02  
### Split attendees from no-shows  
list\_event\_registrants runs twice: with checked\_in set to true and to false. The agent follows next\_cursor on each, so a large event is split as one batch.
3. 03  
### Write two messages  
One thank-you for attendees with the link you gave, one short note for no-shows. The agent does not promise anything you did not put in the prompt, such as a refund or a recording.
4. 04  
### Send each as one email  
send\_email goes out with event\_id and checked\_in\_only for attendees, and with the no-show contact\_ids for the other group. Wild Apricot sends one email per unique address, so a guest who shares an address with a registrant gets one message. Each email waits for your OK by default.
5. 05  
### Report the counts  
The agent returns how many people each email was queued for, so you can compare them with the Attendance column of the events list.

### What you get back

Example data

```
Event: Saturday group ride (Oct 17)
Registered 22, checked in 18
Thank-you queued for 18 attendees
"Sorry we missed you" queued for 4 no-shows
```

### Other ways to ask

- Thank only the attendees and do not write to no-shows.
- After every event this month, send attendees a survey link the next morning.
- Draft both emails in this chat and send nothing.
- Schedule the thank-you for 9:00 tomorrow in our timezone.

## What Wild Apricot allows, and what to know first

- Wild Apricot records check-in at the event level, so at a multi-session event attendees cannot be checked in for individual sessions.
- Only full administrators and event managers can check in attendees, and the Checked in filter shows only what they recorded.
- Wild Apricot sends only one email to each unique email address, and recipients cannot see other recipients, because all are BCC by default.
- After Send it now the email goes into a queue and can take from a few minutes to a few hours to reach all recipients.
- Wild Apricot does not let you attach files to an email, so a photo album goes in as a link.

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

Sources: [Wild Apricot Help: Event attendance](https://gethelp.wildapricot.com/en/articles/34-event-attendance) · [Wild Apricot Help: Sending emails manually](https://gethelp.wildapricot.com/en/articles/35-sending-emails-manually) · [Wild Apricot Help: Searching for event registrations](https://gethelp.wildapricot.com/en/articles/106-searching-for-event-registrations)

## Call send\_email from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/wild-apricot/emails \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":7210,"checked_in_only":true,"subject":"Thank you for riding with us on Saturday","body":"Thanks for coming to Saturday'\''s group ride. The photo album is here: https://yourclub.example/ride-photos"}'
```

Example response

```
{
"email_id": 20318,
"status": "queued",
"recipients": 18,
"event_id": 7210,
"scheduled_for": null,
"subject": "Thank you for riding with us on Saturday"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is wild\_apricot\_write → send\_email. Example data.

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

## Wild Apricot tools this automation uses

__Cotlet Wild Apricot tools used to email Wild Apricot event attendees after the event__
| Tool | Parameters |
| ------------------------ | ----------------------------------------------------------------------- |
| list\_events | search, starts\_after, starts\_before, cursor |
| list\_event\_registrants | event\_id, checked\_in, cursor |
| send\_email | subject, body, contact\_ids, event\_id, checked\_in\_only, schedule\_at |

[All 12 Wild Apricot tools with descriptions](https://cotlet.dev/integrations/wild-apricot-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Wild Apricot to Cotlet?

Yes. You sign in to Wild Apricot yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Wild Apricot 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 Wild Apricot automations

- [Approve Wild Apricot membership applications with AI](https://cotlet.dev/integrations/wild-apricot-api-mcp-server/approve-membership-applications.md)
- [Record offline payments against Wild Apricot invoices](https://cotlet.dev/integrations/wild-apricot-api-mcp-server/record-offline-payments-against-invoices.md)
- [Wild Apricot API and MCP server: every tool](https://cotlet.dev/integrations/wild-apricot-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Wild Apricot.

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

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

---

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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.