Event RSVP follow-up workflow

Setup guide.

Step-by-step from “fresh install” to “first run.” Skim it once, then keep this page open while you go.

Before you import

Decide first whether you want a single workflow that handles every event, or a copy per event. The template uses event_id as a Brevo attribute so a single workflow can fan out to per-event reminder sequences using Brevo's automation rules — that's the recommended path.

Step 1 — Build the Tally RSVP form

Required fields on the form: first_name, last_name, email, event_id (hidden field — you set this when you embed the form on a per-event landing page). Optional: dietary_notes, plus_one_count. The fewer required fields you have, the more RSVPs you get.

Step 2 — Wire Brevo

Create a Brevo list called 'Event RSVPs' and capture its numeric ID. Replace REPLACE_WITH_EVENT_LIST_ID in the n8n node. Then in Brevo → Automations, build a 3-step reminder sequence (T-7d / T-1d / morning-of) keyed off the EVENT_ID attribute so the right copy goes to the right event.

Step 3 — Wire the day-of check-in webhook

Replace REPLACE_WITH_CHECKIN_WEBHOOK_URL with whatever your check-in team uses. A Telegram bot (chat_id format), a Slack webhook, or a custom n8n workflow that writes to a Google Sheet all work — the payload sends event_id, attendee_email, attendee_name.

Troubleshooting.

Hit one of these? Here's the fix.

Reminders fire all at once instead of staggered

n8n's Wait node uses real wall-clock time. If you run the workflow in test mode it may skip waits — re-test in 'Active' mode and check the execution timeline in n8n. The 1-day wait in the template is intentionally short for demo; bump to 7 days for production.

Day-of webhook never fires

Wait nodes only resume if n8n stays running. Self-hosted n8n that restarts loses pending waits. Either deploy n8n with persistent storage (Docker volume + Postgres backend), or move the day-of ping into a separate scheduled workflow that queries the Brevo list each morning.