Notion Event RSVP Tracker

Overview

This solution manages event RSVPs end-to-end from a Notion event hub. It ships as two cloud flows in one solution. Flow 1 (Microsoft Forms trigger) logs each RSVP as a page in a Notion attendee database, emails a confirmation with a calendar (.ics) attachment, recomputes the confirmed headcount, and writes that count back to the Notion event page. Flow 2 (daily schedule) finds events happening tomorrow and emails every confirmed attendee a reminder.

Why it matters: organizers who run event logistics in Notion get RSVPs captured, attendees confirmed and reminded automatically, and a live, accurate headcount - with no manual spreadsheet.

Ships Off (Stopped). The headcount is recomputed from attendee records, not blind-incremented.

Use Case

A Marketing/Operations team plans events in Notion and collects RSVPs via a Microsoft Form. They want each RSVP logged against the event, attendees confirmed with a calendar invite, the confirmed headcount kept current on the event page, and confirmed attendees reminded the day before.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Map your form questions

Set the four flowlibs_FormQuestion* env vars to your form's question ids.

Match your Notion property names

The flows assume attendee props Name/Email/Event/RSVP Status and event props Name/Date/Confirmed Count. Rename in the actions if your databases differ.

Reminder timing

Change the recurrence or the addDays(utcNow(),1) window for a different lead time.

Capacity / waitlist

Add a condition after the count update to close RSVPs or waitlist when a cap is reached.

Ticketing

Swap Microsoft Forms for the Eventbrite connector for ticketed events.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

outputs('Get_Response_Details')?[concat('body/', parameters('flowlibs_FormQuestionAttendeeName'))]

coalesce(outputs('Compose_Event_Page')?['properties']?[variables('varEventDateProperty')]?['date']?['start'], utcNow())

length(body('Filter_Confirmed'))

equals(formatDateTime(coalesce(item()?['properties']?['Date']?['date']?['start'],'2000-01-01'),'yyyy-MM-dd'), variables('varTomorrow'))

{ "properties": { "Confirmed Count": { "number": <count> } } }