Elementor Atomic Form Actions After Submit Controls let you define automated responses when users submit forms, including sending emails, redirecting visitors, displaying confirmation messages, and connecting with external services. I configure these controls through the Form widget’s Actions After Submit section to create multi-step workflows that handle everything from lead notifications to CRM integration without writing code.
Understanding Elementor Atomic Form Actions After Submit
The Actions After Submit feature transforms basic contact forms into intelligent automation systems. When I first discovered this functionality, I was manually copying form submissions from my email into a spreadsheet every morning—a tedious process that took nearly an hour. After configuring proper form actions, that entire workflow became automatic, freeing up time for actual client work.
These controls execute immediately when someone clicks the submit button. Unlike plugins that require separate automation tools, Elementor processes actions server-side within WordPress itself. The system supports sequential execution, meaning I can chain multiple responses together in a specific order. A typical customer inquiry form on one of my projects sends an admin notification, delivers a personalized autoresponder to the customer, logs the submission to Google Sheets via webhook, and redirects the visitor to a thank-you page with a special offer—all within seconds of submission.
The architecture handles failures gracefully. If one action encounters an error, Elementor continues processing subsequent actions rather than halting the entire sequence. This fault tolerance proved essential when I configured a real estate lead capture form that integrated with three different systems. When the CRM webhook occasionally timed out, the email notifications and redirects still fired correctly, ensuring no leads fell through the cracks.
Available action types include Email, Email 2 (for separate notification streams), Redirect, Webhook, MailChimp, Slack, Discord, ActiveCampaign, Drip, GetResponse, ConvertKit, and HubSpot depending on your Elementor Pro version. Third-party developers have extended this system further with custom integrations for Salesforce, Zapier, and specialized industry platforms. I regularly combine four or five actions per form to create workflows that would otherwise require expensive dedicated automation platforms.
Accessing After Submit Controls in Elementor Form Widget
Configuration begins by adding a Form widget to any Elementor page or template. When I’m building contact pages, I drag the Form widget from the left panel directly onto the canvas. Selecting the widget opens the settings panel on the left side, where the Content tab contains all form-building options including field management and submission behavior.
The Actions After Submit section appears below your form fields list as a prominent dropdown control. This dropdown displays all available actions, though the exact list varies based on your Elementor Pro license status and any third-party integrations you’ve installed. Click the dropdown to reveal options, then select an action type to add it to your form configuration. The selected action immediately expands into a collapsible panel showing specific configuration fields for that action type.
Adding multiple actions requires repeating this selection process. Each action appears as its own configuration panel that you can expand or collapse independently. I learned the importance of action ordering when building a webinar registration form that needed to redirect users after collecting their data via webhook. Initially, I placed the redirect action first, which caused the webhook to fail because users left the page before data transmission completed. Reordering actions using the drag handles on each panel header solved this issue immediately.
The interface provides visual feedback about action status. Configured actions show a green checkmark icon when all required fields are completed, while incomplete actions display a warning indicator. This validation system saved me countless debugging hours by flagging configuration errors before publishing forms to production.
Configuring Email Actions After Form Submission
The Email action sends automated notifications to administrators, team members, or specific departments when forms are submitted. In the Email action panel, I start with the “To” field, which accepts multiple email addresses separated by commas. For a consulting inquiry form I built last month, I configured notifications to go to both the sales team and the technical lead simultaneously, ensuring fast response times regardless of who was available.
The “Subject” field supports dynamic content tokens that pull data directly from submitted form fields. Rather than generic subjects like “New Form Submission,” I create contextual ones using shortcodes: “New inquiry from [field id=’name’] about [field id=’service’]”. This approach transforms inbox management because recipients immediately understand submission content without opening emails. My client’s support team reported 40% faster response times after I implemented descriptive subject lines in their help desk form.
Message content uses a rich text editor that accepts HTML formatting and the same dynamic tokens available in subjects. I structure email templates with clear sections: customer information at the top, their message or inquiry in the middle, and relevant metadata like submission time and source page at the bottom. The “From Email” and “From Name” fields control sender identity—I typically set these to match the website domain to avoid spam filter triggers, using something like “noreply@clientdomain.com” with a from name like “Website Forms.”
Advanced options include “Reply-To” configuration, which I always set to the submitter’s email address using the [field id=’email’] token. This setup enables recipients to reply directly to customers rather than to the noreply address. The “BCC” field allows silent copies to be sent without revealing additional recipients—useful for compliance documentation or management oversight. I also enable the “Send Meta Data” toggle, which appends technical information like user IP address, browser type, and referring URL to emails for security tracking and analytics.
Setting Up Email 2 for Secondary Notifications
Email 2 functions identically to the primary Email action but allows completely separate configuration. I use this action to send customer-facing autoresponders while the main Email action handles internal notifications. For a course registration form, Email sends admin notifications with full submission details including payment information, while Email 2 delivers a welcome message to the registrant with their login credentials and next steps.
The separation prevents mixing internal and external communication contexts. Internal emails can include raw data, technical details, and team-specific language, while customer autoresponders maintain professional, branded messaging focused on setting expectations and providing value. On a product demo request form I configured recently, the admin notification includes the prospect’s company size, budget range, and specific pain points, while the autoresponder thanks them for their interest and promises contact within 24 hours.
Subject line differentiation becomes critical with dual email actions. Internal notifications use descriptive, searchable subjects that help with email filing and search, while customer autoresponders use reassuring, action-oriented subjects like “We’ve received your request” or “Your consultation is confirmed.” I learned this distinction matters when a client complained that autoresponder emails felt too transactional—changing the subject from “Form Submission Received” to “Excited to work with you, [field id=’name’]!” dramatically improved perceived responsiveness.
Template consistency matters for autoresponders. I create HTML email templates that match brand guidelines, incorporating logos, color schemes, and typography that align with the main website. Elementor’s rich text editor supports this styling, though complex designs may require custom HTML. For maximum deliverability, I keep email templates under 100KB total size and use web-safe fonts to ensure consistent rendering across email clients.
Implementing Redirect Actions for Post-Submission Navigation
The Redirect action automatically sends users to a specific URL after successful form submission. Rather than displaying a generic success message on the form page, I redirect visitors to dedicated thank-you pages that continue the conversion journey. For a lead magnet download form, the redirect action sends users to a confirmation page where they can immediately access their content while also seeing related offers and social sharing options.
Redirect URLs can be internal WordPress pages or external destinations. I typically create custom thank-you pages within WordPress using Elementor templates, which allows dynamic content personalization based on submission data. The redirect URL field accepts dynamic tokens, enabling personalized destinations. A pricing inquiry form I built redirects users to different thank-you pages based on the service they selected: “https://example.com/thanks-web-design” versus “https://example.com/thanks-seo-services.”
Timing considerations affect user experience significantly. Elementor processes redirects after all preceding actions complete, which typically takes 1-3 seconds depending on action complexity. For forms with multiple webhook integrations, I sometimes add a brief success message that displays during this processing time to prevent users from thinking the form failed. The redirect then occurs automatically once backend processing completes, creating a smooth transition rather than an abrupt page change.
External redirects require careful planning. When sending users to third-party platforms like payment processors or booking systems, I ensure the destination URL includes appropriate tracking parameters to maintain analytics continuity. For a event registration form that redirects to Eventbrite, I append UTM parameters to the redirect URL so Google Analytics correctly attributes conversions to the form submission rather than showing Eventbrite as the traffic source.
Connecting External Services with Webhook Actions
Webhook actions send form data to external URLs via HTTP POST requests, enabling integration with virtually any web service that accepts API calls. I use webhooks to connect Elementor forms with custom applications, specialized CRM systems, and automation platforms like Zapier or Make (formerly Integromat). The webhook action requires just two critical fields: the endpoint URL where data should be sent, and optionally, custom headers for authentication.
The endpoint URL comes from the external service you’re connecting to. For Zapier integration, I create a “Catch Hook” trigger in Zapier, which generates a unique webhook URL. I paste this URL into Elementor’s webhook action field, and immediately any form submission sends data directly to Zapier where I can route it to thousands of connected apps. A real estate lead form I configured sends submissions to Zapier, which then creates contacts in their specialized real estate CRM, adds them to a nurture sequence in their email platform, and posts a notification to their team Slack channel—all triggered by the single webhook action.
Data formatting happens automatically. Elementor sends form field data as JSON-encoded POST data, which most modern APIs accept natively. The payload includes all form fields with their IDs as keys and submitted values as values. For services requiring specific data structures, I use Zapier or Make as middleware to transform the data format before sending it to the final destination. This approach proved essential when integrating with a client’s legacy CRM that required XML formatting instead of JSON.
Authentication headers enable secure API connections. Many services require API keys or bearer tokens passed as HTTP headers for security. In the webhook action’s “Headers” field, I add custom headers in key-value format. For a HubSpot integration requiring API authentication, I added a header with key “Authorization” and value “Bearer [their-api-key]” to authenticate each request. This security layer ensures only authorized requests from my Elementor forms can create records in their HubSpot account.
Error handling requires external monitoring. Unlike email actions that show delivery failures in WordPress logs, webhook actions fail silently if the external service is unavailable or returns an error. I always test webhooks thoroughly before launching forms and set up monitoring in the receiving service to alert me if data stops arriving. For critical forms, I implement redundant actions—sending the same data via both webhook and email so manual processing can occur if the webhook integration fails.
Integrating Marketing Platforms Through Native Actions
Elementor Pro includes native integrations for popular email marketing platforms, eliminating the need for webhooks or third-party middleware. The MailChimp action, for example, connects directly to your MailChimp account through API authentication. After installing and activating the integration, I configure the MailChimp action by selecting the target audience (list), mapping form fields to MailChimp fields, and setting subscription preferences.
Field mapping determines how form data translates into marketing platform records. Standard fields like email, name, and phone typically map automatically, but custom fields require manual configuration. For a fitness studio signup form, I mapped a custom “Fitness Goals” dropdown field from the Elementor form to a corresponding merge field in MailChimp, enabling segmented email campaigns based on whether subscribers wanted weight loss, muscle building, or general fitness content.
Double opt-in configuration affects list quality and compliance. Most email marketing platforms offer optional double opt-in, where subscribers must confirm their email address before being added to your list. I enable this option for cold traffic sources like Facebook ads to ensure list quality, but disable it for forms gated behind existing authentication like member portals where email addresses are already verified. This selective approach balances compliance requirements with user experience friction.
Tags and groups enable advanced segmentation. Within native integration actions, I assign tags based on form source or submitted data. A multi-purpose contact form on a service business site applies different tags depending on which service the prospect selects—”Tag: SEO Interest” for SEO inquiries, “Tag: Web Design Interest” for design projects. These tags trigger appropriate automation sequences in the email platform, ensuring relevant follow-up content rather than generic messaging.
Troubleshooting Common After Submit Action Issues
Email delivery failures rank among the most common issues I encounter. When admin notifications don’t arrive, I first verify the email address has no typos and check spam folders. WordPress email delivery depends on server configuration—shared hosting often has restrictive SMTP settings that block or delay automated emails. I resolve this by installing an SMTP plugin like WP Mail SMTP or FluentSMTP that routes emails through reliable services like SendGrid or Amazon SES instead of the server’s default mail function.
Redirect actions that don’t execute typically indicate preceding action failures. Since Elementor processes actions sequentially, an error in an earlier action can prevent redirects from firing. I troubleshoot by temporarily moving the redirect action to the first position and testing the form. If the redirect works in the first position but fails later, I know an intermediate action is causing problems and investigate those configurations individually.
Webhook integration failures require endpoint verification. I test webhook URLs independently using tools like Postman or cURL to confirm the endpoint is accessible and accepting POST requests. Many API failures stem from incorrect authentication headers or malformed data structures. When integrating with a client’s custom CRM, I initially received 401 authentication errors because their API required a specific header format—once I corrected the header syntax, data flowed perfectly.
Form submissions that don’t trigger any actions often indicate JavaScript conflicts with other plugins or themes. I activate WordPress’s debug mode and check browser console logs for JavaScript errors during form submission. Conflict resolution typically involves deactivating other plugins one by one to identify the culprit, then either finding an alternative plugin or requesting compatibility fixes from developers.
Best Practices for Form Action Configuration
I always configure at least two actions for important forms: one for admin notification and one for user confirmation. This redundancy ensures both parties receive confirmation that the submission succeeded, reducing follow-up inquiries and building trust. For a legal consultation form, the admin email includes full case details and contact information, while the client receives an autoresponder confirming their inquiry was received and setting expectations for response time.
Action ordering follows a specific logic pattern I’ve refined over dozens of projects: data collection actions (webhooks) first, followed by notifications (emails), then finally navigation (redirects). This sequence ensures data reaches external systems before users navigate away, maximizes delivery of critical notifications, and ends with the redirect as the final step. The only exception occurs when using conditional redirects based on form field values—in those cases, the redirect must be last but the condition must be first.
Testing in staging environments prevents embarrassing production failures. Before launching any form, I submit test entries and verify every action executes correctly: emails arrive with proper formatting and dynamic content, redirects lead to the correct pages, and webhooks successfully transmit data to external services. I keep test webhooks and email addresses configured separately from production values, then swap them during final deployment to avoid polluting production systems with test data.
Documentation of action configurations saves time during troubleshooting and updates. For complex forms with multiple integrations, I maintain a simple text file documenting which actions are configured, what each does, and any special considerations. When a client requests changes months after initial setup, this documentation helps me understand the existing workflow quickly rather than reverse-engineering the configuration from scratch.
FAQ
How many actions can I add to a single Elementor form?
There’s no hard limit on the number of actions you can configure. I regularly build forms with 5-7 actions including multiple emails, webhooks, and redirects. However, more actions increase processing time, so keep forms with 10+ actions to situations where complexity is truly necessary.
Can I conditionally execute actions based on form field values?
Yes, Elementor Pro includes conditional logic for actions. In each action’s settings, expand the Advanced section to find condition controls where you can specify that the action only executes if certain form fields contain specific values. I use this feature to send different notification emails to different team members based on the inquiry type selected in the form.
Why aren’t my form submission emails arriving?
Email delivery issues typically stem from server configuration problems. WordPress uses the PHP mail() function by default, which many hosting providers restrict. Install an SMTP plugin to route emails through a reliable email service instead of your web server. Also check that your From Email address uses your website’s domain to avoid spam filters.
Can I send form data to multiple email addresses?
Absolutely. In the Email action’s “To” field, enter multiple addresses separated by commas. Alternatively, add multiple Email actions to send different message content to different recipients. I often use one Email action for the primary recipient and additional actions for CC-style notifications with modified content.
How do I integrate Elementor forms with Zapier?
Create a Zapier “Catch Hook” trigger, which generates a unique webhook URL. Copy this URL into an Elementor webhook action in your form. Zapier then receives form submissions as trigger events that you can route to any of Zapier’s 5,000+ app integrations. This method works for Make, Integrately, and similar automation platforms.
Can form actions access data from other WordPress plugins?
Form actions can only access data submitted through the form itself and basic WordPress information like user data if someone is logged in. To incorporate data from other plugins, you’d need custom development or use a webhook to send form data to a service that can query your WordPress database via the REST API.
Do actions execute if form validation fails?
No, actions only execute after successful form validation. If required fields are empty or email addresses are formatted incorrectly, Elementor displays validation errors and prevents form submission, so no actions fire. This ensures you only process legitimate, complete submissions.
How can I track which forms are generating the most submissions?
Elementor Pro includes a submissions dashboard under Elementor > Submissions in your WordPress admin. This interface displays all form submissions organized by form name with timestamps. For deeper analytics, I send form submissions to Google Analytics using a webhook to a Google Analytics Measurement Protocol endpoint or through Google Tag Manager event tracking.
Can I edit action configurations after a form is published?
Yes, you can modify action settings at any time by editing the page containing the form, selecting the form widget, and adjusting action configurations. Changes take effect immediately upon saving the page. I recommend testing forms after making action changes to ensure new configurations work as expected.
Is there a way to save form submissions in WordPress without a plugin?
Elementor Pro automatically saves all form submissions to the WordPress database, accessible under Elementor > Submissions. This built-in functionality requires no additional plugins and provides basic submission management including viewing, exporting, and deleting entries. For advanced features like submission editing or custom fields, dedicated form plugins offer more capabilities.
