If you’ve spent any time in Gravity Forms notification settings, you’ve probably noticed two features that seem to do the same thing: email routing and notification conditional logic. Both use form field values. Both change how a notification behaves after a submission. And both live on the same settings screen.
So what’s the difference, and when do you use one over the other? This tutorial explains how each one works, walks through real-world examples, and shows when you need both together.
The Difference in One Sentence
Email routing controls where a notification goes. Notification conditional logic controls whether a notification goes at all.
Everything else follows from that.
What Is Email Routing?
Email routing lives in a notification’s Send To setting. When you choose Configure Routing, you’re telling Gravity Forms: don’t send this to a fixed address, work out the recipient from what the user submitted.
You add a set of rules, each pairing an email address with a condition. When a submission comes in, Gravity Forms checks the rules and sends the notification to the address whose condition matches.
The classic example is a contact form with a Department field. Choose “Sales” and the notification goes to the sales team. Choose “Support” and it goes to the support inbox. Same notification, same email body, different recipient.
What Email Routing Does Not Do
Routing can’t stop a notification from sending. It only supplies the address for Send To. If none of your rules match, the notification is still processed, just with an empty Send To, so it fails and nobody gets it.
That’s the most common gotcha. Your rules have to cover every possible choice in the field you’re routing on. A Drop Down with five options needs a rule for each of the five.
There’s a maintenance catch too. Routing rules are saved against the choices that existed when you set them up. If you later edit a choice used in a rule, even by one character, that rule stops matching. Open the notification, pick the updated choice in the rule and save again.
What Is Notification Conditional Logic?
Notification conditional logic works on the whole notification, not inside Send To. It answers a different question: should this notification fire at all?
You turn it on near the bottom of the notification’s settings and add one or more conditions. If the conditions are met, the notification sends. If they aren’t, it’s skipped completely.
This is the feature for submissions that shouldn’t trigger a notification at all, or for different kinds of submissions that need completely different emails: a different subject line, body and From Name, not just a different recipient.
The “Do You Own a Pet?” Example
The Gravity Forms docs use a good example. A form asks “Do you own a pet?” with Yes and No options, and you want to send pet owners a different email than everyone else, with its own subject, copy and links.
Routing isn’t the answer here. Create two notifications instead, each with its own content and its own conditional logic:
- Pet owners: send if “Do you own a pet?” is “Yes”.
- No pet: send if “Do you own a pet?” is “No”.
Each notification stands on its own, so you can change one without touching the other.
When to Use Email Routing
- The email is the same, but the recipient depends on a field. A multi-location business where every submission looks the same but needs to reach the right office manager. A law firm sending each practice area’s inquiries to a different attorney. A staffing agency routing applications to each department’s hiring manager.
- You have one notification and several possible recipients. Routing handles it all in a single notification, instead of copying the same email into five notifications just to change the To address.
- The decision comes from a choice field. Drop Downs and Radio Buttons are the natural fit, because they have a fixed set of values you can match. Routing can also use text fields, but free-typed values are much harder to cover completely.
When to Use Notification Conditional Logic
- Some submissions shouldn’t send a notification at all. If an opt-in checkbox is left unchecked, you don’t want the follow-up email to go out. Conditional logic sends the notification only when the box is checked.
- Different submissions need different email content. If “General Inquiry” and “Request a Quote” should produce emails with different subjects, bodies and structure, use separate notifications with their own conditional logic, not routing.
- The notification depends on whether a field was filled in. The docs use an optional Email field: only send the user’s confirmation if they gave an address. There’s no “is not empty” operator. Instead, choose the Email field, the is not operator, and leave the value blank. (Use is with a blank value for the opposite.)
- You want to hold back a notification under specific conditions. Hidden fields, calculated values and answers to qualifying questions can all decide whether a notification goes out.
When to Use Both Together
This is where it gets useful, and it’s the case most tutorials skip.
Take a contact form for a company with three regional offices (East, West and Central) and two inquiry types (General and Urgent):
- Urgent notification: a high-priority subject line and message. Conditional logic sends it only when Inquiry Type is “Urgent”.
- General notification: the standard email. Conditional logic sends it only when Inquiry Type is “General”.
- Routing inside both: each notification routes to the right regional manager based on the Location field.
The result is two notifications with different content. Conditional logic decides whether each one fires, and routing inside each one decides where it goes. You’ve separated “should it send?” from “where does it go?”
Another example: a lead form that routes to sales reps by territory, but only sends if the lead’s budget is above a set amount. Conditional logic checks the Budget field, routing handles the territory, and each does one job.
Quick Reference
| Email routing | Notification conditional logic | |
|---|---|---|
| Controls | Who receives the notification | Whether the notification fires |
| Where it lives | Send To → Configure Routing | Near the bottom of the notification settings |
| Based on | Field values → email addresses | Field values → send or skip |
| Can stop a notification? | No | Yes |
| Best for | Same content, different recipients | Different content, or skipping sends |
| Common mistake | Not covering every possible choice | Not creating a separate notification for each case |
The Mistake That Catches Everyone
People often use routing where they need separate notifications, or build separate notifications where routing would be simpler.
- If you’re building five identical notifications that only differ in the To address, stop. That’s a routing job.
- If you’re trying to write one email that has to say completely different things depending on the submission, stop. That’s a job for separate notifications with conditional logic.
And remember that routing without full coverage fails quietly. The submission goes through fine, but the notification has no address to go to. Check your routing rules against every choice in the field, and check them again whenever you edit that field’s choices.
Wrapping Up
Email routing and notification conditional logic solve different problems, and they’re most powerful when you use them on purpose, sometimes together. Ask yourself which question you’re answering: “who should get this?” or “should this send at all?” The answer points you to the right tool.
For the full settings, see the Gravity Forms docs on email routing and conditional logic for notifications.
If you still need help, use the chat or leave a comment below and we’ll get back to you.
Comments