How to Configure Elementor Form Actions for Email, Redirects, Webhooks and Marketing Integrations

Elementor form actions determine what happens after a visitor submits a form on a WordPress website. Instead of treating a form as only a group of fields and a submit button, you can define the next step: store the submission, notify a team by email, send a confirmation to the visitor, redirect the visitor, open a popup, or pass the data to another service.

The key setting is Actions After Submit in the Elementor Form widget. A single form can use several actions together, which makes it possible to create a workflow for both people and connected systems. This guide explains how to configure Elementor form email, visitor confirmations, redirects, webhooks and marketing integrations, while keeping data destinations and testing under control.

What Elementor Form Actions Do

Form actions are tasks performed after a visitor submits data through the Elementor Form widget. They are selected in the form settings under Actions After Submit. You do not have to choose only one outcome. Several actions can be active for the same form, provided each one is configured for the intended workflow.

For example, a form may collect submissions for storage, send an internal email to a team member, send a confirmation through Email 2, and redirect the visitor to a follow-up page. Another form may send its data to a webhook or use a supported marketing integration. The important distinction is the next step:

• Human-facing actions: email notifications, visitor confirmations and redirects.
• Storage actions: collecting submissions for later review.
• System-facing actions: webhooks and connections with marketing or communication services.

This approach lets you design the post-submission process around the actual purpose of the form rather than adding an action without checking where the data should go.

How to Add and Configure an Elementor Form Action

Start by opening the page in Elementor and selecting the Form widget. In the widget settings, open Content > Actions After Submit. Use the control for adding an action and select the required option, such as Email, Email 2, Redirect, Webhook or a supported integration.

After an action is selected, its own configuration fields appear in the widget. Configure each action separately and review the complete list before publishing. For example, Email has recipient and message settings, Redirect requires a destination URL, and Webhook requires an external endpoint. A marketing integration may require a connected service account or additional configuration.

Before going live, confirm that every selected action is intentional. Check the form fields, recipients, destination URLs and connected services. Save the form, then test the published form rather than assuming that selecting an action completes the setup. A test should verify both the visitor experience and the destination that receives the submission.

How to Configure Elementor Form Email

To send an internal notification, add or keep the Email action under Actions After Submit. Open its settings and configure the recipient, subject and message. You can also edit From Email, From Name and Reply-To. Optional copy settings include Cc and Bcc. Elementor also provides metadata and a choice between plain-text and HTML message format.

The recipient should be the person or team expected to review the submission. The subject should make the purpose of the message clear, while the message should contain only the information needed for that review. Email delivery depends on operational factors outside the form widget alone, so test the message with the relevant mail-server configuration and authentication in place. Do not treat the form settings as a guarantee that every message will reach an inbox.

Internal Notifications and Message Content

Elementor uses the [all-fields] placeholder to include all form fields in an email by default. This is convenient during initial setup, but it may send more information than the recipient needs. Individual field shortcodes can be used instead when you want to limit the message to selected fields.

Review the sender and reply settings before publishing. In particular, check that the recipient address is correct and that the Reply-To setting supports the intended response workflow. Review Cc and Bcc carefully because they determine who else receives the submission. Also check the selected message format and any shortcodes. Unsupported shortcodes can cause server errors, so the final email should be tested with sample data.

• Send only the fields required by the recipient or next step.
• Confirm recipient, sender and Reply-To values.
• Test the message format and field shortcodes.

Email 2: Confirmation Emails for Visitors

Email 2 is generally used for a confirmation message sent to the visitor who submitted the form. It can be used alongside the internal Email action: one message informs the team, while the other acknowledges receipt for the person who completed the form.

The form must include an Email field so the visitor’s address can be used in the To field for Email 2. Add Email 2 under Actions After Submit, map the recipient to the visitor’s email field, and configure the confirmation message. Review the mapping before testing, because an incorrect recipient setting can prevent the message from serving its intended purpose.

Keep the confirmation focused on useful information related to the submission. Avoid including more personal information than the workflow requires. Test the visitor-facing message separately from the internal notification and check whether both configured actions behave as intended.

Elementor Form Redirects and Thank-You Pages

