An Elementor form is more than a field-and-button component. A useful workflow must determine what happens after a visitor submits it: whether the entry is stored in WordPress, who receives a notification, whether the visitor gets confirmation, where the visitor is redirected and whether selected data is passed to another service. Configuring these steps together makes it easier to review enquiries and check that no part of the process has been overlooked.
The central configuration point is the Form widget’s Actions After Submit field in the Content tab. From there, you can combine collection, email notifications, confirmation emails, redirects, selected marketing integrations, Slack or Discord notifications, popups and webhooks. The exact availability of an external service can depend on the site configuration, so the complete workflow should be tested with dummy data before the form is published.
What a reliable Elementor form workflow should include
A reliable workflow starts with a clear sequence. First, decide whether Elementor form submissions should be collected in WordPress. Internal storage gives the authorised site team a place to review entries in WP-Admin. It should not, however, be treated as the only part of the process when the team also needs immediate alerts or an external automation.
Next, separate the internal notification from the visitor confirmation. The site or team may need an email containing the submitted information, while the person who completed the form may need a different acknowledgement. Elementor documents separate actions for these uses.
A redirect can then provide the next step after submission, such as a suitable thank-you page. At the same time, a selected marketing integration, Slack or Discord notification, or webhook can pass information onward. Several actions may be combined, so one submission can be collected, emailed, forwarded and followed by a redirect. None of these actions should be assumed to guarantee storage, delivery or external processing until the entire path has been tested.
Save and manage Elementor form submissions in WordPress
To save Elementor form submissions, edit the page containing the Form widget and open the Actions After Submit field in the widget’s Content tab. Check that Collect Submissions is present and enabled. Elementor documentation states that this action is active by default when available, but verifying the setting is still a practical step before publishing.
After a visitor submits the form, collected entries can be accessed in WordPress Admin under Elementor > Submissions. The submissions area provides a list of entries, and administrators can open individual records to review their contents. This gives a site owner or authorised team member a direct place to inspect incoming form data without relying only on email notifications.
Send a test entry after configuring collection. Use dummy information and confirm that the record appears in the submissions area. A successful redirect or visible confirmation does not by itself prove that the entry was stored, so check the record directly.
Where to find collected entries
In WP-Admin, go to Elementor > Submissions. Start with the list view to confirm that the test entry exists, then open the individual entry to check whether the expected fields were recorded. Keep access to these records limited to authorised WordPress users. Names, email addresses, messages, uploaded files and other identifiable information should be handled as personal data, with storage and access practices aligned with the obligations that apply to the website.
Export Elementor form entries to CSV
Elementor provides a CSV export option in Elementor > Submissions. To download the complete list, use Export All to CSV. If you need only particular records, mark the relevant entries with their checkboxes and choose Export Selected to CSV.
After downloading the file, check that its contents are readable and that the expected records and fields are present. CSV export can be useful for a defined handoff or review, but it should not automatically be treated as a replacement for a full CRM or a carefully designed data-management process.
Export only what is needed. Store the file in a controlled location, do not share it unnecessarily and remove copies that are no longer required according to the website’s applicable data-handling practices. Do not place webhook URLs, API keys, secret keys or other integration credentials in an export or related documentation.
Configure notifications and confirmation emails
Use Email in Actions After Submit when the site or team should receive a notification about a new submission. Review the recipient and the fields included in the message so that the notification contains useful information without sending unnecessary data.
For a message to the visitor, Elementor documents Email 2 as the confirmation-email action. Configure it separately from the internal alert and verify that the recipient address comes from the intended form field. A visitor confirmation and a team notification serve different purposes, so testing both messages is important.
Email delivery should be checked on the production domain rather than assumed. Messages may be filtered into spam, and delivery can depend on the hosting mail system, domain authentication, recipient-provider filtering and other spam controls. Elementor documentation recommends considering separate email-delivery tooling where appropriate, but no notification should be described as guaranteed.
Internal alerts versus visitor confirmations
Email is intended for the site or team, while Email 2 can be used for a visitor acknowledgement. Test the recipient addresses, the values inserted into each message and the destination folders. Use dummy data and confirm both the internal message and the visitor message before making the form public.
Redirect visitors after submission
The Redirect action sends the visitor to another page after the form is submitted. Configure it in the same Actions After Submit field and select a destination appropriate to the next step of the process, such as a thank-you page or another relevant page.
Test the redirect on desktop and mobile layouts. Also check the submission record and notification during the same test. A correct redirect is only one part of the workflow and does not prove that the entry was stored, that an email was delivered or that an external service received the data.
Connect Elementor forms to marketing and automation tools
Elementor documents connections to selected marketing platforms and notifications for services such as Slack and Discord. When the required service is supported in the specific site configuration, use the documented integration and define which form fields should be transferred.
For an external automation platform, use the WebHook action. Elementor describes webhooks as a way to share submitted form information with third-party platforms and gives Zapier as an example use case. This can create a handoff from the form to another workflow, but the destination still needs to be configured and tested.
Before enabling the handoff, check the selected service’s requirements for authentication, field mapping, payload handling and data access. The reviewed documentation does not establish one universal payload schema, authentication method, retry behaviour or field-mapping process for every platform. It also does not confirm that every marketing or automation service is available on every Elementor plan or every website configuration.
Native integrations and webhook handoffs
A native integration is a practical choice when the required destination is supported in the exact configuration being used. A webhook is a more general handoff for sharing submitted information with an external platform or automation service. In both cases, send only the fields that are necessary, verify how the destination receives them and keep credentials private. Do not expose webhook URLs, API keys or secret keys in screenshots, public documentation or client-facing exports.
Before sending submissions to an external service, review that service’s data-processing terms, access controls and retention settings, and ensure that the site’s privacy documentation reflects the actual workflow. If a form collects sensitive information, avoid transmitting it to destinations that are not necessary for the stated process.
Spam, privacy and reliability checks before launch
Public forms should use anti-spam protection appropriate to their risk profile. Elementor documents reCAPTCHA v2 and v3 integration for reducing bot submissions. The documented setup requires site and secret keys in Elementor > Settings > Integrations, followed by adding the corresponding reCAPTCHA field to the Form widget.
The documented Elementor integration does not support Google’s reCAPTCHA Enterprise API. reCAPTCHA should also not be presented as a complete solution for every form of spam or abuse. Choose protection according to the form’s exposure and test the resulting visitor experience.
Limit WordPress access to stored submissions to authorised users. Treat names, email addresses, messages, uploaded files and other identifiable details as personal data. Before connecting marketing or automation tools, review the destination’s access and retention controls and align the workflow with the privacy obligations that apply to the website.
Pre-launch workflow checklist
- Submit the form with dummy data and confirm that Collect Submissions stores the entry.
- Open Elementor > Submissions and inspect the individual record.
- Check the internal notification and the visitor confirmation, including spam folders.
- Confirm that the redirect opens the intended page on desktop and mobile.
- Verify that the selected integration or webhook receives the expected fields.
- Remove test records and protect any exported files or integration credentials.
Run this check again after significant changes to the form, recipients, destination service or anti-spam configuration. A workflow can appear correct in the editor while still failing at delivery or at the external handoff, so the end-to-end test is the meaningful final check.
Elementor form submissions can support a complete process when collection, notifications, visitor confirmation, redirect and external handoff are configured as connected actions rather than isolated options. Start by enabling and testing Collect Submissions, then add only the notifications and integrations required by the website. Export records carefully, restrict access to personal data and verify the exact behaviour of every external destination. Remember that service availability, payload handling and email delivery must be checked for the specific site and configuration. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.