How to connect RD Station and ReachInbox
Create a New Scenario to Connect RD Station and ReachInbox
In the workspace, click the βCreate New Scenarioβ button.

Add the First Step
Add the first node β a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a RD Station, triggered by another scenario, or executed manually (for testing purposes). In most cases, RD Station or ReachInbox will be your first step. To do this, click "Choose an app," find RD Station or ReachInbox, and select the appropriate trigger to start the scenario.

Add the RD Station Node
Select the RD Station node from the app selection panel on the right.


RD Station

Configure the RD Station
Click on the RD Station node to configure it. You can modify the RD Station URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the ReachInbox Node
Next, click the plus (+) icon on the RD Station node, select ReachInbox from the list of available apps, and choose the action you need from the list of nodes within ReachInbox.


RD Station
β
ReachInbox

Authenticate ReachInbox
Now, click the ReachInbox node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your ReachInbox settings. Authentication allows you to use ReachInbox through Latenode.
Configure the RD Station and ReachInbox Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the RD Station and ReachInbox Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that donβt require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
β
AI Anthropic Claude 3
β
ReachInbox
Trigger on Webhook
β

RD Station
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring RD Station, ReachInbox, and any additional nodes, donβt forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking βRun onceβ and triggering an event to check if the RD Station and ReachInbox integration works as expected. Depending on your setup, data should flow between RD Station and ReachInbox (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect RD Station and ReachInbox
RD Station + ReachInbox + Google Sheets: When a new lead conversion occurs in RD Station, the lead's email is added to a specified campaign in ReachInbox. The details of this addition are then logged in a Google Sheets spreadsheet, including the campaign name and lead information.
ReachInbox + RD Station + Slack: When ReachInbox detects that a lead has been updated, the lead's status in RD Station is updated. A message is then sent to a Slack channel to alert the sales team about the updated lead.
RD Station and ReachInbox integration alternatives

About RD Station
Use RD Station in Latenode to automate marketing tasks. Update leads, trigger personalized emails, and track campaign performance, all inside automated workflows. Integrate RD Station data with other apps, enrich with AI, and build custom logic without code. Scale your marketing automation affordably and visually.
Related categories
About ReachInbox
ReachInbox + Latenode: Automate cold outreach & personalize follow-ups at scale. Trigger campaigns from new leads, scraped data, or CRM updates. Latenode manages complex logic (filtering, scheduling, AI content creation) while ReachInbox handles email sending. Optimize deliverability and engagement in automated workflows.
Similar apps
Related categories
See how Latenode works
FAQ RD Station and ReachInbox
How can I connect my RD Station account to ReachInbox using Latenode?
To connect your RD Station account to ReachInbox on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select RD Station and click on "Connect".
- Authenticate your RD Station and ReachInbox accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger ReachInbox campaigns from new RD Station leads?
Yes, you can! With Latenode, automatically trigger personalized ReachInbox campaigns when new leads are captured in RD Station, enhancing engagement and conversion rates effortlessly.
What types of tasks can I perform by integrating RD Station with ReachInbox?
Integrating RD Station with ReachInbox allows you to perform various tasks, including:
- Automatically adding new RD Station leads to ReachInbox contact lists.
- Sending SMS updates via ReachInbox for key RD Station lifecycle events.
- Creating personalized ReachInbox messages based on RD Station lead data.
- Updating RD Station lead information when a ReachInbox message is opened.
- Triggering internal notifications for high-value leads via ReachInbox SMS.
What RD Station data can I access within Latenode workflows?
You can access various RD Station data points including lead scores, custom fields, conversion events, and contact information to personalize automated workflows within Latenode.
Are there any limitations to the RD Station and ReachInbox integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by RD Station and ReachInbox APIs may affect high-volume workflows.
- Some advanced RD Station segmentation options may not be directly accessible.
- Complex ReachInbox template logic might require custom JavaScript within Latenode.