Skip to main content
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 three 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.
  • Conversion Events: sends conversions (e.g. a form answer or an NPS response) via the RD Station Events API, with standard and custom fields.

​
1. Add your RD Station Marketing access

  1. 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.
  2. 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.
      • Conversion Events: maps your input table columns to conversion fields, including custom fields, and registers one conversion per row in RD Station.
    • Enable partial success: Whether the connector should continue trying to sync records after one fails.
  3. Click Next.

​
2. Select your data to send

  1. 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.
  2. 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.

​
Contacts mode

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:
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.
Example input table (contacts mode): In this example, you would map: 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:
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).
Example input table (qualification events: opportunity): Send contacts as new opportunities in the “Inbound” funnel: Column mapping: contact_email → email, type → event_type, funnel → funnel_name. Example input table (qualification events: sale): Mark contacts as won deals with their sale amounts: Column mapping: 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: Column mapping: 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: Column mapping: 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.

​
Conversion Events mode

In conversion events mode, each row in your input table becomes one conversion in RD Station, shown with a trophy icon on the lead’s timeline. A conversion creates the lead if it doesn’t exist yet, updates its fields, and can be used to segment leads and as the entry point of automation flows. Use it for events such as form answers or NPS responses. Available destination fields: The conversion name usually doesn’t come from your data: add it as a column in the Query that builds your input table, e.g. 'NPS Wootric' AS conversion_identifier.
Each row sent becomes a new conversion, on every run. Destinations send the whole input table each time they run, and RD Station registers a conversion every time it receives one, which can trigger your automations again. Build the input table so it only holds the rows not sent yet, for example the answers received since the previous run, and align the destination’s trigger with that window.

​
Custom fields

Custom fields are mapped by their API identifier with the cf_ prefix, e.g. cf_nps_score. Find it in RD Station under Settings → Custom fields, and use it exactly as shown.
  • Values are sent as text. RD Station’s conversion API expects every field as text, so numbers are sent as text automatically (9 becomes "9"). The exceptions are tags and legal_bases (lists) and available_for_mailing (true/false).
  • Checkbox fields expect 1 (checked) or 0 (unchecked). Values of choice fields (combo box, radio button, multiple choice) must match one of the options configured in RD Station exactly.
RD Station ignores a custom field whose identifier doesn’t exist or whose value has the wrong format: the conversion is registered, but the field is left empty and no error is returned. After the first run, open a lead in RD Station and check that the custom fields were filled.
Example input table (conversion events: NPS responses): Column mapping: contact_email → email, conversion_identifier → conversion_identifier, score → cf_nps_score, comment → cf_nps_comment, answered_at → cf_nps_date.

​
Set up with the Nekt MCP

The column mapping in the app only lists standard fields, so a destination that maps custom fields (cf_...) is created through the Nekt MCP server. In an AI assistant connected to it, ask for the destination, for example:
Create an RD Station destination in conversion events mode from the table <layer>.<nps_table>, running daily at 8:00 (São Paulo time). Map contact_email → email, conversion_identifier → conversion_identifier, score → cf_nps_score, comment → cf_nps_comment.
The assistant creates a draft, gives you a link to authorize your RD Station account, and then completes the destination. The input table is identified by its id from the catalog listing (list_tables).
After it is created, the destination can be edited in the app, but a new cf_... field can’t be added there yet. To change the custom fields, create the destination again through the MCP.

​
Rejected conversions

When RD Station rejects a conversion, the run log names the field and the reason, e.g. cf_nps_score: Must be of type 'STRING'., and lists the affected contacts grouped by reason. With Enable partial success, the run continues past rejected rows and reports them as errors at the end. If RD Station rejects every row of a run, the run is marked as failed.

​
4. Configure your RD Station data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
  2. 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.).
  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!
  2. 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!