Getting started
Form2Workflow documentation
Form2Workflow (form2wf) turns n8n workflows into the backend for any website. Build a form in the dashboard, point it at an n8n webhook, and drop one script tag on your site — no server code.
What form2wf does#
form2wf sits between a static website and your n8n instance. It renders forms and data pages on your site, sends what visitors submit to your n8n workflows, and brings data back from n8n to fill forms and tables. Your workflows are the backend: send email, write to a database or CRM, call an AI model, anything n8n can do.
Forms21 field types, charts, nested objects, repeatable groups, file uploads, multi-column layouts.
Data pagesLoad data from n8n into tables and read-only fields, with row actions and buttons.
Verified & protected formsSign in with Microsoft (no accounts to manage), or your own form users and roles.
AI agents (MCP)Let Claude or any MCP client build and manage forms with a scoped API key.
How the pieces fit#
request flow
Visitor's browser form2wf Your n8n
───────────────── ─────── ────────
f2wf.js loads form ───────▶ GET form config
(+ onload webhook) ─────────▶ Webhook ▶ fetch data ▶ Respond
form renders ◀─────── config + data ◀─────────
visitor submits ───────▶ POST /submit ─────────▶ Webhook ▶ email / DB / AI ...
"Thank you!" ◀─────── success ◀───────── 2xxform2wf stores the form definitions, enforces quotas, rate limits and login rules, logs every submission, and keeps your webhook URLs and header secrets off the page — the browser never sees them.
Start here#
Quick startA working contact form wired to n8n in about ten minutes.
Field referenceEvery field type with a copy-paste sample.
Webhooks & payloadsExactly what n8n receives and what it should send back.
MCP server & API keysConnect Claude Code, Claude Desktop, Cursor or an n8n AI agent.
n8n recipesReady-made workflow patterns: email, sheets, CRUD, uploads.
Best practicesSecurity, reliability and performance guidance.
Key terms#
| Term | Meaning |
|---|---|
| Organization | Your workspace. Forms, themes, form users and API keys all belong to one organization. Its slug appears in embed snippets and hosted URLs. |
| Form | A page definition: settings (name, slug, webhooks) plus a config JSON describing its fields. Also called an endpoint in the API. |
| Submit webhook | The n8n URL that receives submissions (n8n_webhook_url). No submit webhook means no submit button — a read-only data page. |
| Onload webhook | An n8n URL called when the form loads. Its response pre-fills fields and feeds tables. |
| Form user | Someone who signs in to use a login-protected form. Separate from dashboard team members. |
| Team member | A dashboard user with a role: owner, admin, creator or user. |
| API key | An f2w_ key that lets an AI agent act in your organization through the MCP server, at a chosen access level. |