Build forms and data pages, point them at n8n, and paste one script tag. Visitors read, add and change data; your workflows do the work.
Works on any HTML page: WordPress, Webflow, GitHub Pages. No server code.
Request a quote
form2wf sits between your website and n8n. It shows the form, checks who's using it, and passes everything to your workflow.
Fields, columns, repeatable groups, tables and file uploads, styled with your theme. Or let an AI agent build it.
Paste a webhook URL, or connect your n8n server and pick workflows from a list. Secret headers stay on our servers.
Two script tags on your page. The form loads with your theme and talks to your workflows from there.
<div id="f2wf-contact"></div>
<script src="https://form2wf.com/f2wf.js"></script>
<script>
f2wf.load("your-org", "contact");
</script>A form can be a whole data page. Its onload webhook lists records from your workflow, and buttons and row actions create, update and delete them. Each one calls the workflow you choose, so n8n stays your only backend.
Orders
3 open, loaded from your workflow
/webhook/ordersloads the table/webhook/ordersNew order/webhook/orders/{{row.id}}Approve, Edit/webhook/orders/{{row.id}}DeleteAnything where a web page needs to collect, show or change data, and n8n already knows what to do with it.
Quote requests, applications and bookings that land in your inbox, CRM or spreadsheet the moment they're sent.
List records from your workflow, then create, edit and delete them from the same page. Your database stays behind n8n.
Clients sign in with their Microsoft account and see their own projects, invoices and requests. No accounts or passwords for you to manage.
An approval queue, an ops console, an admin page over a spreadsheet or database. Staff click; n8n does the work.
Step-by-step flows that price, check availability and take payment. Your workflow decides where the visitor goes next.
A form in, an AI answer out: contract review, cover letters, ticket triage. n8n runs the model; the page shows the result.
form2wf has an MCP server, so Claude, Cursor or any MCP client can create forms and data pages, wire their webhooks, check submissions and set up access. Each API key has an access level, and never goes beyond the role of the person who made it.
claude mcp add --transport http form2wf https://form2wf.com/mcp \
--header "Authorization: Bearer f2w_your_key"Make a job application form with a résumé upload that posts to my n8n hiring workflow, and give me the embed code.
get_config_referencecreate_formJob application, 6 fieldsget_embed_snippetDone. Job application has six fields including a résumé upload, and posts to /webhook/hiring. Paste the snippet where the form should appear.
Visitors' browsers talk to form2wf, never to n8n directly. Webhook URLs and the headers that protect them are stored on the server and never appear in the page.
Start free. Move to Pro when your pages carry real traffic. Compare plans
$0 / month
For trying it out and small sites.
$29 / month
For businesses and agencies running real traffic.
Custom
For large volumes, or running form2wf on your own servers.
Still wondering? The docs cover every detail.
Forms post JSON to any URL that accepts a webhook, so Make, Zapier or your own API work too. form2wf is built around n8n: you can connect your n8n server to pick workflows from a list, and the docs include ready-made n8n recipes.
Yes, and change it too: full CRUD. An onload webhook loads records into fields and tables when the page opens, and buttons and row actions create, update and delete them through your workflows. You get a working data page without writing a backend.
Yes. form2wf calls your webhook from its own servers, and the hosted service only calls public addresses. If you run form2wf yourself next to n8n, the organization owner can allow calls to addresses on the local network.
A JSON body with the submitted values under data, plus metadata (time, page origin, browser) and who is signed in when the form requires sign-in. Files arrive as multipart uploads. The webhook docs show every payload.
Yes, two ways. Verified forms let visitors sign in with their Microsoft account, with no accounts for you to manage, optionally only from the email domains you choose. Protected forms use form users you create, by user or by role. Either way form2wf checks access on every request and tells your workflow who it is.
Yes. form2wf has an MCP server: give Claude, Cursor or any MCP client an API key and it can create forms, wire webhooks, read submissions and manage access, limited to the access level you choose.
form2wf stores your form definitions and a log of each submission so you can see what was sent and what your workflow answered. Your records live wherever your workflows keep them: a database, a spreadsheet, your CRM.
The quick start takes you from an empty n8n workflow to a working form on a web page.