Make every form actually send, wherever you build it.
Step-by-step guides for AI builders, coding agents, frameworks and site builders. Each one ends with a working form, not a Supabase table and an email key.
AI builders
They generate a polished front end. MakeTheForm is the backend they leave out.
Make your Lovable contact form actually send, without Supabase or an edge function.
Read the guide Bolt.newAI builderA contact form backend for whatever framework Bolt picks for your app.
Read the guide v0AI builderForm handling for v0-generated React components, with success and error states.
Read the guide ReplitAI builderKeep your Replit app stateless and send form submissions to one inbox.
AI builder guideCoding agents
One prompt, and the agent edits your submit handler instead of inventing a backend.
Paste the prompt in your session or keep it in CLAUDE.md for every form.
Form backend for AI-built websites CursorCoding agentUse it in Agent mode, or save it as a project rule so new forms stay wired.
Form backend for AI-built websites GitHub CopilotCoding agentWorks in Copilot agent mode in VS Code with the same prompt.
Form backend for AI-built websitesFrameworks
A fetch call in your submit handler. JSON in, JSON out, errors shown inline.
React contact form in depth: loading state, honeypot, errors that keep what people typed.
Read the guide Next.jsFrameworkClient components or plain HTML forms. No route handler needed.
Read the guide AstroFrameworkStatic pages with a working form, no adapter or server output required.
Read the guide HugoFrameworkA partial, a shortcode and one site param. The site stays fully static.
Read the guide VueFrameworkA small submit handler for Vue 3 and Nuxt, with the same JSON responses.
fetch guide SvelteKitFrameworkWorks with static adapters. Progressive enhancement optional.
fetch guide Plain HTMLFrameworkSet the form’s action to your endpoint. The simplest integration there is.
Read the guideSite builders
Point the builder’s form at your endpoint and keep its design.
Replace Webflow’s form handling with your own endpoint and inbox.
Read the guide FramerSite builderAdd your endpoint as the form’s webhook for spam filtering and storage.
Read the guide CarrdSite builderSend to URL on Pro Plus, with Carrd’s own success message.
Read the guide WordPressSite builderHeadless or classic themes, without a form plugin.
HTML forms guideWhere submissions go
Every submission lands in your inbox. Paid plans also send it wherever the work happens.
Instant on Pro and Agency, a daily digest on Free. Reply-To is the sender.
Email notifications SlackProDestinationPost each submission to a channel.
Set up Slack WebhooksProDestinationSigned and retried. Up to 3 per form on Pro, 10 on Agency.
Webhooks guide DiscordProDestinationPost each submission to a channel.
Set up Discord AirtableProDestinationAdd a row to a base for each submission.
Set up Airtable GitHubProDestinationOpen an issue per submission.
Set up GitHub Google SheetsSoonDestinationAppend a row per submission.
All integrationsHosting
Static hosting works as-is. The form posts straight to MakeTheForm, so there’s no server to deploy.
- VercelStatic and serverless deploys. No server code needed for the form.HTML forms guide
- NetlifyUse MakeTheForm instead of Netlify Forms to keep one inbox across hosts.HTML forms guide
- Cloudflare PagesWorks on fully static builds.HTML forms guide
- GitHub PagesStatic HTML only, so an external endpoint is the only way to receive forms.See guide
- RenderStatic sites and web services alike.HTML forms guide
Don’t see your platform? If it can send a POST, it works.
Every guide above uses the same endpoint and the same JSON responses. Start from plain HTML or the API reference.