Webflow · CMS collections

Your Webflow forms collect data. Form to CMS writes it into your CMS automatically.

Every Webflow form submission that lands in an inbox is a missed opportunity. Form to CMS intercepts your form submissions, maps each field to the right CMS collection field, handles image uploads through Webflow's asset pipeline, and logs every write — so you stop copying data by hand and start building CMS content in real time.

Webflow OAuth · Setup in under 5 minutes · Free tier — 50 submissions/month

Image routing
Webflow assets
Success rate
98.4%
Live routing
Active
Last submission
2m ago
How it works

Four steps from form to CMS item.

Connect once. Form to CMS handles the rest — intercepting submissions, mapping fields, routing images, and writing CMS items without any custom backend.

/01

Connect your Webflow workspace

OAuth sign-in. Form to CMS links to your Webflow workspace and reads your CMS collections. Connection takes under 60 seconds. No API key setup, no developer required.

/02

Create a form and add the embed snippet

Create a form in Form to CMS, copy the one-line embed snippet, and paste it into your Webflow page. The widget intercepts submit events and routes them to your Form to CMS endpoint — one script tag, nothing else.

/03

Map form fields to CMS fields

In the field mapping editor, point each form field name to the matching CMS collection field. Set the type coercion — text, image, or date — so each value lands in the right format for Webflow.

/04

Monitor submissions in real time

Every submission is logged with status (received, writing, done, or failed), ingress mode, and timestamps. The submission log auto-refreshes every 30 seconds so you always know what's happening.

What you get

Four things Form to CMS handles so you don't have to.

Connect

Webflow OAuth connection

One-time OAuth connection links Form to CMS to your Webflow workspace. It reads your CMS collection schemas and accepts re-authorization every 90 days automatically. No API keys to rotate, no webhooks to configure manually — just OAuth and you're set.

Mapping

Field mapping with type coercion

Map any form field name to any CMS collection field in the visual editor. Set type coercion — text for plain strings, image for file uploads routed through Webflow's asset pipeline, date for ISO date fields. Free tier maps all fields to a single rich-text CMS field; Standard unlocks custom per-field mapping.

Embed

One-line embed snippet

Add a single script tag to any Webflow page — or any site with an HTML embed block. The widget finds the form by its ID, intercepts the submit event, and POSTs field data to Form to CMS. Allowed-origin enforcement rejects submissions from unlisted domains with 403 before the payload is parsed.

Monitor

Live submission log

Every submission is logged with status (received → writing → done, or failed), ingress mode (embed or webhook), image presence, and timestamps. Aggregate stats show total, done, failed, and success rate per form. Auto-refreshes every 30 seconds — no manual reloading required.

Pricing

Start free. Upgrade when your forms are serious.

Free tier gets you routing and a live submission log. Standard unlocks custom field mapping, image routing, and unlimited submissions.

Free
$0 / month

50 submissions per month. Route forms to CMS and monitor in real time.

  • 50 submissions / month
  • 1 Webflow workspace connection
  • Default field mapping (all fields → rich-text)
  • Embed snippet for any Webflow page
  • Live submission log with 30-second refresh
  • Community support
Start Free
Security & reliability

Your form data. Written once, logged every time.

Webhook signature verification

Every form creation generates a one-time webhook secret — shown once at creation, never stored in plaintext. Inbound submissions are verified against the HMAC signature before processing. Requests without a valid signature are rejected before touching your CMS.

Tenant-isolated submission logs

Row-level security ensures your form submissions and field mappings are never accessible to another tenant — not just at the application layer, but at the database level. Each submission log is scoped to your account with composite foreign key constraints.

Allowed-origin enforcement

Configure a list of allowed origins per form. Embed submissions from any origin not on the list are rejected with 403 before the payload is parsed. Your form endpoint is private to your domains — not publicly writable by anyone who finds the script tag.

Questions

Straight answers.

Something not answered here? Email us directly.

Yes — Form to CMS needs write access to your Webflow CMS collections so it can create new items from form submissions. It reads your collection schemas to power the field mapping editor, and writes new CMS items when a submission arrives. It does not modify existing CMS items, delete anything, or touch your Webflow site's design or published pages.
The embed snippet is a single script tag you copy from your Form to CMS dashboard and paste before the closing body tag on any Webflow page. The script finds the form by its HTML id attribute, intercepts the submit event, and POSTs the field data to Form to CMS. No Webflow custom code plan is required — a standard embed block works.
Three coercion types are supported: text (plain string to a CMS text or rich-text field), image (file upload routed through the Webflow asset pipeline to a CMS image reference), and date (ISO date string to a CMS date field). Custom field mapping requires the Standard plan; the Free tier writes all fields to one rich-text CMS field using the default mapping.
A submission is any inbound form payload that passes signature verification and origin allow-listing — whether it arrives through the embed snippet or a Webflow native webhook. Failed submissions (invalid signature, rejected origin, or a Webflow API error) are logged but do not count toward your monthly submission limit. The Free tier allows 50 successful submissions per calendar month; Standard is unlimited.
Webflow's OAuth token requires re-authorization every 90 days. When re-authorization is due, Form to CMS marks the integration as reauth_required and shows a reconnect banner the next time you sign in. Submissions that arrive during a reauth window are queued, not dropped, and processed once you reconnect.
When a form field has the "image" coercion, Form to CMS receives the uploaded file, uploads it to Webflow's asset pipeline, and writes the resulting Webflow asset reference to the mapped CMS image field. From your user's perspective, they upload a file in a normal HTML file input. From your CMS perspective, a Webflow asset reference appears in the right field. Image routing requires the Standard plan.
The embed snippet works on any site that can load an external script tag — Framer, Squarespace, or custom HTML pages. The CMS target is always a Webflow CMS collection. If you use a Webflow native form webhook, you can point it at your Form to CMS webhook endpoint and the payload will be processed exactly like an embed submission.
Cancel any time. No cancellation fees. Your Webflow connection is revoked, your submission logs are retained for 30 days, and your field mapping configurations are deleted. Existing CMS items that Form to CMS already wrote to Webflow are not affected — they remain in your Webflow CMS after cancellation.

Stop copying form data into your CMS by hand.

Connect your Webflow workspace now. OAuth sign-in, field mapping editor, and a live submission log ready in under 5 minutes. Free tier — 50 submissions per month, no card required.

Free plan · No card required · Cancel anytime

Connect Webflow View privacy policy