AI form prompt generator
Pick your AI tool, the kind of form and its fields, and copy a prompt that makes the AI build a form that really emails you. It works with Lovable, Bolt, v0, Replit, Cursor, Claude Code, ChatGPT, Claude, Gemini, Framer, Webflow and WordPress, and it’s free.
Write your prompt
No key yet? Get one free; the prompt works with a placeholder too.
Your prompt
How to use the prompt generator
- Choose the AI tool you build your site with.
- Pick a form type. Edit the fields: one per line, with a * after the required ones.
- Say where the form goes and what happens after sending: a thank-you message in the form, or your own thank-you page.
- Paste your FormDoc access key (free at app.formdoc.dev), or leave the placeholder and add it later.
- Copy the prompt into your AI tool, then send yourself a test message.
Why a better prompt gives a working form
Ask an AI tool for “a contact form” and you usually get a good-looking form that sends nothing. The AI fills the gap it can’t see: there’s no server to receive the message, so it shows a fake “Thanks!” or tries to write an API route your host can’t run. A precise prompt removes the guesswork. It names the endpoint, the hidden access key, the field names and the exact success and error behaviour, and it rules out the usual shortcuts.
What the prompt asks for
| Your tool | What the prompt asks it to build |
|---|---|
| Lovable, Bolt.new, v0, Replit | A form in the app that sends with fetch and shows a real success or error message |
| Cursor, Claude Code, Windsurf, GitHub Copilot | The same, using your project’s own framework and components |
| ChatGPT, Claude, Gemini | Complete code, with where to put it |
| Framer, Webflow, WordPress | Plain HTML for a custom code block, with the thank-you message shown in place |
Every prompt includes the field names, labels, required fields, the hidden access_key, a hidden botcheck spam trap, and a line that rules out fake success, mailto: and server routes.
Tips for prompting AI tools about forms
- Name the fields. Field names become the labels in your email, so short, clear names like
name,emailandmessageread best. - Ask for the error path too. A form that only handles success hides problems. The prompt asks the AI to show FormDoc’s error message and keep what the visitor typed.
- Keep the design. In an existing project, ask the AI to change how the form submits, not how it looks.
- Test once. Send yourself a message after the AI finishes. If nothing arrives, paste the code into the AI form checker.
Coding assistants can do even more: connect FormDoc’s MCP server and the assistant can create the form for you. For a general guide, read forms on AI-built websites.
Common questions
Do I need an access key before I generate the prompt?
No. The prompt works with a YOUR_ACCESS_KEY placeholder; replace it with your real key afterwards. Getting a key is free and takes a minute at app.formdoc.dev.
Why does the prompt tell the AI not to create an API route?
On static hosts and in many AI builders there’s no server to run it, so the route never sends anything. FormDoc receives the form directly, so no server code is needed.
Can I use the prompt for a form that already exists?
Yes. Ask your AI tool to apply the requirements to the existing form. To see exactly what’s wrong first, paste the form into the AI form checker.
Is anything I type sent to FormDoc?
No. The prompt is written in your browser. Nothing is sent until you put the finished form on your site and a visitor submits it.