Next.js guide

How to add a backend to a Next.js contact form

Connect a Next.js form without creating an unnecessary API route.

No backend API route Honeypot spam trap Works with any host
FS Formserve Team Product guides
Next.js Stack
4 steps setup Walkthrough
Form <form action="…" method="POST"> in the browser
Formserve Validates & filters spam, then stores the submission
Deliver Notifications sent to email, Slack, Sheets, or webhooks
Why a backend at all

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.

1
Find the form component — Update the existing component instead of creating a separate backend route.
2
Use FormData — Let the browser collect named fields from the form.
3
Submit directly — POST to the Formserve endpoint from the client component.
4
Confirm in production — Deploy and send a real test from the final domain.

§ 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:

next-js.html — minimal
"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>
  );
}
No 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.

Try without signup

§ 05 · FAQ Common questions.

Do I need to build a backend for a Next.js contact form?
No. Formserve is the backend. You point the form at a Formserve endpoint URL and it stores submissions, filters spam, and sends notifications, so you never build or host a server yourself.
Does this work with Next.js?
Yes. A Next.js form submits standard named fields, and Formserve accepts them the same way any HTML form posts data — no SDK or plugin required.
Will connecting Formserve change my form design?
No. You keep your existing markup and styling. Only the submission behaviour changes so the form posts to your endpoint instead of a server you maintain.
How do I stop spam without a CAPTCHA?
Add the hidden _honeypot field shown in the code sample and set a spam protection level on the endpoint. Formserve blocks bots invisibly instead of showing a CAPTCHA.
FS
Formserve Team
We build the form backend behind thousands of HTML forms — from one-page contact forms to high-traffic launch pages.
Next.js Guide No-code