How to Customize Webflow Form Notification Emails for Each Form on Your Website

Understanding the New Webflow Form Notification System

Webflow made a significant update to form notification settings in October 2025 that changed how developers and site owners manage form submissions. Previously, form notification settings lived in Site Settings, applying broadly across your entire website. Now, these settings have moved directly into each Form Block's Settings panel within the Designer interface.

This architectural change unlocks something that was previously impossible without third-party integrations: each form on your Webflow site can now have completely independent notification settings. Your contact form can send submissions to your sales team, your support form can route directly to your help desk, and your newsletter signup can store data without triggering any email notifications at all.

For agencies and developers managing multiple client projects, this update eliminates the need for Zapier workflows or custom code workarounds that were previously required to achieve form-specific routing. The native functionality now handles what used to require external tools.

Prerequisites for Customizing Webflow Form Notifications

Before diving into the customization process, three factors determine which notification features you can access: your Site plan, your Workspace plan, and whether your forms have unique descriptive names.

Site Plan Requirements

Your Webflow Site plan controls who can receive form notifications. The free Starter Site plan limits you to 5 recipients, and all recipients must be existing Workspace members. Any paid Site plan including Basic, CMS, Business, or Enterprise removes these restrictions entirely. With a paid plan, you can add unlimited recipients and send notifications to any email address regardless of whether that person has Workspace access.

Workspace Plan and Sender Branding

Your Workspace plan determines the sender branding on notification emails. On Starter, Core, and Freelancer Workspaces, all notifications are sent from no-reply-forms@webflow.com with "Webflow Forms" displayed as the sender name. This branding cannot be customized on these tiers.

Growth Workspaces and above send notifications from no-reply@webforms.io without Webflow branding visible to recipients. You can also set a custom sender display name on any plan using the Sender name field in the notification panel, though the underlying sending address remains determined by your Workspace tier.

Form Naming Conventions

Every new form in Webflow defaults to the name "Email Form." When managing multiple forms across your site, this default naming creates confusion quickly. If you have three contact forms on different pages all named "Email Form," identifying which form's settings you're editing becomes unnecessarily difficult.

Establish descriptive naming conventions from the start. Names like "Homepage Hero Contact," "Footer Newsletter Signup," or "Pricing Page Demo Request" make form management straightforward. These names also appear in notification subject lines when using the formName variable, making received emails immediately identifiable for your team.

Step-by-Step Guide to Customizing Form Notification Emails

The customization process involves selecting your Form Block, opening the Email Notifications panel, and configuring five key fields: recipients, sender name, reply-to address, subject line, and email body content. Each form requires independent configuration, and the entire setup typically takes about 10 minutes per form once you understand the interface.

Step 1: Accessing Form Notification Settings

Open your Webflow project in Designer and navigate to the page containing the form you want to customize. The fastest method for locating forms is using the Navigator panel, accessible from the left sidebar or by pressing Z on your keyboard. Expand the page structure until you locate the Form element, which displays with a distinctive icon alongside your assigned form name.

Click directly on the Form element to select it, ensuring you're selecting the Form Block wrapper rather than individual input fields inside the form. The Selection indicator at the top of the canvas should display "Form" or your custom form name. If it shows "Input" or "Text Field," you've selected a child element and need to click the form's outer wrapper again.

With the Form Block selected, examine the Settings panel on the right side of the Designer interface. Scroll past the form name and success/error message settings until you reach the "Send to" section, which controls submission destinations.

Step 2: Configuring Recipient Email Addresses

The "Send to" section displays active destinations for form submissions. By default, new forms include two destinations: Webflow (storing submissions in Site Settings → Forms) and Email Notifications (triggering notification emails to designated recipients).

If Email Notifications doesn't appear in your list, click the add icon next to "Send to" and select "Email Notifications" from the dropdown menu. Clicking on "Email Notifications" expands the configuration panel revealing all customization fields.

On paid Site plans, click inside the "To" field and type any email address directly. Press Return or Enter to add each address as a tag. Common configurations include multiple team members receiving the same notifications or departmental aliases that your email system routes to multiple internal recipients.

On the free Starter plan, the "To" field only allows selection from existing Workspace members via dropdown. You cannot enter arbitrary email addresses. To send notifications outside your Workspace on Starter plans, you must either add recipients as Workspace members or upgrade to a paid Site plan.

To disable email notifications while retaining form submissions in Webflow, simply delete all email addresses from the "To" field and leave it empty.

Step 3: Customizing Sender Name and Reply-To Address

The Sender name field controls what recipients see in the "From" field of notification emails. While the actual sending email address depends on your Workspace plan, the display name can be customized on any tier. Use your company name, department name, or website name for professional consistency.

The Reply-to field determines which email address receives responses when recipients reply to notification emails. This setting is crucial for workflow efficiency. If your sales team receives contact form notifications, set the reply-to as your main sales inbox so that responses route correctly rather than bouncing from a no-reply address.

Step 4: Crafting Subject Lines with Variables

Notification subject lines support Webflow variables that dynamically insert form data. The most commonly used variables include formName (inserting your form's assigned name) and field-specific variables that pull submitted data directly into subject lines.

Effective subject line formats include patterns like "New submission from {{formName}}" or "Contact request: {{fieldName}}" where fieldName corresponds to a specific form field. Dynamic subject lines help recipients prioritize and sort incoming notifications, especially when multiple forms feed into the same inbox.

Step 5: Designing Email Body Content

The email body section allows customization of notification content beyond the default format. You can include all submitted form fields using variables, add custom text providing context or instructions, and format the notification layout to match your team's preferences.

Consider including internal routing information, priority indicators based on form type, or direct links to your CRM or project management tools where submissions should be logged.

Troubleshooting Common Notification Issues

When form notifications fail to arrive, several common causes exist. Corporate email systems frequently filter automated messages from unknown senders, meaning Webflow delivers the notification successfully but recipient spam filters intercept it before anyone sees the email.

Always test notifications with actual recipients after initial configuration rather than assuming delivery will work. Ask recipients to check spam folders and whitelist the Webflow sending addresses if necessary.

Verify your Site plan supports the number of recipients you've configured. Starter plans enforce the 5-recipient limit strictly, and exceeding it can cause silent delivery failures.

Check that form submissions are actually reaching Webflow by reviewing the Forms section in Site Settings. If submissions appear there but notifications don't arrive, the issue lies in notification configuration or recipient email filtering rather than form functionality.

Best Practices for Form Notification Management

Establish consistent naming conventions across all projects before creating forms. Document which email addresses receive notifications for each form, especially on client projects where team members may change over time.

Review notification settings periodically, particularly after organizational changes that affect email addresses or team responsibilities. Forms configured to notify departed employees waste submissions and create gaps in lead response times.

Consider creating a notification testing protocol for new form deployments. Submit test entries to each form after publishing and confirm notification delivery to all configured recipients before considering the form live.

Partner with Experts for Your Webflow Projects

Configuring form notifications correctly ensures your team never misses important submissions and that leads route to the right people immediately. While the technical setup is straightforward once you understand the interface, optimizing forms for conversion and integrating them into broader marketing workflows requires deeper expertise.

At Uxie Design, we build Webflow websites that convert visitors into customers through thoughtful design and technical precision. From form configuration to complete website development, our team handles the details so you can focus on growing your business. Visit https://www.uxie.design to discuss your next project.