Jotform Email Notifications Not Working: Fix It in 10 Minutes

When Jotform email notifications stop arriving, the first instinct is to blame Jotform. Sometimes Jotform is the problem. Most of the time, the issue is a configuration that changed, a filter that caught the email, or a conditional logic branch that swallowed the notification. I spent five years inside Jotform. This was one of the top three support topics. Here are the six reasons it happens and exactly how to fix each one.

Reason 1: The sender email is not verified

Jotform lets you set a custom sender email for notifications. This is the 'From' address on the email your team receives when someone submits a form. By default, it is set to noreply@jotform.com. If you change it to your own address (say, forms@yourcompany.com), Jotform requires you to verify that address before it will send from it.

The verification process sends a confirmation email with a link. If that confirmation email lands in spam, or the person who changed the setting did not click the link, the sender email stays unverified. Jotform silently falls back to noreply@jotform.com or, in some cases, stops sending the notification entirely.

How to fix it: Go to Settings → Email → Sender. Check the verification status next to your sender email. If it says 'Unverified,' click 'Verify,' check the inbox for the verification email (check spam), and click the link. If you do not have access to that inbox, change the sender email to an address you can verify.

Reason 2: The notification email is in spam

This is the most common cause and the easiest to overlook. Jotform sends notifications from its own mail servers. Those servers have good deliverability overall, but corporate email filters are aggressive. If your team uses Google Workspace, Microsoft 365, or any enterprise email system with strict DMARC policies, Jotform notification emails get flagged regularly.

The notification is sent. It just never reaches the inbox. It sits in a spam folder or a quarantine queue that nobody checks.

How to fix it: Check the spam/junk folder of the recipient email. If the notification is there, mark it as 'not spam.' For a permanent fix, add the sender address (noreply@jotform.com or your verified custom sender) to the recipient's safe senders list. In Google Workspace, the admin can create an allowlist routing rule. In Microsoft 365, add the sender to the anti-spam policy's allowed senders list.

Reason 3: Conditional notification routing is misconfigured

Jotform lets you set up conditional email routing. For example: if the form's 'Department' field equals 'Sales,' send the notification to sales@yourcompany.com. If it equals 'Support,' send to support@yourcompany.com. This is powerful, but it introduces a failure mode: if the submitted value does not match any condition, no notification is sent.

This happens when a dropdown option is renamed but the condition is not updated, when a respondent types a free-text value that does not match the condition's expected string, or when the condition itself was set up with a typo in the value field.

How to fix it: Go to Settings → Conditions and review every condition that sends an email. Check that the trigger values match the current field options exactly. Add a fallback: a condition that sends to a general inbox if none of the specific conditions match. Without a fallback, any unmatched submission goes nowhere.

Reason 4: The notification was accidentally deleted

Every form has a default email notification. It is possible to delete it. It is also possible to duplicate a form and not notice that the notification on the duplicate is still pointing to the original form's recipient list, or that it was not carried over at all. During form edits, someone can click into the email settings, hit delete, and close the panel. The notification is gone and there is no undo.

How to fix it: Go to Settings → Email → Emails. If the notification list is empty, it was deleted. Click 'Add Email' and create a new notification. Set the recipient, subject, and sender. The default notification includes all form fields in the email body. If you had a custom template, you will need to rebuild it.

To prevent this: before making changes to a production form's email settings, take a screenshot of the current configuration. It takes 10 seconds and saves you from reconstructing a custom email template from memory.

Reason 5: The sending quota was exceeded

Jotform limits the number of email notifications per form on free and low-tier plans. The limit is tied to the submission limit. If you hit your submission cap, notifications also stop because no new submissions are being accepted. But there is a separate email-sending limit that can trigger even if submissions are under the cap. On the Starter plan, Jotform limits how many emails can be sent per day. On paid plans, this limit is higher but still exists.

If you have a form that sends multiple notification emails per submission (one to the submitter, one to the team, one to an integration), each counts separately. A form that gets 50 submissions and sends 3 notifications per submission generates 150 email sends.

How to fix it: Check your plan's email sending limits in Jotform's pricing page. If you are hitting the daily limit, reduce the number of notifications per submission (combine team notifications into a single recipient group), or upgrade to a plan with a higher sending allowance.

Reason 6: The recipient field is blank due to conditional logic

You can set a notification's recipient to pull from a form field instead of a fixed email address. For example, set the notification to send to the email the respondent enters in the form. This is how auto-responder emails work.

The problem: if the email field is hidden by conditional logic (the field is conditionally shown, and the condition did not fire, so the field is blank), the recipient field is empty. Jotform tries to send to an empty address. The email fails silently.

How to fix it: Check that the recipient field in your notification settings always has a value for every path through the form. If you are using conditional logic to show/hide the email field, make sure the notification's recipient is set to a fixed address, not the conditional field. Or add a default recipient that catches any path where the email field is empty.

The one setting everyone forgets: the reply-to email

This deserves its own section because it is not about delivery failure. It is about a workflow failure that feels like a delivery problem. When a team member receives a Jotform notification and hits 'Reply,' the reply goes to the reply-to address. By default, that address is noreply@jotform.com.

So your team member replies to the notification with a follow-up question for the respondent. The email bounces. Or it goes to a black hole. The respondent never hears back. The team thinks Jotform is broken. It is not. The reply-to address is just wrong.

How to fix it: In Settings → Email, edit your notification. Scroll to the 'Reply-To' field. Change it from the default to the form field that contains the respondent's email address. Now when someone hits Reply on the notification, the response goes to the person who submitted the form. This is a 30-second fix that saves hours of confused follow-ups.

Diagnosis checklist

If a notification is not arriving, work through this list in order. Most issues are found in the first three steps.

1. Check the spam/junk folder of the recipient email.
2. Verify the sender email in Settings → Email → Sender.
3. Review conditional email routing in Settings → Conditions. Check for unmatched values and add a fallback.
4. Confirm the notification still exists in Settings → Email → Emails. It may have been deleted.
5. Check the plan's email sending limits against your volume.
6. If the recipient is a form field, confirm that field has a value on every form path.

Run through this list and you will find the issue. In my experience, 80% of notification problems are reason 1 or 2. The rest are split between conditional routing and the deleted notification. The reply-to issue is not about delivery, but fix it anyway. Your team will thank you.