How to add a backend to a Next.js contact form
Connect a Next.js form without creating an unnecessary API route.
The browser can't handle the submission on its own.
An HTML form has to POST somewhere. Formserve is that destination — it receives the submission, screens it for spam, stores it, and sends the notifications. No server to run, no serverless function, no fragile scripts.
Connect a Next.js form without creating an unnecessary API route.
§ 01 · Context Why it still needs a backend.
In many Next.js sites, a form does not need an API route, server action, database table, or email service setup. If the form just needs to collect leads, POST it directly to Formserve and keep your app focused on the page experience.
The form POSTs to an endpoint URL, the submission is stored, and notifications are sent according to the endpoint settings. It's a safer, more maintainable replacement for fragile mailto: patterns or one-off scripts that break the first time your host changes.
§ 02 · Why More than just an email alert.
When the backend stores every submission first and notifies second, you get three things a raw SMTP relay can't give you:
Inbox plus notifications
Every submission stays searchable in the Formserve inbox — not just buried in one person's mailbox.
Spam stopped first
Allowed domains, honeypot fields, rate limits, and blocklists run before any notification is sent.
Route later if needed
Start email-only, then add Slack, webhooks, Sheets, or a CRM later without touching the form.
And because the submission is stored, delivery failures stay visible instead of disappearing into email logs. If a notification bounces, you can see it, retry it, and still have the lead.
§ 03 · Setup How to connect it.
None of these steps involve writing server code. First, make sure you have the essentials in place:
Client component when needed
Use a client component if you want inline success and error state.
Endpoint URL
The Formserve endpoint URL is safe to use in frontend code.
Allowed domain
Add the deployed domain before launch.
Honeypot
Include _honeypot to keep CAPTCHA out of the user experience.
§ 04 · Example Keep the form simple.
There's nothing special about the markup. The only required change is the action attribute. The hidden _honeypot input is the one spam-prevention field worth adding by hand:
"use client";
export function ContactForm() {
async function submit(event) {
event.preventDefault();
const res = await fetch("https://formserve.io/f/YOUR_ENDPOINT_KEY", {
method: "POST",
body: new FormData(event.currentTarget)
});
if (!res.ok) throw new Error("Submission failed");
}
return (
<form onSubmit={submit}>
<input name="_honeypot" tabIndex="-1" autoComplete="off" className="hidden" />
<input name="email" type="email" required />
<textarea name="message" required />
<button>Send</button>
</form>
);
}
fetch required for the basic case.A plain action + method="POST" works with zero JavaScript. Reach for fetch only when you want to stay on the page and show a custom success state.
Before you launch
- ✓ Use a client component only if inline state is needed.
- ✓ Keep validation in the UI.
- ✓ Add production domain to allowed domains.
- ✓ Check the Formserve inbox after deploy.
Common mistakes
- ! Building a custom API route for simple lead capture.
- ! Putting secret keys in NEXT_PUBLIC variables.
- ! Forgetting the honeypot field.
- ! Testing only in preview mode.
Get a working endpoint in under a minute.
Paste the URL into your form's action and send a test. Free up to 100 submissions / month — no credit card.
§ 05 · FAQ Common questions.
Do I need to build a backend for a Next.js contact form?
Does this work with Next.js?
Will connecting Formserve change my form design?
How do I stop spam without a CAPTCHA?
Keep reading
All guides →HTML form
Point a normal HTML form at Formserve and receive submissions instantly.
React contact form
Use FormData from your existing React component and POST it to Formserve.
Vue contact form
Submit a Vue form to Formserve while keeping your current UI intact.