Elementor Form Not Sending to RD Station? A Troubleshooting Checklist

Your Elementor form says “thank you”, but the lead never shows up in RD Station. Here is a checklist that finds the cause in minutes — because with Connect Elementor Forms to RD Station, no failure is ever silent.

Start at the Logs tab — always

The plugin records every delivery with the full request and response in its Logs tab. Before changing any setting, open the log entry for your test submission and read what RD Station actually answered. Nine times out of ten, the response names the problem — a missing required field, an expired authorisation, a validation error.

[PLACEHOLDER: screenshot — Logs tab with a failed delivery expanded]

One important thing to understand: your visitor sees the confirmation message before delivery happens — that’s deliberate, so a slow RD Station never slows your form down. It also means a successful form submission is not proof of a successful delivery. The log is.

No log entry at all? Check these first

• Is Elementor Pro active? The Forms widget is an Elementor Pro feature — the plugin has no forms to hook into without it.
• Is the integration pointing at the right form? Each integration is tied to one Elementor form. If you rebuilt or duplicated the form, re-select it in the integration.
• Is the integration switched on? Open the Integrations tab and confirm it is active, with the form and field mapping in place.

Delivery failed? The usual causes

1. A required field isn’t mapped

RD Station requires the same field it requires on its own forms: an email for a Marketing conversion — plus any custom field your account marks mandatory, which the plugin adds to the required list automatically. Check the mapping against the Field mapping doc.

2. The connection or app permissions

The plugin authenticates with an app you registered in the RD Station App Store. That app needs the RD Station Marketing permissions — an app registered with CRM permissions alone cannot deliver a conversion. Also confirm the callback URL registered in the app matches the one shown on the plugin’s Settings tab. The Getting started doc walks through the whole connection.

3. RD Station was temporarily unavailable

If RD Station’s API is down or unreachable, the submission is not delivered and the failure is recorded in the log with the full response. The free version does not retry — you’ll need to re-send that lead manually. The Pro version queues every submission and retries failed sends automatically with increasing delays.

“It worked, but I don’t see a new lead”

That may not be a failure. RD Station identifies leads by email: when a returning visitor submits again, the conversion is recorded on the lead they already have rather than creating a second one. Open that lead and check its conversion history — the submission is probably there.

Still stuck?

Open the log entry for the failed delivery and copy the full request and response — with those two pieces, almost any problem can be diagnosed. [PLACEHOLDER: support contact link]