splitforms.com
EVENT RSVP · GATSBY

Event RSVP for Gatsby

Attendance confirmation with headcount and dietary needs. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Gatsby
Form.tsxtsx54 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function EventRsvpForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New event RSVP');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Your name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="attending">Will you attend? *</label>
36 <select id="attending" name="attending" required>
37 <option value="">Choose…</option>
38 <option>Yes — count me in</option>
39 <option>Maybe</option>
40 <option>No, I can't make it</option>
41 </select>
42 <label htmlFor="guests">How many guests are you bringing?</label>
43 <input id="guests" type="number" name="guests" placeholder="0" />
44 <label htmlFor="dietary">Dietary preferences</label>
45 <input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…" />
46
47 <button type="submit" disabled={status === 'sending'}>
48 {status === 'sending' ? 'Sending…' : 'Send'}
49 </button>
50
51 {status === 'error' && <p>Something went wrong. Try again.</p>}
52 </form>
53 );
54}
500
submissions / mo, free
5
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Gatsby + Event RSVPplatform-specific integration guide

Why Gatsby developers choose splitforms for event rsvp

Gatsby's static output is excellent for SEO and performance, but static HTML forms have no way to deliver submissions without a backend. Gatsby Cloud offers serverless functions, but wiring SMTP and a dashboard is a substantial project for what should be a simple contact form. The event rsvp on this page posts from the browser to splitforms — no Gatsby Function, no API route, no build-time configuration. The form works identically whether you deploy to Gatsby Cloud, Netlify, Cloudflare Pages, or any static host.

§ 00Quick answerReact / Next.js · events

Yes — this is the shortest safe path for Gatsby.

Use the React / Next.js snippet on this page, keep the event rsvp fields visible in your Gatsby UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

The posted payload contains your name, email, will you attend?, how many guests are you bringing?, dietary preferences. Required fields are your name, email and will you attend?.

native gatsby reality

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend.

use case fit

Eventbrite charges 3.7% + $1.79 per ticket. For a free event, fundraiser, or private gathering, the RSVP form does the same job for $0 — and lives on your own domain.

§ 01Event RSVP × Gatsbywhy this combination, in 80 words

Built for Gatsby developers who hate operating a backend.

Splitforms is the form backend for Gatsby sites. One POST endpoint, no SDK, no plugin — drop the event rsvp into a page and ship.

Splitforms is the form backend for Gatsby sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan
  • 500 form submissions per month
  • 2 forms on Free; unlimited forms on Pro
  • Spam protection (honeypot + classifier)
  • Webhooks: Slack, Discord, WhatsApp, custom
  • CSV export of all submissions
  • Email notifications (CC and BCC on Pro)
§ 02Copy-paste codeReact / Next.js · 54 lines

Drop into any Gatsby project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Gatsby page, and ship. No build-time integration required.

Form.tsxtsx54 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function EventRsvpForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New event RSVP');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Your name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="attending">Will you attend? *</label>
36 <select id="attending" name="attending" required>
37 <option value="">Choose…</option>
38 <option>Yes — count me in</option>
39 <option>Maybe</option>
40 <option>No, I can't make it</option>
41 </select>
42 <label htmlFor="guests">How many guests are you bringing?</label>
43 <input id="guests" type="number" name="guests" placeholder="0" />
44 <label htmlFor="dietary">Dietary preferences</label>
45 <input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…" />
46
47 <button type="submit" disabled={status === 'sending'}>
48 {status === 'sending' ? 'Sending…' : 'Send'}
49 </button>
50
51 {status === 'error' && <p>Something went wrong. Try again.</p>}
52 </form>
53 );
54}
ALTPrefer plain HTML? View the universal event rsvp HTML snippet25 lines
form.htmlHTML
<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New event RSVP">

  <label for="name">Your name *</label>
  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
  <label for="email">Email *</label>
  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
  <label for="attending">Will you attend? *</label>
  <select id="attending" name="attending" required>
    <option value="">Choose…</option>
    <option>Yes — count me in</option>
    <option>Maybe</option>
    <option>No, I can't make it</option>
  </select>
  <label for="guests">How many guests are you bringing?</label>
  <input id="guests" type="number" name="guests" placeholder="0">
  <label for="dietary">Dietary preferences</label>
  <input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…">

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first event rsvp submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the event rsvp into your Gatsby project

