An RSVP form that emails you every reply

When you want this form

Event pages need an answer to one question: who's coming? Whether it's a workshop with twelve seats, a meetup that needs a headcount for pizza, or a wedding collecting meal choices, the replies all look the same — a name, a yes or no, and a few details.

If your event page is static HTML, it can't receive the form POST itself. Form2Email receives it and emails you each RSVP, so the headcount builds up in your inbox without a spreadsheet, a database, or an account to create.

The form

Paste this into your page and replace your-token with the token from your endpoint (setup below):

<form action="https://form2email.terragohan.com/f/your-token" method="post">
  <label for="name">Name</label>
  <input id="name" name="name" required>

  <label for="email">Email</label>
  <input id="email" name="email" type="email" required>

  <fieldset>
    <legend>Will you be attending?</legend>
    <label><input type="radio" name="attending" value="yes" required> Yes, I'll be there</label>
    <label><input type="radio" name="attending" value="no"> Sorry, can't make it</label>
  </fieldset>

  <label for="guests">Number of guests (including you)</label>
  <input id="guests" name="guests" type="number" min="1" max="10" value="1">

  <label for="meal">Meal preference</label>
  <select id="meal" name="meal">
    <option value="standard">Standard</option>
    <option value="vegetarian">Vegetarian</option>
    <option value="vegan">Vegan</option>
    <option value="gluten-free">Gluten-free</option>
  </select>

  <label for="notes">Anything we should know? (allergies, accessibility, …)</label>
  <textarea id="notes" name="notes" rows="4"></textarea>

  <!-- optional: send guests to a details page after they RSVP -->
  <input type="hidden" name="_redirect" value="https://yoursite.com/event-details">

  <button type="submit">Send RSVP</button>
</form>

That's the whole integration. The form works with or without JavaScript, on any host that can serve an HTML page. Style the fields however you like — only the action, method="post", and the input name attributes matter to Form2Email.

Set it up

1. Create the endpoint

   Use the tool on the homepage — or POST https://form2email.terragohan.com/api/endpoints — with the email that receives submissions and the exact domain this form lives on.

2. Verify the email

   We send a verification link to the destination address — single-use, valid 24 hours. Nothing is accepted until a human clicks it. Add form2email@terragohan.com to your trusted senders.

3. Point the form at it

   Put your public URL in the form's action. Submissions are only accepted from the domain you registered — exact hostname match, subdomains need their own endpoint.

4. Keep it alive

   Endpoints stay active for 7 days after verification. Extend for free (+7 days, as often as you like) from your manage page — extending also revives an expired endpoint.

What lands in your inbox

Each RSVP becomes one email to your destination address:

• Reply-To is the guest's email, so hitting reply reaches them directly if plans change.
• name appears in the body.
• attending, guests, meal, and notes are listed as additional fields.

With _redirect set, the guest's browser is sent to your page after a successful submit. Without it they get a small JSON response — fine for JavaScript-driven forms, less friendly for plain HTML.

Tips

• Ask for dietary needs and accessibility requirements in the notes field rather than adding more inputs — one free-text box covers requests you didn't anticipate.
• One email per RSVP makes headcounts easy: count the "yes" replies in your inbox, or filter on attending: yes with your mail client's search.
• Point _redirect at a details page with the venue address, start time, and parking info — guests confirm their RSVP worked and get the practical details in one step.
• Say on the page that no confirmation email is sent; guests only hear from you if you reply.
• Add form2email@terragohan.com to your contacts so the verification and RSVP emails don't land in spam.

Limitations

• Timing matters: the endpoint expires 7 days after verification. If your event is further out than that, extend it from your manage page so it's still alive on the event date — extensions are free, unlimited, and revive an expired endpoint.
• Submissions are accepted only from the exact domain you registered. If your event page answers on both yoursite.com and www.yoursite.com, register the one your form is served from (or create one endpoint per hostname).
• Guests get no automatic confirmation email — Form2Email only emails you. Put the key details on the page itself or the _redirect target.
• No file attachments — file inputs are dropped. Ask for a link instead.
• Spam protection is origin checks plus per-IP rate limits with backoff; there is no CAPTCHA or honeypot yet.

Keep reading

• Booking form — when guests pick a specific date and time rather than just yes or no.
• Waitlist form — for a sold-out event or a coming-soon page, reduced to a single email field.
• How it works — the endpoint lifecycle and security model in detail.