Google Sheets + Gmail QR tickets, smooth event check in
You collect registrations, then everything gets messy. Names spelled three ways, duplicate signups, and a check-in line where someone’s “ticket email” is buried under 40 unread threads.
Event organizers usually feel this first. A conference manager dealing with sponsors and VIPs feels it too, and community teams running meetups don’t get a free pass. This QR ticket check-in automation keeps your attendee list clean, sends QR tickets automatically, and stops duplicate check-ins before they create an awkward moment at the door.
This workflow uses n8n to connect Google Sheets, Gmail, and Slack so registration and check-in run like a system, not a scramble. You’ll see how it works, what you need, and where teams typically customize it.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Google Sheets + Gmail QR tickets, smooth event check in
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Check-in Webhook"]
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Decode QR Code"]
n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Is Valid QR?", pos: "b", h: 48 }
n10@{ icon: "mdi:database", form: "rounded", label: "Lookup Ticket in DB", pos: "b", h: 48 }
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Validate Check-in"]
n12@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check-in Allowed?", pos: "b", h: 48 }
n13@{ icon: "mdi:database", form: "rounded", label: "Mark as Checked In", pos: "b", h: 48 }
n14@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Is VIP?", pos: "b", h: 48 }
n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Slack VIP Alert"]
n16["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge VIP Path"]
n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Build Success Response"]
n18["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Check-in Success"]
n19["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Check-in Denied"]
n20["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Invalid QR Response"]
n14 --> n15
n14 --> n16
n9 --> n10
n9 --> n20
n8 --> n9
n16 --> n17
n15 --> n16
n7 --> n8
n12 --> n13
n12 --> n19
n11 --> n12
n13 --> n14
n10 --> n11
n17 --> n18
end
subgraph sg1["Flow 2"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Registration Webhook"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Create Ticket Data", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "Save to Participants Sheet", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Prepare QR Payload"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Generate QR Code"]
n5@{ icon: "mdi:message-outline", form: "rounded", label: "Send Ticket Email", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Registration Success"]
n4 --> n5
n5 --> n6
n1 --> n2
n3 --> n4
n0 --> n1
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n9,n12,n14 decision
class n10,n13,n2 database
class n7,n18,n19,n20,n0,n4,n6 api
class n8,n11,n17,n3 code
classDef customIcon fill:none,stroke:none
class n7,n8,n11,n15,n16,n17,n18,n19,n20,n0,n3,n4,n6 customIcon
The Challenge: Fast Check-In Without Data Chaos
Event check-in sounds simple until you actually run one. People register through a form, you export a CSV, someone edits it, then you’re searching email confirmations while a line builds. The worst part is the uncertainty. You don’t know if an attendee already checked in, if they registered twice with different emails, or if a VIP just arrived and nobody noticed. And when your “source of truth” is spread across inboxes and half-updated spreadsheets, mistakes aren’t rare. They’re inevitable.
It adds up fast. Here’s where it breaks down in real life.
- Manual confirmation emails get skipped or sent late, which creates support emails right before the event.
- QR codes (if you use them) end up generated in a separate tool, so matching tickets to attendees becomes a mini project.
- Duplicate check-ins happen when staff can’t tell if a ticket was already scanned, and that throws off attendance numbers.
- VIP handling becomes guesswork because there’s no reliable “flag” that triggers a heads-up to your team.
The Fix: QR Tickets + Live Attendance, Fully Automated
This n8n workflow gives you two connected flows: registration and check-in. First, a webhook receives a new registration from your form. n8n creates a unique ticket ID, stores the attendee record in Google Sheets, generates a QR code tied to that ticket, and sends a Gmail confirmation with the QR code attached. Then, at the venue, your check-in flow scans and decodes the QR code, looks up the ticket in your Google Sheets “database,” and decides what happens next. Valid ticket? It marks the person as checked in and records the time. Already scanned? It blocks the duplicate and returns a clear message. VIP ticket type? It pings Slack so your team can react immediately.
The workflow starts with registration data hitting a webhook, then turns that into a structured row in Google Sheets plus a QR ticket sent by Gmail. At the door, a scan triggers validation, updates your sheet in real time, and posts a Slack alert for VIP arrivals so nothing important slips by.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you’re running a 200-person workshop and you usually spend about 2 minutes per registration generating a “ticket,” emailing it, and updating a spreadsheet. That’s roughly 6-7 hours of admin before doors even open. With this workflow, registrations drop into Google Sheets automatically and Gmail sends the QR ticket without you touching anything. On-site, check-in becomes a quick scan plus an automatic update, and you get live attendance numbers instead of estimates.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for the attendee database and check-in log.
- Gmail to send QR ticket confirmations automatically.
- Slack to notify your team about VIP arrivals.
Skill level: Beginner. You’ll connect accounts, paste webhooks into your form tool, and confirm your sheet columns match.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Registration hits your webhook. When someone submits your registration form, n8n receives the details (name, email, ticket type, event ID) immediately.
Ticket creation and recordkeeping happens in Google Sheets. The workflow generates a unique ticket ID, then stores the full attendee row in your sheet with timestamps so you have one reliable list.
QR ticket generation + Gmail delivery runs automatically. n8n creates a QR code tied to the ticket ID and emails it as a confirmation, so attendees show up with something scannable.
Check-in scanning validates and updates attendance. A scan/decoded QR triggers a lookup, blocks duplicates, marks check-in time, and sends a Slack message when the ticket type is VIP. You also get real-time attendance statistics back from the workflow.
You can easily modify ticket types to include things like “Speaker” or “Sponsor” based on your needs. See the full implementation guide below for customization options.
Watch Out For
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google connection inside n8n’s Credentials panel first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Slack alerts depend on your “Ticket Type” values matching your logic. If VIP notifications aren’t firing, check the exact text in the sheet row and the IF condition in the workflow.
Common Questions
About an hour if your Google Sheet columns are already set up.
Yes. No coding is required, but you do need to connect Google Sheets, Gmail, and Slack credentials. Once the webhooks are pasted into your form and scanner flow, it runs on its own.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in any extra tools you add later (for example, a paid QR scanning app if you don’t already have one).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can customize the Google Sheets fields (Ticket Type, Event ID, or a “Company” column) and then update the IF conditions that route VIP logic. If you want capacity limits, add a check before the “store registration” action to count existing rows for that Event ID and reject new registrations once you hit your cap. You can also swap the Gmail message content so it matches your brand and includes venue details, calendar links, or refund policies.
Usually it’s expired Google credentials or the wrong Google account connected inside n8n. Reconnect Google Sheets in the Credentials area, then verify the spreadsheet ID and sheet/tab name still match. If the sheet structure changed (columns renamed or reordered), the workflow may be writing to the wrong place or failing to find the Ticket ID during check-in.
For most small events, it’s effectively “as many as your sheet can handle,” and Google Sheets will comfortably manage thousands of rows.
Often, yes, because check-in logic needs branching (valid ticket vs. duplicate vs. VIP) and you don’t want to pay extra every time your flow gets more detailed. n8n also makes it easier to self-host, which matters if you have multiple events and lots of scans. Zapier or Make can still work if you only need “form submission → email sent,” and you don’t care about real-time validation at the door. Once you start blocking duplicates and returning messages to a scanning flow, n8n tends to fit better. Talk to an automation expert if you’re on the fence.
Once this is live, your attendee list stays accurate and check-in becomes predictable. Honestly, that calm is worth the setup by itself.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
