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.
Event RSVP · Next.js
Attendance confirmation with headcount and dietary needs. Free for 500 submissions per month — no backend, no SDK, no plugin.

Copy-paste code
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Next.js page, and ship. No build-time integration required.
'use client';
import { useState, type FormEvent } from 'react';
export default function EventRsvpForm() {
const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
async function onSubmit(e: FormEvent<HTMLFormElement>) {
e.preventDefault();
setStatus('sending');
const data = new FormData(e.currentTarget);
data.set('access_key', 'YOUR_ACCESS_KEY');
data.set('subject', 'New event RSVP');
const res = await fetch('https://splitforms.com/api/submit', {
method: 'POST',
body: data,
headers: { Accept: 'application/json' },
});
const json = await res.json();
if (json.success && json.payment_url) {
// Payment form: finish the payment on the secure Stripe page.
window.location.href = json.payment_url;
return;
}
setStatus(json.success ? 'sent' : 'error');
if (json.success) e.currentTarget.reset();
}
if (status === 'sent') return <p>Thanks — we’ll be in touch.</p>;
return (
<form onSubmit={onSubmit}>
<label htmlFor="name">Your name *</label>
<input id="name" type="text" name="name" placeholder="Jane Builder" required />
<label htmlFor="email">Email *</label>
<input id="email" type="email" name="email" placeholder="jane@example.com" required />
<label htmlFor="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 htmlFor="guests">How many guests are you bringing?</label>
<input id="guests" type="number" name="guests" placeholder="0" />
<label htmlFor="dietary">Dietary preferences</label>
<input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…" />
<button type="submit" disabled={status === 'sending'}>
{status === 'sending' ? 'Sending…' : 'Send'}
</button>
{status === 'error' && <p>Something went wrong. Try again.</p>}
</form>
);
}Next.js + 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 fetch('/api/submit') call. The event rsvp works identically in App Router and Pages Router — it's just a FormData 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.

Event RSVP fields
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?. Rename, remove, or add your own — splitforms accepts any name you POST.

Template playbook
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.

Setup
Three actions stand between you and your first event rsvp submission — no backend, no database, no CAPTCHA library.
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
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.
Dashboard updates live on Free. Free includes owner email delivery; Starter adds signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
How SplitForms works
Connect your form, collect every submission, and send data where it needs to go — without building backend infrastructure.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
SplitForms works with the destinations you route to and the platforms you build on — from Slack and Sheets to WordPress, Shopify, and Next.js.

Trusted by indie teams and agencies shipping forms worldwide
Testimonials
40 quotes on record — from indie hacks to agency migrations.
“I replaced a Lambda + DynamoDB + SES contact form with six lines of HTML. It took eleven minutes, and the dashboard is better than what I was going to build.”
“We migrated 14 client sites off Formspree in a single weekend. The price is a third of what we paid, the API is more honest, and the spam filter actually works.”
“The webhook payload is signed, idempotent, and well-shaped. It reads like code from a competent team, not a CRUD app held together with duct tape.”
“I stopped reaching for Typeform on small marketing sites. splitforms covers 90% of the use case at none of the bloat.”
“I onboarded our whole agency in an afternoon. The MCP integration meant Cursor literally dropped the form straight into our client repos for us.”
“The free plan gave me 500 submissions before I paid a cent, and Pro is five dollars a month. I've spent more on coffee deciding which backend to use.”
“Spam went from forty junk entries a day to zero, with no reCAPTCHA puzzle ruining the form. The honeypot and time-trap just quietly do their job.”
“Point the form action at one endpoint and you're done. No SDK, no client library, no build step. This is how a form backend should feel.”
“Leads land in Slack the second someone submits, and a copy goes to Google Sheets for the sales team. I wired both up in under ten minutes.”
“I run a static Hugo site on a five-dollar VPS. splitforms gave it a real contact form without me standing up a single server.”
Common questions
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.
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.
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.
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.
Yes. Webhooks are available on paid plans, 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.
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.
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.
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.
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.
Simple pricing
Choose a plan that fits your workflow — from a free form endpoint to full automations, exports, and higher submission limits.
Free forever
For side projects and indie devs.
For agencies and growing products.
Pay $59. 3 years sorted.
No credit card required on Free • Cancel anytime