EVENT RSVP · NEXT.JS

Event RSVP for Next.js

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

Get free access key Copy the code

500/mo free·no card·drop-in for Next.js

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

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Next.js + Event RSVPplatform-specific integration guide

Why Next.js developers choose splitforms for event rsvp

Next.js Server Actions handle the submit side but still leave you wiring SMTP, spam filtering, file uploads, and a dashboard. splitforms replaces all of that with one <code>fetch('/api/submit')</code> call. The event rsvp works identically in App Router and Pages Router — it's just a <code>FormData</code> POST, no router-specific magic. Because Next.js pre-renders pages, the form HTML is in the DOM before any JavaScript executes, meaning instant Time-to-Interactive. The honeypot field is invisible to users but catches bots that scrape rendered HTML — especially important for Next.js sites where the form HTML is statically generated and predictable.

§ 00Quick answerReact / Next.js · events

Yes — this is the shortest safe path for Next.js.

Use the React / Next.js snippet on this page, keep the event rsvp fields visible in your Next.js 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 next.js reality

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 × Next.jswhy this combination, in 80 words

Built for Next.js developers who hate operating a backend.

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

Splitforms is the form backend for Next.js 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 Next.js project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Next.js 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

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the event rsvp into your Next.js project

Drop the form snippet into a Next.js 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

Capture attendance and party

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

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.

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%.

§ 03cNext.js production notesnative path · deploy · gotchas

What changes when this event rsvp lives in Next.js.

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

without splitforms

Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out. Server actions made the wiring slightly tidier in Next 14+, but the operational cost stays the same: a function with a runtime, a database, an outbound email provider, an inbox to monitor, and your name on the spam-filter incident report. Splitforms collapses all of that into a POST to a single URL.

deploy notes

On Vercel, the form works on every plan tier — server actions and client components both run inside the same edge/serverless function. Don't put the splitforms fetch inside a Vercel cron or background function (it's user-facing, latency matters). On Netlify with the Next runtime, server actions need the latest @netlify/plugin-nextjs (≥5.6). For self-hosted / Docker: configure output: 'standalone' in next.config.ts and pass SPLITFORMS_KEY as a runtime env var — never bake it into the image. For static export (output: 'export'), use the client-component path only — server actions aren't supported in static mode.

Next.js gotcha

Don't expose your access key client-side without domain locking

Inlining access_key in a "use client" component makes the key visible to anyone who views source. That's fine if you've enabled allowed-domains in your Splitforms dashboard (Settings → Security) — anyone copying the key from your bundle can't use it from a different origin. If you haven't, use a server action so the key stays on the server.

Next.js gotcha

Server actions need `'use server'` and a real form, not fetch

If you submit to a server action via <form action={myAction}>, Next handles the FormData serialization for you. If you call the action manually with fetch, you have to set the right Content-Type and stringify yourself. Pick one path and stick with it — mixing causes 'Server Action invalid' errors.

Next.js gotcha

App Router + Suspense + useSearchParams = static-prerender bailout

If your form reads ?next=/something to support post-submit redirects, useSearchParams forces the page out of static generation. Either wrap the inner component in a <Suspense fallback={<Skeleton/>}> so the wrapper still prerenders, or accept dynamic rendering for the form route only.

Next.js gotcha

Vercel Edge runtime can't read FormData from `multipart/form-data`

If your route handler uses export const runtime = 'edge' and the form posts as multipart (file inputs), it'll silently miss fields. Use application/x-www-form-urlencoded or remove the edge runtime declaration.

PATTERN A

Pattern A — server action (no client JS, key stays server-side)

Form posts to a server action; the action appends the access key from process.env.SPLITFORMS_KEY and proxies to splitforms. Works without JavaScript, key never reaches the bundle. Use the same wiring for the event rsvp fields on this page.

pattern-a.tsxtsx10 lines

01// app/actions/contact.ts
02"use server";
03import { redirect } from "next/navigation";
04 
05export async function submitContact(formData: FormData) {
06  formData.append("access_key", process.env.SPLITFORMS_KEY!);
07  const res = await fetch("https://splitforms.com/api/submit", { method: "POST", body: formData });
08  if (!(await res.json()).success) throw new Error("Submission failed");
09  redirect("/thanks");
10}

PATTERN B

Pattern B — client component with fetch and inline status

'use client' component using useState for a 4-state status machine. Lets you show a spinner, inline errors, optimistic resets — at the cost of a hydration boundary. Use NEXT_PUBLIC_SPLITFORMS_KEY and rely on splitforms' domain-locking for safety. Use the same wiring for the event rsvp fields on this page.

pattern-b.tsxtsx17 lines

01"use client";
02import { useState } from "react";
03export default function ContactForm() {
04  const [s, setS] = useState<"idle" | "loading" | "ok" | "err">("idle");
05  return (
06    <form onSubmit={async (e) => {
07      e.preventDefault(); setS("loading");
08      const fd = new FormData(e.currentTarget);
09      fd.append("access_key", process.env.NEXT_PUBLIC_SPLITFORMS_KEY!);
10      const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
11      setS((await r.json()).success ? "ok" : "err");
12    }}>
13      <input name="email" type="email" required />
14      <button disabled={s === "loading"}>{s === "loading" ? "…" : "Send"}</button>
15    </form>
16  );
17}

§ 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

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…

§ 05Event RSVP on other frameworks21 frameworks · same backend

One backend. Every framework.

The same event rsvp template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Event RSVP on Next.js — FAQ.

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

01Does this event rsvp work on Next.js?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Next.js site without server-side code, plugins, or SDKs. Drop the snippet into a Next.js page or component and submissions land in your splitforms dashboard.

02How much does the event rsvp cost on Next.js?

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 Next.js 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 Next.js 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.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Next.js5 adjacent patterns

Ship a event rsvp on Next.js in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Event RSVP for Next.js

Why Next.js developers choose splitforms for event rsvp

Yes — this is the shortest safe path for Next.js.

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

Built for Next.js developers who hate operating a backend.

Drop into any Next.js project.

Generate, embed, receive.

Generate a free splitforms key

Paste the event rsvp into your Next.js project

Receive submissions

The reason this event rsvp exists.

Capture attendance and party

Update the running list

Confirm via email

What changes when this event rsvp lives in Next.js.

Don't expose your access key client-side without domain locking

Server actions need `'use server'` and a real form, not fetch

App Router + Suspense + useSearchParams = static-prerender bailout

Vercel Edge runtime can't read FormData from `multipart/form-data`

Pattern A — server action (no client JS, key stays server-side)

Pattern B — client component with fetch and inline status

What every field actually does.

Your name

Email

Will you attend?

How many guests are you bringing?

Dietary preferences

One backend. Every framework.

Event RSVP on Next.js — FAQ.

splitforms vs everything else.

Other ready-to-ship Next.js forms.

Ship a event rsvp on Next.js in 60 seconds.