Put each RSVP on the calendar and on the reminder list
Guests who say yes get a calendar invite and a place on the reminder list from the same Zap, with no spreadsheet export in between.
New Submission on your RSVP form
Create a calendar event for the attendee and add them to an email marketing list in the same Zap
One-directional. A submission triggers the action — nothing is written back into your form.
Two lists always drift apart before an event: the one the caterer works from, and the one the reminder emails go to. Both start from the same RSVPs, and both get rebuilt by hand from an export in the last week.
One Zap keeps them together. A guest who says yes is added to the calendar entry and subscribed to the reminder campaign at the same moment, with the party size carried into both. It is the flow a small events team wants when the RSVP list is also the planning document.
Setting it up
- 1
Publish the RSVP form and keep Will you be attending? to fixed options. The Zap branches on that answer, and a typed-in maybe will not match either side.
- 2
In Zapier, add formformform's New Submission trigger on the RSVP form and pull a test reply from someone who is attending.
- 3
Add a Filter as the second step: continue only when Will you be attending? equals your yes option, so regrets never reach the calendar.
- 4
Add the calendar action next, adding the guest as an attendee on the existing event rather than creating a fresh event for each RSVP.
- 5
Hard-code the date, time and venue in the calendar step. They live on the invitation, not on the form, so nothing is mapped for them.
- 6
Add the email marketing action last, subscribing the guest to the reminder audience with the party size stored as a merge field.
- 7
Tag each subscriber with the event name, so the reminder campaign targets this event rather than your whole list.
- 8
Test with one yes and one no, and confirm the no produced neither an invite nor a subscription.
What maps where
Using the Party RSVP Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Zapier |
|---|---|
| Will you be attending? | The Filter condition — a no stops the run before any invite is sent |
| Email Address | Calendar attendee address, and the subscriber record on the reminder list |
| Your Name | Guest name on the attendee list and the greeting merge field |
| How many in your party? | Head count merge field on the subscriber, and appended to the calendar note |
| Dietary Restrictions | Line in the event description, where whoever briefs the caterer reads it |
| Anything else we should know? | Note on the subscriber record for the organiser to read before the day |
Variations worth knowing
Add a spreadsheet step that appends each party size to a running total, then a Path that posts to the organisers' channel once that total passes the venue capacity. The invite still goes out; somebody just learns the room is close to full.
Give the no answer its own Path rather than dropping it at a Filter. Log it to a declines sheet and, if the event runs annually, tag the contact so next year's invitation goes out early. A no is still information about who wanted to come.
If something isn't arriving
The calendar step is creating a new event each time instead of updating one. Switch it to the add-attendee action and point it at a specific event ID, so every RSVP joins the same entry rather than filling the calendar with copies.
The merge field does not exist at the destination, so it is dropped without an error. Create the field in your marketing app first, then resubscribe those guests through the Zap so the head count has somewhere to land.
Frequently asked questions
Do guests see each other's names on the calendar invite?
That depends on the calendar's own settings rather than on the form. Most calendars show the attendee list to everyone invited unless guest visibility is turned off. Check that before pointing this Zap at an event with a private guest list.
What happens if someone RSVPs twice?
The calendar step matches on the email address and will not add the same attendee twice. Marketing lists usually behave the same way and update the existing subscriber. Both submissions are still stored in the form, so the change of answer stays visible.
Can a guest change their answer from yes to no?
They submit again with the new answer. Nothing is edited back into the form or removed from the calendar automatically, so add a Path on the no answer that removes the attendee if you want the head count to correct itself.
Related automations
- Let only qualifying applications reach the hiring manager
A Filter step checks location and hours first, so only qualifying applications create a candidate record and reach the hiring manager.
- Log every feedback score, then follow up a day later
Formatter cleans the rating into a number, the row lands in your analysis sheet, and a Delay sends the follow-up email a day later.
- Send one demo request to your CRM, sheet and Slack
A single demo request creates a CRM contact, adds a row to the reporting sheet and posts to the sales channel in one multi-step Zap.
- Split urgent support requests into their own queue
A Path reads the priority answer and raises an escalated help desk ticket for urgent submissions, a standard one for everything else.
- Turn each order into an invoice and a confirmation email
Each order submission drafts an invoice in your billing app and sends the buyer a confirmation, so fulfilment and accounts stay level.
- Confirm event sign-ups and log the attendee
A registration becomes a calendar entry, a confirmation email and an attendee row, all from one scenario run.
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