The moment someone registers for your event, they expect something back that feels like a ticket, not a bare confirmation email. This workflow produces that artifact automatically: every new registration row becomes a personalized, branded ticket with the attendee's name and their own QR code, filed in Drive and ready to send.
Events that run on this
Anatomy of a generated ticket
The template defines the design once: event branding, venue, date, and placeholders for what changes per person. The sheet supplies the rest. Click a row:
| AName | BTicket type | CSeat | DTicket ID | |
|---|---|---|---|---|
| 1 | Priya Sharma | VIP | Table 2 | TKT-0041 |
| 2 | Daniel Okoye | General | Open | TKT-0042 |
| 3 | Mei Lin | Speaker | Reserved | TKT-0043 |
Rendered from row 1, one per row
The ID column renders as a QR code, giving every ticket a scannable identity for check-in without a ticketing SaaS in the loop. Tier columns can switch colors or labels so staff spot VIPs instantly. Tickets render as PDFs for email and printing, and the same run can produce a phone-sized PNG version, which is what most people actually show at the door.
Set it and let registrations flow
With the new-row trigger active, ticket generation keeps pace with signups all the way to doors-open. Late registrations get the same ticket everyone else did, minutes after submitting.
