Elementor

Run flows the moment an Elementor Pro form is submitted on your WordPress site. Paste the FlowRunner callback URL into the form's webhook action and each submission arrives parsed, with field values keyed by ID and an optional form name filter to target a single form.

1 trigger 0 actions Custom auth available

Elementor website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

On New Form Submission fires the instant a visitor submits the Elementor Pro form on your WordPress site

The agent reads the normalized field values, name, email, company, and the message, keyed by field ID

The lead is created or updated in the CRM, matched on email so repeat submitters do not duplicate

The agent scores the submission, budget signals, company domain quality, and message intent, against the team's routing rules

High-intent leads post to the sales channel immediately with the full answers and the page they came from

The rep reads the submission and decides the first response, because the opening message sets the relationship

The approved reply goes out and the follow-up task lands in the tracker

What This Integration Enables

Elementor is a page builder, not an API platform, and this connector is honest about that: there is no endpoint to list forms or fetch submissions later. What Elementor Pro does give you is a webhook action on every form, and that is enough, because the moment of submission is the only moment that matters for a lead. Paste the FlowRunner callback URL into the form's webhook action once, and every submission arrives parsed, with fields keyed by ID, form name and page URL attached, and an optional form name filter so each flow listens to exactly the form it should. - Fire flows in real time from any Elementor Pro form on the site - Receive submissions normalized: field array, flattened value map, and the raw payload - Scope flows to a single form with the Form Name filter, or catch every form on one URL - Route leads to CRM, sheets, chat, and email tools in one pass - Verify authenticity with your own hidden field or header, validated in the flow This is also the pattern that makes a WordPress site a first-class citizen in an orchestrated stack. The site does what it is good at, presenting forms people actually fill in, and FlowRunner does what WordPress plugins are bad at: coordinating the CRM write, the team alert, the reply draft, and the audit log as one governed flow with a [human-in-the-loop](/concepts/human-in-the-loop) gate on the customer-facing step. Marketing keeps full control of the pages; operations gets full control of what happens after the submit button. Neither team files a ticket with the other.

Without FlowRunner

Leads sit in a WordPress inbox Submissions collect in the site's database and email, waiting for someone to check

Speed-to-lead measured in days The hot prospect who submitted Friday evening hears back Tuesday

Every form is a copy-paste job Answers get retyped into the CRM, the sheet, and the reply, with errors at each hop

With FlowRunner

Submissions become events Every form post fires a flow in real time with parsed, field-keyed data

The team knows in seconds High-intent submissions reach the sales channel while the visitor is still on the site

Data lands everywhere at once CRM, sheet, and notification all populate from one normalized payload

Use Case Scenarios

The demo request that gets a same-minute response

A visitor submits the demo request form. The flow fires, creates the contact in [HubSpot](/integrations/hubspot) matched on email, and posts the submission to [Slack](/integrations/slack) with every answer and the page it came from. The rep on duty claims it, and the draft reply the agent prepared from the form answers is ready for review in [Gmail](/integrations/gmail). The prospect who expected an autoresponder gets a specific, human-approved reply while their tab is still open.

One callback URL, a whole site's worth of forms

The agency runs a site with a contact form, a newsletter signup, and a careers form, all posting to the same FlowRunner callback. Three flows listen, each scoped by Form Name. Contact submissions go to the CRM and sales channel, newsletter signups become contacts in [Brevo](/integrations/brevo), and careers submissions land in the hiring tracker in [Airtable](/integrations/airtable) with the resume link intact. Adding a fourth form to the site means adding one webhook action in Elementor and one filtered flow, not a new integration project.

The submissions log that survives WordPress

Every submission appends to [Google Sheets](/integrations/google-sheets): timestamp, form name, page URL, and each answer in its own column from the flattened value map. When the site gets rebuilt or a plugin update misbehaves, the lead history lives outside WordPress. The weekly flow summarizes volume by form and page, which is how the team learns the pricing page's form converts at twice the rate of the homepage's, and shifts traffic accordingly.

Human-in-Loop Highlight

On New Form Submission delivers a real person's contact details and their exact words, and everything costly in this integration happens in what the flow does next: the reply that lands in the prospect's inbox, the contact written into the CRM, the lead routed to a rep's queue. The first response is the one operation that cannot be recalled once it sends, and it is the prospect's first impression of how your company communicates. So FlowRunner flows draft it but do not send it: the agent assembles the reply from the form answers, attaches the submission and source page, and hands it to the rep for approval. The same discipline applies to trust in the payload itself. Elementor sends no signature, so flows validate the optional hidden-field secret before acting, and any submission that fails the check is quarantined for a person to inspect rather than written into systems of record. The webhook fires at machine speed. The words a prospect reads were approved by someone accountable for them.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

0 actions

Capabilities

Triggers

1 triggers

Event Triggers

On New Form Submission Fires in real time when an Elementor Pro form posts to the FlowRunner callback URL configured in the form's Webhook action. Each run receives the form's name and ID, the source page URL and title when available, a fields array of id, label, type, and value objects, a flattened field-to-value map for direct access, and the raw payload as Elementor sent it. The optional Form Name filter scopes the flow to a single form when multiple forms share the callback URL.

Frequently Asked Questions

Does connecting Elementor to FlowRunner require OAuth?

Elementor uses a custom authentication method to connect to FlowRunner.

Can Elementor trigger a FlowRunner workflow automatically?

Yes. Elementor supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Elementor

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us