How to Connect Elementor Forms to RD Station (Step by Step)

Elementor Pro’s Forms widget collects the lead — but out of the box, the submission stays in WordPress. This guide walks through connecting your Elementor forms to RD Station with the free Connect Elementor Forms to RD Station plugin, so every submission arrives in RD Station automatically, with lead source attribution intact.

What you’ll need

Elementor Pro — the Forms widget is a Pro feature, so the free version of Elementor is not enough.
An RD Station account — either RD Station Marketing (any plan with API access) or RD Station CRM (any plan, including the free one).
The plugin — download the free version from the plugin page.

Step 1 — Install and activate the plugin

In your WordPress admin, go to Plugins → Add New → Upload Plugin, choose the zip you downloaded, install it and activate it. You’ll find the plugin’s screen in the admin menu, with three tabs: Settings, Integrations and Logs.

[PLACEHOLDER: screenshot — plugin admin screen after activation]

Step 2 — Create an app in the RD Station App Store

The plugin talks to RD Station through an app registered in your own RD Station account — your credentials never pass through anyone else’s servers.

In the RD Station App Store, create a new app and give it the permissions for the product you’re connecting — Marketing, CRM, or both.
On the plugin’s Settings tab, copy the callback URL shown there and register it in your app.
Paste the app’s Client ID and Client Secret into the Settings tab and click connect. You’ll be sent to RD Station to authorise, then back to your site.

[PLACEHOLDER: screenshot — Settings tab with callback URL and credential fields]

Your OAuth tokens are stored encrypted in your own database, and the plugin sends data nowhere except RD Station’s API. The full details are in the Getting started doc.

Step 3 — Create an integration

Open the Integrations tab and create your first integration:

Choose the destination — RD Station Marketing (the submission arrives as a conversion event) or RD Station CRM (the submission adds or updates a contact). Not sure which? See our guide on choosing between Marketing conversions and CRM contacts.
Pick your Elementor form from the list.

Step 4 — Map your fields

Mapping tells the plugin which Elementor field goes to which RD Station field. The mapping screen offers your account’s real fields — custom fields included — instead of asking you to type identifiers, and after the first submission it suggests your form’s field names automatically.

[PLACEHOLDER: screenshot — field mapping UI]

You only have to map the same fields RD Station itself requires on its own forms:

Email for a Marketing conversion. Mapping email also gives you duplicate protection on the CRM side — returning visitors update their existing contact instead of creating a new one.
Name for a CRM contact.
Any custom field your account marks mandatory is added to the required list automatically.

The free version maps up to two fields per integration — enough for the required field plus one more. For more mappings, tags, funnel stage and the rest, see the Pro version. The Field mapping doc covers every option in detail.

Step 5 — Submit a test and check the log

Open the page with your form, submit a test entry, then check two places:

RD Station — the conversion event or contact should be there.
The plugin’s Logs tab — every delivery is recorded with the full request and response, success or failure. Nothing is silent.

Delivery happens after your visitor already has their confirmation, so even a slow RD Station never slows your form down.

What about lead source attribution?

If the visitor has RD Station’s tracking cookies (_rdtrk, __trf.src), the plugin forwards them with each Marketing conversion — so your funnel and traffic source reports stay accurate, exactly like a native RD Station form. There’s nothing to configure; it’s automatic.

Going further

The free version handles one integration with two mapped fields. When you outgrow it, Pro adds unlimited integrations and mapped fields, conversion identifiers, tags, funnel stage, lead owner and opportunity flag, CRM companies and deals, and a delivery queue that retries failed sends automatically.