Webflow support: what to check when forms, pages or integrations fail
Written by Derrick KityoFind where your Webflow journey stops: the published page, form submission, email notification or CRM handoff. Then get the right person to help.

A form can show a success message while the enquiry never reaches the person who needs it. A page can work on your Webflow staging address and fail on your own domain. Those are different faults, and they need different checks.
When I'm narrowing down a website issue, I want to find the last step that worked. Start with the visitor's journey, record what happens, then follow the evidence before changing settings.
Start with one repeatable failure
Write down the exact page URL, the action you took, the expected result and what actually happened. Include the time and timezone, device and browser. “The contact form shows an error after Submit on Safari” gives someone a useful starting point; “Webflow is broken” doesn't.
Try the same journey in a private window and another browser. If only one setup fails, look at extensions, stored browser data and browser-specific behaviour. If several people can reproduce it, the fault probably needs investigation beyond that one browser.
Check Webflow's status page for a matching incident. A clear status page doesn't rule out an issue with your site. Keep your evidence and move to the affected part of the journey.
Before editing, record the current configuration and agree how to undo the change. Use staging for experiments where possible. A live form test can send emails, create contacts or start sales automations, so arrange it with the people receiving those records first.
If a page is missing or shows the wrong version
Compare the exact path on your published staging address and custom domain. A preview in the Designer isn't enough to establish what visitors receive.
- Staging is right, but the custom domain is wrong: check which domains were selected for publication, then check the domain status in Site settings > Publishing > Production.
- The page is missing on both: check the page slug, any redirect from the previous URL and whether the page or CMS item has been published. Test the direct URL as well as the navigation link.
- The page loads but looks wrong on mobile: reproduce it at the affected width. Inspect the element and its parent layout, breakpoint styles and any custom script controlling visibility.
For domain problems, follow the values displayed for that particular site. Don't paste DNS records from an old tutorial: Webflow's infrastructure and the records required by different sites can differ. Its domain connection guide explains the available setup routes.
If you need to change a redirect or DNS setting, capture the existing value first and confirm who owns it. Avoid changing several things at once; otherwise you won't know which change resolved the fault.
If the form won't submit
Test the published page and note whether the browser blocks submission, the form displays an error or the button never responds. Check required fields, field types and whether the submit button and inputs belong to the intended form. A required field hidden at a mobile breakpoint is worth investigating.
Next, select the form and inspect its Send to settings. Establish whether it stores submissions in Webflow, sends email notifications, connects to an app or uses a custom action. An embedded third-party form may be handled entirely by its provider.
A custom action bypasses Webflow's processing and can't be combined with Webflow storage or its email notifications. Don't remove that action just to make a test pass; it may be the intended route to another system. Webflow's form setup documentation explains those destinations.
For forms processed by Webflow, inspect the right form and its spam view in Site settings > Forms. Also check the site's current plan and any applicable limits. If the site was exported and hosted elsewhere, Webflow doesn't process its submissions; investigate the external form handler instead. See Webflow's submission troubleshooting notes.
If the configuration looks right, a developer can inspect the browser's network request and console error while reproducing the problem. Record the failing request and response, with personal data and credentials removed. Avoid disabling spam protection on the live site as a blanket fix.
Want to apply this to your own website or app?
Tell me what you are working on and where it is getting stuck. I will help you turn the useful ideas into shipped work.
If the submission exists but the email or CRM record doesn't
Treat each destination as a separate step. A saved submission establishes that Webflow received it; it doesn't establish that every later integration completed.
For a missing notification, check that Email notifications is enabled for that form, the recipient is correct and the receiving mailbox hasn't filtered the message. Save and publish any configuration change before an agreed retest. Webflow's notification settings guide shows where those controls live.
For a CRM or automation problem, use the test timestamp to follow the record through the connected tool. Was the trigger received? Did an action fail authentication? Was a required property missing? Did a filter skip the record, or did an existing contact get updated instead of a new one being created? Check the actual run history before reconnecting accounts or replaying submissions.
Demonstration: the form works, but the sales handoff stops
This is an illustrative diagnosis, not a client incident or a measured result. Suppose a test enquiry appears in Webflow, but the sales team can't find it in their CRM.
- Find the agreed test submission by its timestamp and form name. Confirm Webflow storage is an intended destination.
- Find the matching event in the automation's run history. If there's no event, investigate the trigger connection and selected form.
- If the event exists, inspect the first unsuccessful step. In this example, the CRM rejects an empty required company field.
- Correct the field mapping and decide how genuinely missing company values should be handled. Don't fill them with invented customer details.
- Retest once and verify the resulting CRM record, owner and notification. Check for an existing record before replaying the original event, so the repair doesn't create duplicates.
The form's appearance didn't need changing in that example. The useful evidence was the failed step between receipt and the destination. My lead-routing comparison goes further into routing choices and failure handling.
Choose the right person to help
Use the Webflow Support Portal for account access, billing, platform functionality and hosting issues. Include the smallest set of steps that reproduces the problem, the affected URL and a redacted screenshot or recording. Log in with the appropriate account; billing requests may require a Workspace owner or admin.
Custom code, third-party integrations and design implementation need a different owner. Webflow's customer support policy sets out those boundaries. Send an app-specific failure to the app provider; involve the developer responsible for custom code or routing. Support availability and response terms depend on the service, so don't assume an immediate fix or a particular support channel.
For implementation work, I can help investigate the page, form and integration journey and agree the repair scope. Send me the affected URL and what happens, along with the business impact and any deadline. Don't put passwords, API keys or real customer submissions in the enquiry. If you need an ongoing owner after the repair, my website management service explains that work.
Frequently asked questions
Why does my Webflow form show success but no email arrives?
Check whether the form is configured to send email notifications and whether the submission is stored in Webflow. If it is stored, inspect the notification recipient and mailbox filtering. A success message does not confirm that a later email or CRM handoff completed.
Why does my page work on staging but not on my custom domain?
Check that you published to the intended domain and inspect its status in Site settings > Publishing > Production. Compare the exact page path on both addresses, including redirects. Use the DNS values shown for your own site if a domain change is required.
Can Webflow support fix my custom integration?
Webflow support handles platform issues, but its policy excludes custom code and third-party integration troubleshooting. Use the failing step and error details to decide whether the app provider or the developer responsible for the implementation should investigate.

.jpg)