Drop the form snippet into a Gatsby page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippettsx
'use client';
  …
</form>
STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now
FROM contact@yoursite.com
New event RSVP
Maya Iyer maya@studio71.co
Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?
§ 03bEvent RSVP Form (Public / Private Events)template-specific playbook

The reason this event rsvp exists.

Webhooks into Notion / Airtable / Google Sheets · auto .ics calendar invite.

why it matters

Eventbrite, Splash, and Hopin take 3-7% of every paid ticket and charge subscription fees for the white-label option. For free events (fundraisers, private parties, conferences with sponsor-only revenue, weddings), the platform fees are pure waste. The RSVP form captures attending yes/no, guest count, plus-one names, dietary restrictions, and any custom fields (workshop preference for conferences, song requests for weddings). Webhook to a Notion / Airtable / Google Sheet for the running headcount, plus an automatic confirmation email. Final headcount goes to catering 5-7 days out, same as any platform would deliver.

route the submission
01

Capture attendance and party

Required: attending yes/no, guest count, plus-one names if applicable. Optional: dietary restrictions, song requests, workshop preference, accessibility needs.

02

Update the running list

Webhook to a Notion / Airtable / Google Sheet that the host references. Each RSVP appends a row; conditional formatting highlights special diets. Real-time headcount without spreadsheet work.

03

Confirm via email

Auto-respond with confirmation, event details, and a calendar invite (.ics file). Most guests forget the date once they've RSVP'd — calendar adds reduce no-shows by 30-40%.

§ 03cGatsby production notesnative path · deploy · gotchas

What changes when this event rsvp lives in Gatsby.

These notes come from the Gatsby platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend. Gatsby v4 had Functions running as Lambda-equivalent serverless routes; v5 removed them entirely. Result: every Gatsby contact form today uses an external service. Splitforms is a drop-in replacement — same shape as Netlify Forms (POST to a URL), same shape as Formspree, but with 5× the free monthly submissions and built-in spam filtering.

deploy notes

Gatsby builds static HTML + JS that deploys to any host: Netlify, Vercel, Cloudflare Pages, AWS Amplify, S3 + CloudFront, Gatsby Cloud (sunset 2024 — migrate). The form posts cross-origin to splitforms regardless of host. Env vars exposed to the browser bundle must be prefixed GATSBY_ — anything else is undefined client-side. The key gets bundled into the JS at build time; lock it to your domain in the splitforms dashboard. For headless Gatsby + WordPress / Contentful setups, the form lives in the React tree, not the CMS — no special CMS wiring required.

Gatsby gotcha

GATSBY_ prefix required for env vars exposed at build time

Gatsby's webpack config only exposes process.env.* variables prefixed with GATSBY_. If you write process.env.SPLITFORMS_KEY, you'll get undefined in the browser bundle. Rename to GATSBY_SPLITFORMS_KEY — and accept that it's bundled into the static JS (lock the key to your domain in the splitforms dashboard).

Gatsby gotcha

Gatsby's <Link> can't wrap a form's submit handler

Gatsby's <Link> component prevents default navigation. If you wrap your form in <Link to="/thanks"> thinking the redirect will fire, it won't — the form's submit event runs, but the navigation is suppressed. Use a hidden redirect input on the form and let splitforms handle the 302.

Gatsby gotcha

SSR + client hydration mismatch on form initial state

If you use useState('idle') in your form and render any state-dependent UI on first paint, Gatsby's static HTML and React's client render can diverge — you'll see a hydration warning. Render the form unconditionally; only render status messages inside the handler-triggered branches.

