RD Station

RD Station

· #210 most-used

Turn leads into customers with Brazil's leading marketing automation platform

CRMSalesMarketingAnalyticsAutomationEmail MarketingLead Generation

RD Station is a comprehensive digital marketing and CRM platform built for growing businesses in Latin America and beyond. It combines lead generation, email marketing, landing pages, marketing automation, and sales pipeline management in a single suite — helping teams attract traffic, capture leads, nurture them through automated flows, and hand qualified opportunities to sales. Connect RD Station to Actionist and your agents can register conversion events, mark deals won or lost, pull contact and funnel data, and orchestrate multi-step lead-to-close workflows without anyone touching the dashboard.

Average time saved
14 hours
per person · per month
≈ 2 workdays back

Eliminates manual work. Agents eliminate the manual work of logging conversion events, updating funnel stages, moving leads between workflows, and compiling weekly pipeline reports from the RD Station dashboard.

Schedule

What your RD Station agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
TueThu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

RD Station × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
6Apps spanned
~16 hrsSaved / week
5Personas served
For marketing
Featured4 apps

Demo request auto-routed to sales rep within minutes

Within about a minute of a demo form submission, the lead's full profile is in the rep's CRM, the correct automation sequence is running in RD Station, and a Slack alert with company context lands in #sales-alerts — the rep books the demo without touching the CRM manually.

~8 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a visitor submits the 'Request a Demo' form on the website
Result
Add tag 'Demo-Requested' to trigger the sales-ready automation flowCreate deal in HubSpot CRM assigned to the correct territory repPost lead profile and company context to #sales-alertsCreate a suggested demo slot on the rep's calendar for the following day
The win
Saved per run
15 min
Runs / week
~30×
No demo request goes unrouted or sits unworked for more than an hour
Driven byMarketing Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    45 min / week
    Manual deal closure and CRM updates

    Sales reps manually update deal stages in RD Station CRM at the end of each day, often forgetting to close deals until the weekly pipeline review catches the discrepancy.

    Sales Agent
    0 min
    Agent closes deals and routes opportunities automatically

    When a contract is signed, the agent marks the deal Won in RD Station, writes ARR to the revenue tracker, and posts the win to #wins — the rep never touches the CRM manually.

  • Marketing
    90 min / week
    Manual lead imports and event registration

    The marketing team manually imports CSV files of event attendees, webinar registrants, and offline leads into RD Station, often days after the event, causing delayed nurture-sequence starts.

    Marketing Agent
    0 min
    Agent registers conversion events from every channel automatically

    Whether leads arrive from a webinar, a partner referral, or an offline event, the agent creates a conversion event in RD Station within about a minute — every lead enters the correct nurture sequence from the first touch.

  • Customer Support
    60 min / week
    Weekly manual churn-risk review

    The support team compiles a churn-risk list once a week by cross-referencing the ticket system with the CRM, then manually updates tags in RD Station — at-risk customers can wait 7 days before entering retention flows.

    Customer Support Agent
    0 min
    Agent tags churn-risk contacts and activates retention flow within minutes

    When support ticket volume crosses the threshold, the agent adds the Churn-Risk tag in RD Station and alerts the CSM — all within about a minute of the signal, before the customer disengages further.

  • Human Resources
    40 min / week
    Manual applicant entry and funnel management

    HR manually creates RD Station contact records for each new applicant from the ATS or a spreadsheet, adding tags and stage data by hand — taking 5–10 minutes per applicant during high-volume hiring periods.

    Human Resources Agent
    0 min
    Agent registers application events and manages candidate funnel stages

    New applicants are created as RD Station contacts with the correct tags and conversion events within about a minute of applying, so they're in the recruiter's pipeline immediately rather than after a batch import.

  • Finance
    90 min / week
    Manual pipeline and ARR reporting

    Finance manually exports pipeline data from RD Station each week, pastes it into the revenue model, and calculates coverage ratios by hand — a process that takes 90 minutes and is often done the night before the leadership meeting.

    Finance Agent
    0 min
    Agent compiles pipeline coverage and ARR data without manual reporting

    Every Monday the Finance Agent pulls funnel analytics from RD Station, calculates pipeline coverage against the quarterly target, and posts the result to #finance — ready before the leadership call without anyone building the report.

  • Operations
    30 min / week
    Periodic manual data-hygiene sprints

    Operations runs a manual data-quality project every quarter — exporting contacts, identifying field gaps and tag errors in a spreadsheet, and re-importing corrected records into RD Station — typically taking a full day per sprint.

    Operations Agent
    0 min
    Agent runs contact hygiene and automation-eligibility repairs on a schedule

    Every Monday the Operations Agent identifies contacts with missing fields or broken automation eligibility, updates them in RD Station, and posts a repair report — data stays clean without a data-ops sprint.

  • Legal
    60 min / week
    Manual LGPD compliance checks and opt-out processing

    The legal team manually reviews opt-out requests once a week, looks up each contact in RD Station, removes the relevant tags by hand, and keeps a separate compliance spreadsheet — a process that takes 2–3 hours when volume is high.

    Legal Agent
    0 min
    Agent processes opt-outs and monitors LGPD consent on a weekly cycle

    Every Thursday the Legal Agent processes all opt-out requests — removing marketing tags and registering the data-processing-ended event in RD Station — and the weekly LGPD consent audit runs automatically with no human effort.

+ 100s of other RD Station automations
Average time saved
42 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
18
Hours saved / year
875
Annual ROI
$65,625

Based on RD Station's typical team usage — the visible tasks plus a few other automations the agent runs: ~3.5 hrs / person / week of admin work automated.

Connect

How to plug RD Station into Actionist

