FlowRunner
PricingContact
Theme
Start Free

RD Station

Email Marketing

Sync leads into RD Station Marketing from any workflow. Agents upsert contacts by email, register conversion events, send custom events, enrich leads with tags and custom fields, and flag qualified leads as sales opportunities.

6 actions OAuth available
RD Station website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A lead submits a webinar registration form outside RD Station
Get Contact By Email checks whether the lead already exists with tags and history
Upsert Contact merges the new details, name, job title, tags, and cf_ custom fields
Track Conversion Event registers the webinar sign-up against the lead, the same mechanism as a native form submission
The agent scores the lead's accumulated conversions and firmographics against the qualification bar
The sales lead confirms qualification for leads the agent scores at the threshold
Mark Opportunity flags the confirmed lead as a sales opportunity with a funnel name and estimated value

What This Integration Enables

RD Station Marketing is where Latin American marketing teams run their lead machine, and the machine is only as smart as the events it sees. A lead who converts on three external touchpoints but shows an empty RD Station profile gets nurtured like a stranger. FlowRunner agents close that gap: they upsert contacts by email from any system that captures a lead, register conversions through the same mechanism RD Station uses for its own forms, and push custom events for everything in between, so segmentation, lead scoring, and lifecycle automation operate on the lead's full story. - Sync leads captured in forms, landing pages, and other apps into RD Station by email - Register landing-page conversions, downloads, and webinar sign-ups against the lead - Enrich contacts with names, tags, and cf_ custom fields as data improves - Send custom events for chat, media playback, and activities the conversion action does not cover - Flag qualified leads as opportunities with funnel name and monetary value The design principle is to feed RD Station rather than replace it. Marketing teams invest heavily in the automations, scoring models, and segmentations they build inside the platform; the failure mode is not bad automation but blind automation, journeys reacting to a fraction of the customer's actual behavior. FlowRunner agents make the platform's existing intelligence better informed instead of building a parallel brain beside it. The opportunity flag is where marketing hands revenue a promise, so that is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate stands. Everything upstream of that promise runs at machine speed.

Without FlowRunner

Leads outside RD Station vanish Sign-ups in external forms and apps never reach the platform where nurture actually runs
Conversions go unrecorded A lead attends a webinar or downloads a guide, and their RD Station profile shows none of it
Opportunity is a gut call Leads become opportunities when someone remembers to flag them, so the funnel reports mood

With FlowRunner

Every touchpoint syncs by email External captures upsert into RD Station with tags and custom fields in the same run
The conversion history is complete Landing pages, downloads, and sign-ups register as conversion events wherever they happen
Opportunities are earned and confirmed Agents score the evidence, a person confirms, and the funnel reports reality

Use Case Scenarios

The external form that feeds the nurture machine

A [Typeform](/integrations/typeform) lead magnet collects a sign-up. The agent calls Upsert Contact with the respondent's email, name, and answers mapped to cf_ custom fields, then Track Conversion Event with the campaign's conversion identifier. RD Station treats it exactly like a native form submission: scoring updates, segmentation recalculates, and the automation flows built in RD Station fire on schedule. Marketing keeps its RD Station automations exactly as built; FlowRunner just makes sure they see everything.

Qualification with evidence, promotion with sign-off

The agent watches accumulated conversions per lead. When a lead crosses the bar, three conversions, a director title, a target-market country, the agent pulls the full profile with Get Contact By Email and posts the case to [Slack](/integrations/slack): who, what they did, why now. The sales lead confirms with a reaction, and Mark Opportunity fires with the funnel name and estimated value attached. Sales gets a briefed opportunity instead of a bare flag, and the funnel report counts only leads a person agreed were real.

The marketing report that reconciles itself

Weekly, the agent looks up the leads touched by that week's campaigns with Get Contact By Email, and appends each profile, tags, custom fields, lifecycle state, to [Google Sheets](/integrations/google-sheets). The report shows which external sources actually produced qualified leads, with RD Station's own data as the source of truth. Nobody assembles it, and it never disagrees with the platform, because it is read from the platform on the morning it is needed.

Human-in-Loop Highlight

Mark Opportunity is a small API call with organizational consequences. The OPPORTUNITY event moves a lead into sales's territory: it changes lifecycle state, lands in funnel and revenue reporting with whatever monetary value was attached, and, in most RD Station setups, summons a salesperson to spend real time on the lead. An agent that marks opportunities on an over-eager heuristic pollutes the one metric marketing and sales both answer for, and teaches sales to ignore the flag, which is worse than never raising it. So FlowRunner agents do the accumulation and the scoring, then stop. The promotion to opportunity happens when a person looks at the evidence the agent assembled and agrees. Upserts and conversion events flow autonomously all day; the handshake between marketing and sales stays a handshake.

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

6 actions

Contacts

3
  • Get Contact By Email Retrieves a lead by email using the email: identifier syntax, returning UUID, name, job title, tags, and custom fields. The lookup before any update, score, or routing decision.
  • Get Contact By UUID Retrieves a lead by their RD Station UUID using the uuid: identifier syntax. Used when a prior step already holds the platform identifier.
  • Upsert Contact Creates or updates a lead identified by email, merging name, tags, and cf_-prefixed custom fields. The primary write for syncing lead data from any external source.

Events

3
  • Track Conversion Event Registers a conversion against a conversion identifier for the lead, the same mechanism RD Station uses for form submissions. Creates the lead if needed. The event behind landing pages, downloads, and sign-ups.
  • Send Event Sends a generic CDP-family event with a custom payload for anything the conversion action does not fit: chat events, media playback, custom activities.
  • Mark Opportunity Flags a lead as a sales opportunity, optionally with monetary value and funnel name, driving lifecycle and funnel reporting. The promotion this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with RD Station?

FlowRunner agents can run Get Contact By Email, Get Contact By UUID, and Upsert Contact in RD Station, plus 3 more actions.

Does connecting RD Station to FlowRunner require OAuth?

Yes. RD Station connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can RD Station trigger a FlowRunner workflow automatically?

RD Station doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with RD Station

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