Gatsby gotcha

Gatsby v5 partial hydration changed how forms hydrate

Gatsby 5 introduced partial hydration via React Server Components. If your form is in a Server Component, the onSubmit handler won't bind. Add 'use client' at the top of the file (or use a separate ContactForm.client.jsx).

PATTERN A

Pattern A — React component (Gatsby v4/v5)

Standard React function component, useState for status. Drop into src/components/ContactForm.jsx and import on any page. Set GATSBY_SPLITFORMS_KEY in .env.production and .env.development. Use the same wiring for the event rsvp fields on this page.

pattern-a.jsxjsx16 lines
01import React, { useState } from "react";
02export default function ContactForm() {
03 const [status, setStatus] = useState("idle");
04 return (
05 <form onSubmit={async (e) => {
06 e.preventDefault(); setStatus("loading");
07 const fd = new FormData(e.target);
08 fd.append("access_key", process.env.GATSBY_SPLITFORMS_KEY);
09 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10 setStatus((await r.json()).success ? "ok" : "err");
11 }}>
12 <input name="email" type="email" required />
13 <button disabled={status === "loading"}>Send</button>
14 </form>
15 );
16}
PATTERN B

Pattern B — partial hydration (Gatsby v5)

Gatsby 5's partial hydration mounts only the components marked client-bound. Add 'use client' at the top of the form file so the onSubmit handler binds at hydration time; the rest of the page stays static. Use the same wiring for the event rsvp fields on this page.

pattern-b.jsxjsx7 lines
01// src/components/ContactForm.jsx
02"use client";
03import React, { useState } from "react";
04export default function ContactForm() {
05 const [status, setStatus] = useState("idle");
06 // ...same body as Pattern A
07}
§ 04Field-by-field rundown5 fields · names you POST

What every field actually does.

Each field below ships in the event rsvp template — rename, remove, or add your own. Splitforms accepts any name you POST.

nameREQUIRED
TEXT

Your name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Jane Builder
emailREQUIRED
EMAIL

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · jane@example.com
attendingREQUIRED
SELECT

Will you attend?

Dropdown — keeps responses normalised so you can filter the dashboard.

Yes — count me inMaybeNo, I can't make it
guests
NUMBER

How many guests are you bringing?

Standard input — splitforms accepts whatever you POST under this name.

placeholder · 0
dietary
TEXT

Dietary preferences

Logistics input you'd otherwise gather over email anyway.

placeholder · Vegan, gluten-free, allergies…
§ 06Questions9 answered

Event RSVP on GatsbyFAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this event rsvp work on Gatsby?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Gatsby site without server-side code, plugins, or SDKs. Drop the snippet into a Gatsby page or component and submissions land in your splitforms dashboard.
02How much does the event rsvp cost on Gatsby?
Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.
03Can I customize the fields?
Yes. The template ships with sensible defaults (your name, email, will you attend?, how many guests are you bringing?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the event rsvp?
A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Gatsby as on any other framework.
05Can I send the event rsvp submissions to Slack or Discord?
Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.
06Will it work on a static Gatsby site?
Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.
07Why not just use Eventbrite or Splash?
For free events, both charge subscription fees ($30-100/mo for white-label) plus per-ticket fees. The form costs $0, lives on your own domain (which matters for weddings and brand events), and the data is yours — not licensed inside their platform.
08Can I send a calendar invite (.ics) automatically?
Yes — generate an .ics file and attach to the auto-responder. Webhook to a Zapier / Make automation that crafts the .ics with event title, date, location, and notes. Most email clients render the attachment as 'add to calendar' inline.
09How do I handle plus-ones?
Add 'plus-one yes/no' and a name field that appears conditionally. For weddings, the 'plus-one allowed' is invitation-specific — capture invitation code on the form, and the webhook validates whether that invite includes a plus-one before accepting the second name.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a event rsvp on Gatsby in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Gatsby project.

Get free access key →Read the docs
founders pricing locked in · early access open