n8n Workflow: Luma Triage Approvals w/ Attendance History + Telegram
n8n Workflow: Luma Triage Approvals w/ Attendance History + Telegram
Regular price
£77.99
Regular price
£77.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Workflow: Luma Triage Approvals w/ Attendance History + Telegram
Regular price
£77.99
Regular price
£77.99
Sale price
Unit price
/
per
Turn Luma approvals into a data-driven triage—with Telegram proposals
This n8n workflow automatically uses your Luma event attendance history stored in n8n Data Tables to triage upcoming approval and waitlist queues. It then sends a Telegram proposal to approve or skip suggested guests—optionally updating guest status via the Luma API.
What this workflow does
- Runs on a manual trigger, a daily 9:00 schedule, or a form submission to handle past imports, CSV-based analysis, or upcoming-event checks via the Luma API (or mock data).
-
Creates and maintains Data Tables (events, attendance, snapshots, and actions) to persist:
- Per-event attendance history
- Historical show-up performance
- Guest-list snapshots
- Previously recorded approval actions
- Imports past events by parsing an uploaded Luma guest CSV, normalizing and hashing guest emails, then storing attendance plus event-level show-up rates. It sends an attendance recap to Telegram.
- Analyzes upcoming events by fetching the guest list from the Luma API (or parsing an upcoming CSV), loading historical attendance and the last event snapshot, and replaying prior actions.
- Computes expected attendance using per-person show-up rates blended with a global average, then groups the waitlist/pending approvals by past behavior.
- Proposes approvals to hit the target fill while respecting the overbooking limit, and saves a snapshot for “since last check” comparisons—posting status updates to Telegram (and optionally updating status via the Luma API).
Use cases
- Reduce overbooking risk for Luma-based events by approving guests based on historical attendance likelihood.
- Process guest CSV uploads to continuously improve approval decisions over time.
- Centralize approval triage notifications in Telegram for faster, consistent ops workflows.
Technical details
- n8n nodes/logic used: if, set, code, form, crypto, switch
- Core features: n8n Data Tables, email normalization + hashing, guest-list snapshots, and Telegram messaging
- Optional integration: update guest status via the Luma API
