How Do I Get Notified When Someone Submits a Form on WordPress?
WordPress does not notify you when a form is submitted. Notifications are handled by your form plugin, or by a workflow automation plugin layered on top of it. Krom Automation is one concrete way to handle this: the free plugin connects form submissions from Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms and Ninja Forms to email, Slack, Telegram, SMS or any webhook, with no Pro upgrade required for basic email and HTTP notifications.
Every form plugin has a built-in email notification panel, and for simple admin alerts that is often enough. The limit appears when you need to route submissions to different people based on field values, send a Slack message instead of an email, or trigger a CRM action the moment a form is filled in. That is where a dedicated automation layer earns its place.
This guide covers both paths: the native notification settings inside the major form plugins, and the workflow automation approach with Krom Automation for anything more complex.
Browse the full Krom Automation feature list to see what the free plugin includes before we get into the setup.
Does WordPress Notify You by Default When a Form Is Submitted?
No. Core WordPress has no concept of a form submission notification. The WordPress admin email receives comments, user registrations and plugin update alerts, but form entries are handled entirely by the form plugin you install.
Every major form plugin ships with a basic email notification panel. You set a recipient address, a subject line and a message body, and the plugin fires an email via wp_mail() after each submission. That covers the majority of single-admin, single-recipient use cases without any extra tooling.
What the native panels do not cover:
- Sending to a Slack channel, Telegram chat or SMS number instead of email
- Routing to a different recipient based on a field value, for example, routing “sales enquiry” forms to one address and “support” forms to another
- Triggering a CRM action, a spreadsheet row or a webhook at the same time as the notification
- Chaining a confirmation email to the submitter plus an internal alert plus a follow-up after 24 hours, all from one trigger
For those scenarios you need either the form plugin’s Pro tier (which usually unlocks conditional notifications) or an automation plugin that listens for the form submission trigger and handles the rest.
How to Set Up Email Notifications in the Major Form Plugins
The steps differ slightly by plugin, but the core shape is the same: find the notification or confirmation panel inside the form editor, set the “Send To” address and customise the subject and body with dynamic field placeholders.
Gravity Forms
Open the form, go to Settings > Notifications and edit the default “Admin Notification” entry. The “Send To” field accepts a static email or a merge tag like {admin_email} or {field:3} to pull the address from a field. The message body supports all Gravity Forms merge tags.
For conditional routing, Gravity Forms Pro lets you add conditional logic rules directly to each notification. Full setup detail is in the Krom Automation Gravity Forms integration guide.
WPForms
Edit the form and open the Settings > Notifications panel. The default notification sends to your WordPress admin email.
Add additional notifications with the “Add New Notification” button, each with its own recipient and conditional logic rule if you are on WPForms Pro. See the WPForms integration documentation for the automation trigger details.
Fluent Forms
Go to Configure > Email Notifications inside the form editor. Fluent Forms supports multiple notification entries on the free version, which is more generous than most competitors.
Each entry has its own conditional logic panel. The Fluent Forms integration page covers the specific trigger Krom Automation exposes.
Contact Form 7
Edit the form, open the Mail tab and set the “To” field. Contact Form 7 sends one email per submission with no native conditional routing and no built-in multi-recipient support.
Anything beyond a single static address requires a third-party plugin or automation layer. The Contact Form 7 integration documentation explains how to wire CF7 submissions into Krom Automation workflows.
Elementor Forms
In the Elementor editor, select the form widget and open Actions After Submit. Add the “Email” action and configure the recipient.
Elementor Forms Pro supports conditional actions. The Elementor Forms integration guide covers trigger setup for automation workflows.
Ninja Forms
Edit the form and go to the Emails & Actions tab. Add an “Email” action for each notification you need.
Conditional routing requires the Conditional Logic add-on. Full details are in the Ninja Forms integration documentation.
Built-in form plugin notifications are fine for a single admin email. The moment a submission needs to reach three people, a Slack channel and a CRM, you are duct-taping workarounds together instead of building a real workflow.
Quick Summary: Which Approach Fits Which Situation
| Situation | Best approach | Free or paid? |
|---|---|---|
| One admin email per submission | Native form plugin notification panel | Free on all major plugins |
| Multiple static recipients | Native panel with extra entries (Fluent Forms, WPForms Pro) | Free on Fluent Forms; paid on most others |
| Route by field value (sales vs support) | Krom Automation conditional branching | Free plugin |
| Slack, Telegram or SMS alert | Krom Automation with messaging integration | Pro (messaging integrations) |
| Email + CRM tag + follow-up after 24 hours | Krom Automation multi-step workflow | Free for email; Pro for CRM integrations |
| Confirmation email to the submitter | Native form plugin confirmation panel or Krom Automation Send Email action | Free on both paths |
| Webhook to an external service | Krom Automation HTTP Request action | Free plugin |
How to Get Notifications via Krom Automation (Free Plugin)
Krom Automation works by connecting a trigger to one or more actions on a visual drag-and-drop canvas. For form submission notifications, the trigger is the form submission event and the actions are whatever you want to happen next: send an email, post to a channel, call a webhook, update a CRM record.
The free plugin includes 16 triggers and 21 actions. Form plugin triggers (Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms, Ninja Forms) are Pro triggers, meaning you need the Pro plugin installed alongside the free base to use them as workflow triggers.
The free Send Email action and the free HTTP Request action are available to anyone. If you only need email alerts and your form plugin already fires them natively, the free plugin adds value through conditional branching and multi-step workflows rather than the notification itself.
Building a Basic Form Notification Workflow
The setup follows the same shape regardless of which form plugin you use:
- Install Krom Automation from the WordPress.org plugin directory and activate it.
- Navigate to Krom Automation > Workflows and click New Workflow.
- On the canvas, add your form submission trigger, for example “Gravity Forms: Form Submitted” or “Fluent Forms: Form Submitted”.
- Add a Send Email action and use merge tags to pull in field values: the submitter’s name, email address and message text appear in the notification body dynamically.
- Save and activate the workflow. Use the workflow simulator to run a dry test with zero side effects before going live.
Merge tags are what make the notification useful rather than generic. Instead of receiving “A form was submitted”, you receive the actual name, email and message the person typed. The merge tags documentation lists every available variable per trigger.
How Do I Route Notifications to Different People Based on Form Fields?
This is where Krom Automation’s conditional branching replaces a stack of duplicated native notification rules. You build one workflow with a Yes/No branch after the trigger. The condition checks a field value, for example “if Department field equals Sales”, and the Yes path sends to the sales inbox while the No path sends to the general support address.
A more complex routing example might look like this:
- Trigger: Gravity Forms submission on your contact form
- Branch condition: “Enquiry Type” field equals “Partnership”
- Yes path: email the partnerships team + add a tag in FluentCRM
- No path: email the general inbox + create a support ticket via HTTP Request
This replaces what would otherwise require 4 separate native notification entries across two different plugin settings panels, each needing its own conditional logic rule. One workflow canvas is easier to audit and easier to change.
Conditional routing in a form plugin’s notification panel is a workaround. A visual workflow with branching logic is an actual system you can read, test and hand to a colleague without explanation.
Can I Send Form Notifications to Slack, Telegram or SMS?
Yes, with Krom Automation Pro. The messaging integrations cover Slack, Discord, Twilio (SMS) and Telegram as first-class actions. A Slack notification workflow looks exactly like an email notification workflow: form submission trigger, then a “Send Slack Message” action with merge tags pulling in the submission data.
The practical difference between email and Slack for form notifications is speed of acknowledgement. An email sits in an inbox.
A Slack DM in your team’s #leads channel gets seen within minutes, regardless of whether anyone has the WordPress admin open. For time-sensitive enquiries, that gap matters.
For teams without a fixed messaging platform, the free HTTP Request action covers any service that exposes a webhook endpoint. You can POST submission data to a Zapier webhook, a Make scenario, a custom endpoint or a CRM API without leaving Krom Automation or needing a Pro upgrade for that specific step.
Why Am I Not Receiving Form Notification Emails?
This is the most common support question for any WordPress form plugin. The cause is almost always one of four things:
- wp_mail() delivery failure: WordPress sends email via PHP’s mail function by default, which many shared hosts block or throttle. Install an SMTP plugin (WP Mail SMTP, FluentSMTP or Post SMTP) and connect it to a transactional email service like Mailgun, SendGrid or Amazon SES. This single change resolves the majority of missing notification reports.
- Spam or junk folder: Emails sent from a shared server IP with no SPF or DKIM record land in spam. Configuring SMTP through a proper transactional provider sets those records automatically.
- Wrong recipient address: Check the form’s notification panel. Many forms default to the WordPress admin email, which may not be the address you check regularly.
- Conditional logic blocking the notification: If a notification has conditional logic rules, a submission that does not meet the conditions silently skips the notification. Review the rules and test with a submission that deliberately matches.
If your form plugin is delivering correctly but Krom Automation workflows are not firing, check the execution log under Krom Automation > Logs. Each execution shows a per-step audit trail so you can see exactly which action failed and why. Failed executions also trigger an email notification to the site admin with automatic retry on configurable backoff.
What About WP-Cron and Delayed Notifications?
Krom Automation runs background executions via Action Scheduler, which means workflows do not run during page loads and do not slow your site down. Action Scheduler depends on WP-Cron to fire reliably.
On a busy site this is a non-issue. On a low-traffic site where no page loads happen for several hours at a stretch, WP-Cron can fire late, and a “notify on submission” workflow may arrive 30 to 90 minutes after the form was submitted rather than immediately.
The fix is a real server cron job that calls the WordPress cron endpoint every minute, bypassing WP-Cron entirely. Most managed WordPress hosts (Kinsta, WP Engine, Cloudways) offer this as a setting. On a VPS you add one crontab line.
This is worth doing on any site where timing matters, not just for form notifications. The delays and scheduling documentation covers this in more detail.
Cost Comparison: Native Notifications vs Automation Plugin
| Requirement | Native form plugin (free) | Native form plugin (paid) | Krom Automation |
|---|---|---|---|
| Single admin email | Included | Included | Free plugin |
| Conditional routing | Not available | Varies by plugin, typically $99 to $299/year | Free plugin |
| Slack or Telegram alert | Not available | Rarely included | Krom Pro from $69/year |
| CRM action on submission | Not available | Add-on required on most | Krom Pro from $69/year |
| Multi-step workflow (notify + tag + follow-up) | Not available | Not available | Krom Pro from $69/year |
| Unlimited sites | N/A | Typically a separate agency licence | Krom Pro Enterprise, $449/year or $1,199 lifetime |
Krom Automation Pro starts at $69 a year for a single site (launch pricing as of 2026). Lifetime plans start at $199, which is the more cost-effective path for any site running long-term. Every plan includes all 25 Pro integrations and all 101 Pro workflow templates, with the only difference between plans being the number of sites covered.
Paying $99 a year for a form plugin’s Pro tier just to get conditional notification routing is a poor trade when a full automation layer costs $69 and does the routing plus CRM, Slack and follow-up emails on the same canvas.
What Else Can a Form Submission Trigger?
Notification is the first use case most people think of, but a form submission trigger can start a much longer chain. With Krom Automation, a single “form submitted” event can:
- Send an immediate confirmation email to the submitter using their email address from the form
- Add them as a contact in FluentCRM, ActiveCampaign or Mailchimp with tags pulled from their form responses
- Create a WordPress post or update a custom post type record with the submission data
- Send a Slack alert to the sales channel with the lead’s name, company and message
- Wait 24 hours via a delay node, then send a follow-up email if no reply has been sent
- Log the submission to a Google Sheet row for reporting
All of that runs from one workflow, on one canvas, triggered by a single form submission. There are no separate Zaps, no separate Make scenarios and no third-party SaaS accounts required.
The data stays in your WordPress database. For agencies managing client sites, that is a meaningful compliance and data-ownership argument.
If you are looking at automating other site events beyond forms, the blog post on automating WordPress without Zapier covers the broader picture of what a self-hosted automation layer can replace.
Also from wpRigel
Pollify is wpRigel’s poll, survey and quiz plugin. It builds polls as native Gutenberg blocks directly inside the WordPress editor, so there are no shortcodes to paste and no separate admin interface to navigate. If you collect feedback through forms, Pollify handles the structured opinion-gathering side of the same problem.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search, navigate and run admin actions without clicking through menus. It is particularly useful for agencies and developers managing high-volume sites, and it is the only command palette plugin with real WooCommerce order, product and customer commands built in.
Our Verdict
If you need a single email to one address when a form is submitted, your form plugin already does that for free. Do not install anything extra. Configure the native notification panel, set up SMTP, and you are done in under 10 minutes.
If you need conditional routing, Slack alerts, CRM actions or any kind of multi-step response, the form plugin’s native panel runs out quickly, and the Pro upgrade cost for just that feature is hard to justify. Krom Automation’s free plugin handles conditional branching and HTTP requests without any payment. The Pro upgrade at $69 a year unlocks the messaging and CRM integrations that replace what would otherwise require two or three separate SaaS tools.
For agencies running multiple client sites, the lifetime plans deserve a look. A one-time payment covering unlimited sites is a straightforward calculation against the recurring cost of per-site Pro licences on individual form plugins. Download the free plugin to test the workflow builder before committing to anything.
See all Krom Automation plans and pricing to compare annual and lifetime options across all three tiers.
Frequently Asked Questions
Does Krom Automation work with Contact Form 7 on the free plan?
The Contact Form 7 form submission trigger is a Pro feature, so you need Krom Automation Pro installed alongside the free base plugin. Once active, you can find full setup steps in the Contact Form 7 integration documentation. The Send Email action used in the resulting workflow is free.
Can I send a confirmation email to the person who submitted the form?
Yes. Every major form plugin has a separate “confirmation email” or “user notification” panel in addition to the admin notification.
In Krom Automation, you add a second Send Email action to the same workflow using the submitter’s email address pulled in via a merge tag. Both the admin alert and the submitter confirmation fire from the single form submission trigger.
Why are my notification emails landing in spam?
The most likely cause is that WordPress is sending via PHP mail through a shared server IP with no SPF or DKIM authentication. Install an SMTP plugin and connect it to a transactional email service. Mailgun, SendGrid and Amazon SES all set the required DNS records and are free or very low cost at typical form submission volumes.
How do I notify multiple people with different emails based on a form field?
Use Krom Automation’s conditional branching. Add a Yes/No condition node after the form trigger, check the relevant field value, and connect separate Send Email actions to each branch.
The conditions and branching documentation walks through the exact setup. This approach is easier to read and maintain than multiple conditional notification entries inside the form plugin itself.
Can form submission notifications trigger actions in Mailchimp or FluentCRM?
Yes, with Krom Automation Pro. The Mailchimp and FluentCRM integrations are Pro-level actions.
Once your form trigger fires, you add a “Subscribe to Mailchimp List” or “Add FluentCRM Contact” action to the same workflow, map the form fields to the contact fields, and both the notification and the CRM action run together. See the Mailchimp integration guide and the FluentCRM integration guide for setup details.
Does Krom Automation slow my site down when a form is submitted?
No. All workflow execution runs in the background via Action Scheduler, completely separate from the page load that delivers the form confirmation to the user.
The submission response is instant. The workflow actions fire asynchronously after the page has already returned to the browser.