Which methods allow for granular filtering of native Webflow CMS form notifications?

Answer

Webflow’s native email notifications do not support conditional logic; they can only include or exclude specific form fields via merge tags.

Methods that enable granular filtering

1. Native field‑level merge‑tag filtering – In Form Settings → Email Notification, use merge tags to show or hide fields. This controls what appears in the email but does not prevent the email from being sent.
2. Collection Item Notifications – When the form is set to create or update a CMS Collection item, you can enable a Collection Item Notification. The notification template can use the same merge‑tag syntax to include/exclude fields, giving you field‑level control over the alert that is sent only for CMS‑item submissions.
3. Form Webhook → external automation – Enable a Form Webhook (Form Settings → Webhooks) that POSTs the raw submission JSON to an endpoint such as Zapier, Make, AWS Lambda, or a custom server. In the external service you can apply any logical filter (e.g., only if “Priority” = “High”) before forwarding an email via SendGrid, Mailgun, etc.
4. Custom‑code embed that intercepts submit – Add a <script> block before that calls event.preventDefault(), reads field values, and conditionally fires a fetch to a third‑party email API. This gives full JavaScript‑level filtering while still using Webflow’s UI for the form.

Verification steps

• Create a test form with at least three fields (e.g., Name, Email, Priority). Enable the native email notification and verify you can hide/show fields using merge tags.
• Enable a Form Webhook pointing to a request‑bin service, submit the form, and confirm the full JSON payload is received. Then add a filter step in Zapier/Make to forward only when Priority equals “High”.
• Add a custom‑code embed that prevents default submit, checks the Priority field, and posts to a test endpoint (e.g., https://httpbin.org/post). Inspect network traffic to ensure the call occurs only for the expected condition.
• If the form is configured to create/update a CMS item, enable a Collection Item Notification, place merge‑tag filters in the template, submit an item, and verify the received email respects those filters.

Missing diagnostic detail

To recommend the most efficient path, please confirm whether your form is set to create or update a CMS Collection item (i.e., uses Collection Item Notifications) or is a standard form‑only submission. This determines if the native Collection Item Notification method is available to you.