Pick the connection method that suits your environment.

Connect with an RD Station API Key — the quickest path for most users. Generate the key in your RD Station Marketing account under Marketing → Integrations → API Key and paste it into Actionist.

1
Open RD Station Marketing

Log in to your RD Station Marketing account and navigate to Marketing → Integrations → API Key.

2
Copy your API Key

Copy the token shown on the API Key page. Treat it like a password — store it in a secrets manager rather than plain text.

3
Paste into Actionist

Paste the key into the field below and click Test Connection. Actionist will verify the handshake with a read-only API call.

Credentials you'll need
API Key*
RD Station Marketing → Marketing → Integrations → API Key
Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

2 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

MCP servers

MCP servers that work with RD Station

Connect Actionist to MCP servers built for or around this app.

mcp-rd-station

Community MCP server for RD Station — provides access to contacts, conversion events, funnels, and opportunities through the Model Context Protocol.

FAQs

Questions about RD Station + Actionist

How does Actionist connect to RD Station?
Go to the Apps tab in Actionist, find RD Station, and click Connect. The recommended path is the API key method — go to RD Station Marketing, navigate to Marketing → Integrations → API Key, copy your key, and paste it into Actionist. An OAuth flow is also available for apps that use the RD Station OAuth2 standard. Actionist runs a test call to verify the connection before any actions run. Once connected, agents can read and write contacts, conversion events, funnel data, and deals across both RD Station Marketing and RD Station CRM.
Does Actionist work with both RD Station Marketing and RD Station CRM?
Yes. RD Station offers two products — RD Station Marketing (lead generation, email marketing, landing pages, automation flows, funnel analytics) and RD Station CRM (deal pipeline, won/lost tracking, sales tasks). Actionist connects to both. Marketing-side actions cover conversion events, contact management, segmentation, funnel analytics, and landing page stats. CRM-side actions cover marking deals won or lost, managing opportunities, and retrieving deal data. The triggers (New Lead Conversion, New Opportunity) originate from RD Station Marketing's webhook system and fire into both products' pipelines.
What is a Conversion Event in RD Station and why does Actionist use it so often?
A Conversion Event is RD Station Marketing's fundamental data record — it's how the platform registers that a contact took a meaningful action (submitted a form, downloaded content, attended a webinar, started a trial). Every conversion event has a name, a timestamp, and optional metadata. Actionist uses Create Conversion Event frequently because it's the correct way to introduce a contact to the RD Station funnel from any external source, to advance them through automation flows, and to log lifecycle changes. A contact without conversion events won't enter most RD Station automation sequences, so registering the correct events is the key to making the platform work across all connected tools.
How do the New Lead Conversion and New Opportunity triggers work in Actionist?
Both triggers use RD Station Marketing's webhook system. When you enable them in Actionist, Actionist registers a webhook with your RD Station account. New Lead Conversion fires within about a minute whenever any contact completes a conversion event in your RD Station account — a form fill, a landing page submission, or an API-registered event. New Opportunity fires within about a minute when a lead is marked as an Opportunity, either manually by a rep or by an RD Station automation rule. Each webhook payload includes the contact's email, name, company, conversion event details, and funnel stage, giving Actionist's agents everything they need to route, enrich, or act on the event.
Can I use Actionist to keep RD Station in sync with another CRM like HubSpot or Pipedrive?
Yes. A common pattern is to use RD Station for top-of-funnel marketing automation and lead nurturing, then sync qualified opportunities to HubSpot, Pipedrive, or Salesforce for the sales team. The New Opportunity trigger fires in Actionist when a lead is promoted in RD Station, and the agent's next steps can create or update the deal in the other CRM, map the contact's field data, and write back the RD Station contact ID for two-way syncing. When a deal is Won in the other CRM, the agent calls Mark Deal as Won in RD Station so the two systems stay consistent.
RD Station is a Brazilian platform — does Actionist support it in Portuguese and handle LGPD compliance?
Actionist's agents operate in the language you configure for your workspace — workflows and task outputs can be written in Portuguese if your team works in Portuguese. On LGPD: Actionist helps you automate consent management in RD Station by tagging contacts with consent status on entry, removing marketing tags for opt-out requests, and registering data-processing-ended conversion events when a contact exercises their LGPD rights. Actionist processes your RD Station data strictly to execute the actions you define and does not retain contact data beyond the task execution context. Your LGPD compliance programme should include legal advice specific to your business — Actionist is an execution layer, not a legal guarantee.
What is the difference between tagging a contact and registering a conversion event — when should I use each?
Tags and conversion events serve different purposes in RD Station. Tags are labels that determine which segmentation filters and automation flows a contact belongs to — they're stateful (a contact either has a tag or doesn't). Conversion events are time-stamped records of actions taken — they're additive and build the contact's journey history. Use tags when you want to activate or exit an automation sequence, control segment membership, or mark a lifecycle state. Use conversion events when you want to record that something happened at a specific time, advance a contact through a funnel, or build a journey history that informs future personalisation. Actionist agents typically do both: register the conversion event first, then add the appropriate tag.
Can Actionist help clean up duplicate or incomplete contacts in RD Station?
Yes. The Operations Agent can run a scheduled hygiene sweep using List Segmentation Contacts to identify contacts meeting your 'suspect duplicate' or 'missing field' filter criteria — contacts with no company name, for example, or contacts with a tag that should have been removed after a campaign. The Update Contact Fields action fills missing standard and custom field values using enrichment data from connected tools like Clearbit or Google Sheets. For deduplication at scale, the agent can identify duplicate email addresses across a segmentation export and flag them for manual review or merge via the RD Station API. Actionist can automate the detection and bulk-update, but full merge requires action in RD Station itself.