[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 the Billetto guest list to your venue

> Email the Billetto guest list of each weekend event to the venue or door team on a schedule, with the report type you choose.

Source: https://cotlet.dev/integrations/billetto-api-mcp-server/email-guest-list-to-venue

Before every event the venue or the door team asks for the guest list. You open the event, pick the report and type their address, again for each event.

Cotlet does it in your own Billetto account with list\_events and send\_guest\_report, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Billetto do this on its own?

Billetto's public API v3 lists attendees and has a reporting endpoint (checked 23 Oct 2026), but both need a developer with an API key or OAuth, and the API Terms require you to handle the guest data under GDPR. The Zapier app finds attendees; it sends no report. The report types of Guest list & reports are sent from the app.

## How you do it in Billetto today

1. Log in, open My Billetto and click Manage on the event.
2. Open Overview, then Guest list & reports, and pick a report type.
3. Type the recipient's email address and click Send via email. In the app you tap "<sales overview" first.
4. The Guest list (simple) holds Order ID, Name and Ticket ID; the Guest list (detailed) adds name and email, number of tickets, answers to purchase questions, and access codes.
5. An optional date range limits the data; the whole sequence repeats for each event and each recipient, and a late order means sending the report again.

## How to email the Billetto guest list to your venue

Prompt

```
Every Thursday, email the detailed guest list of each of my events from the weekend to door@example.com.
```

1. 01  
### Pick this weekend's events  
list\_events returns your current events with their start dates. The agent keeps those that start before Monday and skips events that already ended.
2. 02  
### Choose the report per recipient  
The venue gets guest\_list\_simple unless you say otherwise, because it holds only order ID, name and ticket ID. The detailed list also carries guest emails and purchase answers, so the agent sends it only to the address you named for it.
3. 03  
### Send once per event  
send\_guest\_report runs once per event and recipient. Each call asks for your OK by default, because guest data leaves Billetto.
4. 04  
### Skip empty events  
An event with no tickets sold gets no report, and the agent says so in its summary.
5. 05  
### Report what went out  
The agent lists each event, report type and recipient, so you can see who has what.

### What you get back

Example data

```
Events this weekend: 2
Sent guest_list_detailed for Autumn Jazz Night (132 tickets) to door@example.com
Sent guest_list_simple for Pottery Workshop (57 tickets) to door@example.com
Skipped 0
```

### Other ways to ask

- Send the sales report of every event that ended last week to accounts@example.com.
- Email the newsletter sign-up report of Autumn Jazz Night to me.
- The morning of each event, send the simple guest list to the door team again.

## What Billetto allows, and what to know first

- Billetto sends the reports by email, and events with more than 5,000 attendees may take longer to generate.
- The Email list report holds guest email addresses only, and Billetto reminds organisers that GDPR requires consent before using them for non-essential purposes.
- The Newsletter sign up report has consent to newsletter and the email data.
- The date range is optional; without it all data is included.

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

Sources: [Billetto Help: How to find and export guest lists and reports](https://support.billetto.com/hc/articles/206434189) · [Billetto API: endpoint reference](https://api.billetto.com/reference) · [Billetto API: Getting started](https://api.billetto.com/docs/get-started) · [Billetto on Zapier MCP](https://zapier.com/mcp/billetto)

## Call send\_guest\_report from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/billetto/events/1204551/guest-reports \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"report":"guest_list_detailed","email":"door@example.com"}'
```

Example response

```
{
"event_id": "1204551",
"report": "guest_list_detailed",
"sent_to": "door@example.com",
"status": "sent"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is billetto\_write → send\_guest\_report. Example data.

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

## Billetto tools this automation uses

__Cotlet Billetto tools used to email the Billetto guest list to your venue__
| Tool | Parameters |
| ------------------- | ---------------------------------- |
| list\_events | include\_past, cursor |
| send\_guest\_report | event\_id, report, email, from, to |

[All 14 Billetto tools with descriptions](https://cotlet.dev/integrations/billetto-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Billetto to Cotlet?

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

- [Refund Billetto tickets for guests with AI](https://cotlet.dev/integrations/billetto-api-mcp-server/refund-tickets-for-guests.md)
- [Resend Billetto tickets to guests who did not get them](https://cotlet.dev/integrations/billetto-api-mcp-server/resend-tickets-to-guests.md)
- [Billetto API and MCP server: every tool](https://cotlet.dev/integrations/billetto-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Billetto.

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

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

---

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.