How to customize Webflow form notification emails for every form on your site

The redesign means designers now open a form’s Settings panel in the Designer to edit five fields—recipients, sender name, reply‑to, subject, and body—rather than navigating the global Site Settings. Because the “Send to” section lives on the form itself, a single site can direct a contact form to sales@company.com, a support form to support@company.com, and a newsletter signup to no address at all, without Zapier or external services. The change also clarifies that the feature’s reach depends on three variables: the Site plan (free Starter caps notifications at five Workspace members; paid tiers like Basic ($14/mo), CMS ($23/mo), Business ($39/mo) lift that cap), the Workspace tier (Starter, Core, Freelancer use a generic no‑reply‑forms@webflow.com address, while Growth and higher switch to no‑reply@webforms.io and allow custom sender names), and distinct form names (default “Email Form” can cause confusion; naming each form uniquely surfaces the {{formName}} variable in email subjects).

This move aligns Webflow with a broader push among no‑code platforms to give creators granular control over backend processes while keeping the UI low‑code. Competitors such as Squarespace and Wix still route all form notifications through a single site‑wide setting, often forcing users to rely on third‑party automations for per‑form routing. By embedding notification settings directly in the Designer, Webflow reduces friction for agencies managing multi‑form client sites and for internal teams that need separate inboxes for sales, support, and marketing. The tiered restrictions also reinforce Webflow’s monetization strategy: free users receive a functional but limited experience, encouraging upgrades to unlock unlimited recipients and brand‑neutral sender addresses.

Looking ahead, the primary risk is that the new per‑form UI may confuse long‑time users accustomed to the old global location, especially when forms share default names. Additionally, corporate email filters could still block the no‑reply@webforms.io address, so teams must test deliverability after configuration. Watch for Webflow’s next iteration—potentially adding webhook or API‑only notification options—to see if they further reduce reliance on email and expand integration depth for enterprise customers.