Contact Form 7 Not Sending to RD Station? A Troubleshooting Checklist

Your Contact Form 7 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 Contact Form 7 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. Most of the time, 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 Contact Form 7’s confirmation 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 Contact Form 7 active? The plugin has no forms to listen to without it.
• Did Contact Form 7 accept the submission? A submission it rejects — a validation error, spam, or a missing acceptance checkbox — is not sent to RD Station. Submit a clean test entry and confirm the form shows its success message.
• Is the integration pointing at the right form? Each integration listens to one Contact Form 7 form. If you duplicated the form or built a new one, it’s a different form — 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.

The form says the message failed to send?

That message is about Contact Form 7’s notification email, not RD Station. Delivery to RD Station doesn’t depend on the email, so the lead is still sent — check the Logs tab to confirm. Fix the email separately, usually with an SMTP plugin.

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 field type is never sent

File uploads, quizzes and CAPTCHAs are not sent to RD Station. If a value you expected is missing, check which Contact Form 7 field type it came from.

3. 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.

4. 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 automatically with increasing delays, up to five attempts.

“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. Then contact support, or start again from the step-by-step setup guide.