Manage form responses

You've built your form, that's great! But where do the form submissions actually go? And how do we manage them in Webflow? That's exactly what we're going to cover in this video, and we'll do it in five steps. We'll publish and submit. We'll go over notifications and routing. We'll see where these submissions live. We'll review our submissions, and then we'll do some troubleshooting if things don't go as expected.

Let's dive right into it. Here we have our form that we completed in the other video (go check that out if you haven't already.) And remember, form submissions only work once you've published your site. In our site, let's go up and do exactly that (we'll publish our site to our staging domain or you can of course also choose to publish to your custom domain.) For us (we're still testing here) so we're just gonna use the staging domain. So if we click in and open up our staged site in a new tab, we now have our site here, so let's just go in and fill out the form (I still have some Emmtokens left, so my AI agent is on top of it). We've filled out the form. Thank you. Now let's press submit. And we can see that the form was successfully submitted. This is the same experience that anyone else will see on their end once the site was published (we're not in preview). It has to be published.

Alright, that's publishing our site and submitting the form. Let's talk about notifications and routing. Once a submission has gone through (someone actually fills out the form and clicks submit on your website) it can trigger an email notification and different forms can notify different people. How do we set that up? With our form block selected, we can go into the element settings. And here in our "Send to", we can see that the form submissions are going to go to Webflow (more on this in a little bit), and then we have email notifications. Let's click in and see what's going on.

But first, here's a side by side. On the left, our email notifications settings in Webflow, and on the right, how that email looks in your inbox. Back to Webflow, let's start at the top here. To. This is who the email notification will go to, and you can choose a member (or multiple members) of your team or type in an email that should be getting that email notification (could be the person who's owning the follow up). Next we have the sender name, and this might be a little confusing at first. This is not the name of the person filling out the form on your site or the name of the form itself. It is the "from" name, so in your inbox it's going to look like this. So if you have multiple forms on your site, using clear names here could be helpful.

We have the reply to email that will receive replies. This controls where replies are sent. Replying directly to a notification can work well in some cases, such as a simple contact form owned by a single person, where a quick response is all that's needed. However, replying to a notification email doesn't update the submission record in Webflow and can limit visibility for teammates unless messages are shared. For this reason, email replies work best for quick, lightweight follow up, not for tracking or collaboration. In practice, many teams use both approaches. Notifications create awareness, while Webflow remains the place where submissions are stored and reviewed as a complete record.

Subject. This is the subject line of the notification email. And the body. That's the main content of the notification email. What the recipient sees when they open it. And if you want to use the add field option to insert dynamic form fields into your options, you can do that too. So instead of typing things in, you can dynamically pull it from the form submission to make each message automatically personalized and more useful. If we go back to our original side by side, and if we change things in Webflow, this is how and where it will show up in the email. And remember, you need to publish your site for these changes to work. That's notifications, who gets them and how you can direct them to the right place.

But where do these submissions live? And how do we manage them? In our site settings, under forms, we can see how submissions are grouped by form. You can manage multiple unique forms on a single site, all with their different settings and configurations if needed. And the name of the form here matches the name you gave it in its form block settings when you built it. You can change this later too. Clicking on the form that we were looking at earlier, we can see all the submissions in there. Each of these submissions is a completed form on your public site, and these submissions are stored separately from your page content. If a new entry comes in, this is where you go to review it.

Here you can see we have two tabs: submissions and spam. In the spam view, Webflow automatically evaluates each submission for spam signals (you can toggle that off or back on in the apps and integrations tab under the Cloudflare spam protection), and that is automatic and happens as soon as the form is submitted. Flagged submissions are stored in the spam view but can be reviewed. And don't ignore the spam tab, real submissions can occasionally get flagged (but you can always manually move submissions out of the spam). And if spam does get past the filter, you can do the opposite and manually move a submission to spam.

Okay, that's where the submissions live and how to manage them, let's look into how to review a submission. In our submissions tab, you can see all your submissions and review them one at a time. We have our different field names (these are the names we used for our fields in Webflow). In addition to that, we have a date and IP address information. You can look through and view all the submissions in this view. It's useful for reviewing individual leads, spotting form behavior and just confirming if required fields are working as expected.

Second, we can export in bulk, so you can export all your submissions as a CSV. This can be extremely helpful when you're exporting data to share with teammates, uploading to another tool, or just keeping a record locally. Also, if you want to route them outside of Webflow, you can use the webhook option to send submission data directly to another app or server automatically. This is especially helpful if you're on a larger team and already using a system to track lead follow ups and you want to keep everything together. That's reviewing our submissions.

Let's do some troubleshooting. If something's not working, we recommend checking four things: is the site published, are you looking at the right form, are required fields configured correctly, and did it get flagged as spam? A lot of the time, many submissions issues are related to the publish state, form identification or spam classification, not the styling itself. So those are a few simple things to double check that can solve the issue.

But that's it. That's how to manage your form. Let's recap. We published and submitted our form. We looked at notifications and how to route them to the right place. We saw where the submissions live in Webflow and how we can manage them. We reviewed our submissions and finally we covered some troubleshooting tips. And that's managing form submissions in Webflow.