WhatsApp logo

Send RSVP confirmations to guests

Guests get their RSVP details and the venue address in a thread they can find again.

When this happens

New Submission on your party RSVP form

Do this

Send an approved WhatsApp template message confirming the RSVP and the venue

One-directional. A submission triggers the action — nothing is written back into your form.

An RSVP confirmation by email is read once and lost. In WhatsApp it stays in a thread the guest can search on the day, which is when they actually need the address.

One thing to fix first: the Party RSVP Form template has no phone field, because most RSVPs never need one. Add one before wiring this up, and say on the form that it is used to send the confirmation.

Setting it up

  1. 1

    Publish the Party RSVP Form template, then add a Phone field and mark it required — the template ships without one, so nothing can be sent until you do.

  2. 2

    Create an approved WhatsApp template carrying the guest's name, party size and the venue address as placeholders.

  3. 3

    In Zapier, trigger on formformform's "New Submission" for the RSVP form.

  4. 4

    Add a filter so only guests who answered yes to "Will you be attending?" receive a confirmation. Sending one to somebody who declined reads badly.

  5. 5

    Add the WhatsApp Business Cloud Send Template Message action and map your new phone field as the recipient.

  6. 6

    Map the placeholders from the fields below. The venue address is fixed text in the template rather than a form field, so it cannot arrive blank.

  7. 7

    Test both branches — attending and not attending — before switching it 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 fieldWhatsApp
Your NameTemplate placeholder 1 — the greeting
How many in your party?Template placeholder 2
Will you be attending?Zapier filter condition, not a placeholder
Dietary RestrictionsInternal message to the organiser's own number

Variations worth knowing

Tell the caterer, not the guest

Send Dietary Restrictions and party size to your own number in a second step. The guest does not need their own answer read back; the person doing the headcount does.

A week-before nudge

Add a Zapier Delay Until step ahead of a second approved template so the venue and time resurface in the thread shortly before the event.

If something isn't arriving

Nothing sends, and the Zap reports a missing recipient.

The Party RSVP Form template has no phone field as shipped. Add one in the editor and re-select it in the Zap — the trigger's field list only refreshes once the form has been saved.

Guests who declined still get a confirmation.

The filter has to run before the WhatsApp step, and it has to match the stored answer exactly. Check the value in a real submission rather than assuming it is "Yes".

Frequently asked questions

Do guests need WhatsApp for the RSVP itself?

No. The form is a normal web page with its own link and QR code. WhatsApp is only the confirmation channel, and anyone without a number can still RSVP.

Can I message everyone at once later?

Not from this Zap, which fires per submission. Export the responses to CSV and use them wherever you send bulk messages — bulk sending is not something the form does.

Can I collect a contribution with the RSVP?

Yes. Add products and priced options to the form, then collect payment through secure hosted checkout with Stripe, PayPal, or Square. Payment status is tracked alongside the response.

Related automations

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