Formserve
Features Templates Pricing Docs Blog FAQ
Sign in Create endpoint
Codex guide

How to add a backend to a Codex form backend

Use Codex to make a minimal safe change that connects your form to Formserve.

No backend API route Honeypot spam trap Works with any host
FS Formserve Team Product guides
Codex Stack
4 steps setup Walkthrough
Try without signup Read the docs
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.

Use Codex to make a minimal safe change that connects your form to Formserve.

§ 01 · Context Why it still needs a backend.

Codex is a good fit when you want a constrained implementation change and a clear summary of touched files. Formserve keeps the task small: update the existing form to POST to the endpoint URL, preserve the design, and avoid adding custom backend infrastructure unless the project truly needs it.

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:

Existing form component

The form should already exist in the project so Codex edits the right file.

Endpoint URL

Create the endpoint in Formserve first and copy the public form URL.

Minimal-change instruction

Tell Codex to preserve styling and avoid unrelated refactors.

Field names

Inputs still need real HTML name attributes even if state management already exists.

1
Generate the Formserve AI prompt — Select Codex so the prompt emphasizes a minimal safe code change.
2
Apply the change to the current form — Update method, action, _honeypot, and submit feedback only where needed.
3
Review changed files — Confirm Codex did not introduce a new backend route or broad refactor.
4
Test end to end — Submit from the running app and verify the lead appears in the Formserve inbox.

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

codex.html — minimal 
Update the existing form in this project to submit to Formserve.

Use this endpoint:
https://formserve.io/f/YOUR_ENDPOINT_KEY

Requirements:
- Make the minimal safe code change
- Preserve the current UI and styling
- Keep method POST
- Ensure all fields have correct name attributes
- Add a hidden _honeypot field
- Show a success and error state after submit
- Explain which files changed
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

  • ✓ Confirm Codex changed the correct form file.
  • ✓ Verify name attributes exist on the rendered inputs.
  • ✓ Send a real submission, not only a mocked request.
  • ✓ Check the inbox before enabling notifications and integrations.

Common mistakes

  • ! Letting Codex introduce a new API route for a simple frontend form.
  • ! Ignoring missing name attributes because the component already uses local state.
  • ! Skipping the hidden _honeypot field.
  • ! Accepting broad code churn instead of a small wiring change.

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 Codex form backend?
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 Codex?
Yes. A Codex 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.
Codex Guide No-code

Keep reading

All guides →
Cursor

Cursor form backend

Give Cursor a generated prompt that wires your existing form to Formserve.

4 steps · Setup guide
Bolt

Bolt form backend

Connect a Bolt-generated website form without building a backend API.

4 steps · Setup guide
v0

v0 form backend

Use Formserve as the backend for forms generated by v0.

4 steps · Setup guide