The Redirect action sends visitors to a specified URL after submission. A thank-you page or follow-up page can be used as the destination when that matches the website’s workflow. Add Redirect under Actions After Submit and enter the required URL.

Redirect does not have to replace other actions. Elementor’s documented setup supports keeping actions such as Collect Submissions and Email active alongside Redirect when storage and notification are both required. This allows the visitor to receive a next step while the submission remains available to the relevant recipient or system.

Verify the destination URL before publishing. Test the redirect on the published page and confirm that the email, collection or other selected actions still run. A successful page transition does not by itself confirm that every other part of the workflow completed correctly.

Elementor Webhooks and Marketing Integrations

A Webhook action sends Elementor form data to an external endpoint. This is useful when the next step is system-to-system processing rather than a person reading an inbox. Elementor documents a Zapier workflow in which a catch-hook trigger is created first. The generated hook URL is then added to the form under Actions After Submit > Webhook.

The documented sequence is to create the catch-hook trigger, copy its URL into the Elementor form, submit test data, and then configure the downstream action in Zapier. The receiving platform must be checked to confirm that fields are mapped correctly. Webhook behavior, authentication, retries, rate limits and error handling can vary by receiving platform, so none of these outcomes should be assumed without testing the specific connection.

Elementor also documents native marketing actions for services including ActiveCampaign, ConvertKit, Drip, GetResponse, MailChimp and MailerLite. Zapier-based workflows can move collected leads into services such as MailChimp, MailPoet, ActiveCampaign, Campaign Monitor, GetResponse, Drip and HubSpot. HubSpot setup requires the relevant plugin, a connected HubSpot account and configuration that permits non-HubSpot forms.

Availability may depend on the Elementor subscription or hosting plan. A connected service may also require its own account, plugin or additional configuration. Check those requirements in the actual environment before designing the final workflow.

Choosing Email, Webhook or Native Integration

Use email when a person needs to read and respond to a submission in an inbox. Use a webhook when the data needs to move to another application or automation workflow, such as a Zapier trigger followed by an action in a connected service. Use a native marketing integration when the required service and account setup are supported.

This is a practical distinction, not a universal ranking. The appropriate choice depends on what should happen next to the lead. Treat webhook URLs and connected marketing accounts as sensitive configuration details. Use HTTPS endpoints where supported, test with non-sensitive sample data first, and verify field mapping before launch. Do not publish private webhook URLs in screenshots or public documentation.

Troubleshooting and Safety Checklist

A structured pre-launch review helps identify configuration problems before real submissions enter the workflow. Begin with the action list and then check every destination separately. A form can appear to work in the browser while an email, webhook or connected service still needs attention.

1. Confirm that the required actions are present under Actions After Submit.
2. Check internal recipient addresses, sender settings, Reply-To, Cc and Bcc.
3. Verify that the form includes an Email field when Email 2 is intended for the visitor.
4. Review [all-fields] and individual field shortcodes, removing information that the workflow does not need.
5. Confirm the Redirect destination URL and test it on the published page.
6. Test email delivery and do not assume that the form widget alone guarantees inbox placement.
7. For a webhook, protect the endpoint details, use HTTPS where supported and submit non-sensitive sample data.
8. Check the receiving platform’s field mapping after the test submission.
9. Review Elementor subscription or hosting plan requirements for the selected integration.
10. Confirm any required plugin, third-party account or connected-service configuration.

When a form collects personal data or marketing consent, align the form fields, consent wording, storage destination and retention practices with the laws and policies applicable to the audience and business. Transmit only the data needed for the stated purpose, and review every recipient and external destination before publishing.

Email can be appropriate for a person who reviews individual enquiries, but it should not automatically be treated as a complete lead-management system for high-volume workflows. A CRM, email marketing platform or automation service may be relevant when the process requires another way to organize submissions. The supplied documentation does not establish one universally correct workflow, so test the selected configuration in its actual environment.

Elementor form actions give one form several possible post-submission paths. Select them in Actions After Submit, combine storage, internal email, Email 2 and Redirect when the workflow needs those outcomes, and use Webhook or a native integration when data must reach another system. Configure each destination deliberately, limit the fields you transmit, and test with sample data before launch. Finally, review plan, hosting, plugin and third-party account requirements rather than assuming every integration is available in every setup. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.