Track event RSVPs and registrations
Registrations append to an Attendees table, so the headcount totals itself and dietary needs are countable before the day.
New submission on your event registration form
Add a row to an Attendees table in Microsoft Excel with name, ticket type, dietary needs and party size
One-directional. A submission triggers the action — nothing is written back into your form.
Guest lists move right up to the afternoon of the event, and the caterer wants one number. This flow appends every registration to an Attendees table in a shared SharePoint workbook, with ticket type, party size and dietary notes each in their own column.
Events coordinators run it so the headcount is never a manual tally. The registrant plus their additional guests give a party size the table can sum, and the dietary column can be counted without reading each response, while accessibility requests stay visible in a column of their own.
Setting it up
- 1
Publish the registration form with Ticket Type as a dropdown matching the tickets you actually offer, so the column can be pivoted rather than tidied by hand.
- 2
Create the workbook in the SharePoint library the events team already shares, then format an Attendees worksheet as a table. A file sitting on someone's desktop cannot be written to.
- 3
Give the table columns for Registered, Name, Email, Ticket, Additional Guests, Party Size, Dietary, Access and Checked In.
- 4
Write =[@[Additional Guests]]+1 in the Party Size column so each row counts the registrant as well as their guests. The total at the foot of that column is your headcount.
- 5
In Zapier, choose formformform's New Submission trigger, connect the account, select the registration form and pull a test RSVP.
- 6
Add Microsoft Excel's Add Row to Table action, connect a Microsoft account with access to that SharePoint site, then select the workbook, worksheet and Attendees table.
- 7
Map Full Name, Email Address, Ticket Type, Number of Additional Guests, Dietary Restrictions and Accessibility Requirements to their columns, and leave Checked In empty for the door team.
- 8
Submit a test RSVP, confirm Party Size calculated, then turn the Zap on and share the workbook read-only with anyone who only needs to look.
What maps where
Using the Event Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Microsoft Excel |
|---|---|
| Full Name | Name column in the Attendees table |
| Email Address | Email column, used to match a later change of plan |
| Ticket Type | Ticket column, filtered per session |
| Number of Additional Guests | Additional Guests column, feeding the Party Size formula |
| Dietary Restrictions | Dietary column, counted for the caterer |
| Accessibility Requirements | Access column, reviewed by the venue |
Variations worth knowing
Build a second worksheet that pulls only Name, Party Size and Dietary from the table, then export that sheet as its own file. The caterer gets the numbers they need and the guest email addresses stay in the workbook you keep.
A Zapier Filter on Ticket Type sends each class to its own table. Coordinators running a paid session alongside a free one usually want the two lists apart, since only one of them needs chasing before the doors open.
If something isn't arriving
Number of Additional Guests counts the guests, not the person registering. Keep the Party Size column as =[@[Additional Guests]]+1 and total that column rather than the raw field from the form.
Multi-select answers come through joined together. Count them with a wildcard, as in =COUNTIF(Dietary,"*vegan*"), or split the answer with Formatter before mapping if you need one column per option.
Frequently asked questions
What if someone needs to change their RSVP?
A second submission appends a second row rather than editing the first, because the flow only ever writes forwards. Keep the Registered timestamp column, sort on it, and treat the most recent row for that email address as the current answer.
Does the workbook need to be open for rows to appear?
No. Rows are written through Microsoft's cloud API, so they land whether or not anyone has the file open. It does have to live on OneDrive or SharePoint — a copy saved to a laptop is invisible to the Zap.
Can the caterer see attendee email addresses?
Only if you share the whole workbook. The usual approach is to export a sheet holding name, party size and dietary notes and send that instead, which keeps contact details in the file the events team controls.
Related automations
- Aggregate survey and feedback responses
Each feedback response becomes a row with the score, the product and the comments, ready for averages and PivotTables.
- Build an order log for fulfilment
Every order appends a row to an Orders table, so quantities total themselves and the packing list is always current.
- Collect job applications in a hiring sheet
Applications land in a Candidates table you can filter by role and colour by stage as people move through the round.
- Log new leads to a tracking workbook
Each quote request becomes a row in a Leads table, with company, service type and budget already in their own columns.
- Route support requests into a triage log
Every bug report lands in an Inbox table with severity and reporter, sorted so triage starts with the worst of them.
- Add every inbound enquiry to your Notion leads database
Every business enquiry lands in your Notion Leads database as a page tagged New, with the company and inquiry type already filled in.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free