Post event RSVPs to the planning channel
Every RSVP posts to #events with the name, party size and dietary notes, so organisers watch the headcount build in one place.
New submission on your "RSVP" form
Post a channel message to #events with the attendee name, guest count and dietary notes
One-directional. A submission triggers the action — nothing is written back into your form.
Planning an event means the guest list matters most in the last fortnight, when catering numbers and room bookings have to be confirmed. Posting each RSVP into #events gives the planning group a running feed of who has answered, without anyone opening a spreadsheet or asking for an updated export.
It works best for internal events and community meetups where a handful of organisers share the work. Dietary notes are the reason most teams add it: the caterer needs them early, and a note in the channel is harder to forget than a cell in a column.
Setting it up
- 1
Publish the RSVP form and keep it to a handful of questions. "Will you be attending?" and "How many in your party?" are the two answers organisers act on, so nothing should stand in front of them.
- 2
In Zapier, point the New Submission trigger at the RSVP form for this specific event, not the general sign-up form you reuse each year.
- 3
Add Slack's Send Channel Message action and choose #events. Set the bot name to the event itself, so two events running at once can be told apart in the sidebar.
- 4
Write the message as a single line: Your Name, then the attendance answer, then the party size. One line keeps the channel scannable when twenty RSVPs land in an afternoon.
- 5
Put Dietary Restrictions on a second line so the caterer's list can be built by scrolling the channel rather than opening a file.
- 6
Leave Email Address out of the message. It stays in your responses list for the reminder mail-out, and the channel has no use for it.
- 7
Pin one message to #events with the date and the venue, so an organiser joining mid-planning has the context without asking for it.
- 8
Submit a test RSVP, check it reads cleanly on a phone, then turn the Zap on.
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 | Slack |
|---|---|
| Your Name | First line of the message |
| Will you be attending? | First line, straight after the name |
| How many in your party? | First line, closing the one-line summary |
| Dietary Restrictions | Second line, used to build the caterer's list |
| Anything else we should know? | Third line, where accessibility notes and requests land |
Variations worth knowing
Filter on "Will you be attending?" and route the no answers to a side channel, or leave them in your responses list entirely. #events then reads as the guest list, which is what an organiser is scrolling it for anyway.
Post an opening message for the event, then feed the timestamp Slack returns into the action so every RSVP arrives as a threaded reply. The channel stays calm and the whole guest list sits under one parent message.
If something isn't arriving
Nothing is edited or replaced after the fact, so a changed answer posts as a new message below the old one. Tell organisers the newest message for a name is the one that counts, and total party sizes from an export rather than the channel.
That question is usually optional, and an empty answer prints as a bare label with nothing after it. Either make it required in the form, or add a Zapier formatter step that drops the line when the answer comes through blank.
Frequently asked questions
How do I get the actual headcount?
Export your responses from formformform and total the party-size column. Each RSVP posts as its own Slack message, so the channel shows the list rather than a sum, and counting messages under-reports everyone who is bringing guests.
Can people RSVP by reacting in Slack instead?
Not through this flow. It runs one way, from a form submission into a channel, and a reaction is never written back. Reactions are still handy for organisers marking which RSVPs have already been added to the caterer's list.
Can two events share the same channel?
They can, with one Zap per form and a different bot name for each, though most organisers find a channel per event easier once messages start overlapping. Either way each form keeps its own responses list and its own export.
Related automations
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
- Drop customer feedback into your product channel
Feedback posts to #product as it arrives, with the rating and the comment, so nobody waits for a weekly roundup.
- Post new job applications to your hiring channel
Applications land in a private #hiring channel with the role and the candidate's skills, and reviewers thread their notes under each one.
- Send each new order as a direct message
New orders arrive as a direct message to whoever packs them, with the product, quantity and address in one place.
- Send new demo requests to your sales channel
A rep sees each inbound demo request in #sales the moment it lands, and claims it with an emoji reaction before anyone else replies.
- Alert the team when a new order comes in
Each new order pings #orders with the product, quantity and buyer details, so fulfilment can start straight away.
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