Questions
Straight answers.
Everything we get asked about Form to CMS, Webflow form routing, field mapping, and how the submission log works. Something not covered here? Visit support or 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 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.
When you create a form, you can specify a list of allowed origins (e.g. https://example.com). Embed submissions from any origin not on that list are rejected with a 403 before the payload is parsed. This prevents your form endpoint from being publicly writable by anyone who finds the script tag. You can manage allowed origins in your form settings at any time.
The Free plan is $0/month and covers 50 successful submissions per month, one Webflow workspace connection, the default field mapping (all fields to one rich-text CMS field), the embed snippet, and the live submission log. Standard is $49/month and adds unlimited submissions, unlimited workspace connections, custom per-field mapping, image routing via the Webflow asset pipeline, and date coercion. Standard includes a 14-day free trial with no card required. See the full breakdown on the pricing section.
Cancel any time. No cancellation fees. Your Webflow connection is revoked, your submission logs are retained for 30 days for your reference, 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.