RD Station Marketing is a marketing automation and lead generation platform that helps businesses attract, convert, and nurture leads. It provides tools for email marketing, landing page creation, lead scoring, and marketing analytics to improve conversion rates and customer acquisition.
The RD Station destination supports two operating modes:
- Contacts — creates or updates contacts via the RD Station Contacts API.
- Qualification Events — sends contact qualification events (opportunity, sale, or lost) via the RD Station Events API.
1. Add your RD Station Marketing access
-
In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the RD Station option from the list of connectors.
-
Click Next and you’ll be prompted to add your access:
- Authorization: Complete RD Station authorization to grant permissions for Nekt to load data.
- Mode: Select the operating mode for the connector:
- Create/Update Contacts — maps your input table columns to RD Station contact fields and creates or updates contacts.
- Qualification Events — maps your input table columns to event fields and sends qualification events (opportunity, sale, or lost) to RD Station.
- Enable partial success: Whether the connector should continue trying to sync records after one fails.
-
Click Next.
2. Select your data to send
-
The next step is letting us know which data you want to send. Select the layer and then the desired table.
Tip: The table can be found more easily by typing its name.
-
Click Next.
3. Map your columns
Map the columns from your input table to the corresponding RD Station fields. The available destination fields depend on the mode you selected.
In contacts mode, each row in your input table represents a contact to create or update. The email field is required — it’s used as the unique identifier for upserting contacts.
Available destination fields:
| Destination field | Description |
|---|
email | Contact email address (required) |
name | Contact full name |
job_title | Contact job title |
birthdate | Contact birthdate |
bio | Contact biography |
website | Contact website URL |
personal_phone | Personal phone number |
mobile_phone | Mobile phone number |
city | City |
state | State |
country | Country |
twitter | Twitter handle |
facebook | Facebook profile |
linkedin | LinkedIn profile |
tags | Tags to apply to the contact |
legal_bases | Legal bases for LGPD/GDPR compliance |
You must ensure the records in your input table have a column mapped to email, as it’s required by the RD Station API to identify contacts.
Deduplicate records with the same email in your input table before sending to the destination. RD Station has a limit of 24 updates per contact in a 24-hour period. Exceeding this limit will cause the API to block further requests to that contact.
| email | full_name | phone | company_city |
|---|
| alice@example.com | Alice Santos | +55 11 91234-5678 | São Paulo |
| bob@example.com | Bob Silva | +55 21 99876-5432 | Rio de Janeiro |
| carol@example.com | Carol Mendes | +55 31 98765-4321 | Belo Horizonte |
email → email, full_name → name, phone → mobile_phone, company_city → city.
Qualification Events mode
In qualification events mode, each row in your input table represents a contact qualification event to send to RD Station. This is used to move contacts through your sales funnel by marking them as opportunities, won sales, or lost opportunities.
Available destination fields:
| Destination field | Description |
|---|
email | Contact email address (required) |
event_type | Type of qualification event (required). Must be one of: OPPORTUNITY, SALE, OPPORTUNITY_LOST |
funnel_name | Name of the sales funnel (optional, defaults to default) |
reason | Reason for losing the opportunity (optional, only applied to OPPORTUNITY_LOST events) |
sale_amount | Monetary value of the sale (optional, only applied to SALE events) |
Both email and event_type are required for every record. Records missing either field will cause the pipeline to fail (unless partial success is enabled).
| contact_email | type | funnel |
|---|
| alice@example.com | OPPORTUNITY | Inbound |
| bob@example.com | OPPORTUNITY | Inbound |
| carol@example.com | OPPORTUNITY | Outbound |
contact_email → email, type → event_type, funnel → funnel_name.
Example input table (qualification events — sale):
Mark contacts as won deals with their sale amounts:
| contact_email | type | funnel | amount |
|---|
| alice@example.com | SALE | Inbound | 4500.00 |
| bob@example.com | SALE | Inbound | 12000.00 |
contact_email → email, type → event_type, funnel → funnel_name, amount → sale_amount.
Example input table (qualification events — lost):
Mark contacts as lost opportunities with a reason:
| contact_email | type | funnel | lost_reason |
|---|
| carol@example.com | OPPORTUNITY_LOST | Outbound | Chose a competitor |
| dave@example.com | OPPORTUNITY_LOST | Inbound | Budget constraints |
contact_email → email, type → event_type, funnel → funnel_name, lost_reason → reason.
Example input table (qualification events — mixed):
You can also send mixed event types in a single table:
| contact_email | type | funnel | lost_reason | amount |
|---|
| alice@example.com | OPPORTUNITY | Inbound | | |
| bob@example.com | SALE | Inbound | | 8500.00 |
| carol@example.com | OPPORTUNITY_LOST | Outbound | No budget | |
contact_email → email, type → event_type, funnel → funnel_name, lost_reason → reason, amount → sale_amount. Fields that don’t apply to a given event type (e.g. reason for a SALE row) are ignored.
-
Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
-
To define your Trigger, consider how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).
-
Click Done.
Check your new destination!
-
Once completed, you’ll receive confirmation that your new destination is set up!
-
You can view your new destination on the Destinations page. Now, for you to be able to see it on RD Station, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on RD Station.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!
