Billetto logo Billetto automation · runs weekly

Email the Billetto guest list to your 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 All Billetto tools

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 · Billetto API: endpoint reference · Billetto API: Getting started · Billetto on Zapier MCP

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

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

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.

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