How to connect Instantly and RD Station
Create a New Scenario to Connect Instantly and RD Station
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 Instantly, triggered by another scenario, or executed manually (for testing purposes). In most cases, Instantly or RD Station will be your first step. To do this, click "Choose an app," find Instantly or RD Station, and select the appropriate trigger to start the scenario.

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

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

Instantly
⚙

RD Station

Authenticate RD Station
Now, click the RD Station node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your RD Station settings. Authentication allows you to use RD Station through Latenode.
Configure the Instantly and RD Station 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 Instantly and RD Station 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
⚙

RD Station
Trigger on Webhook
⚙
Instantly
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Instantly, RD Station, 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 Instantly and RD Station integration works as expected. Depending on your setup, data should flow between Instantly and RD Station (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Instantly and RD Station
Instantly + RD Station + Google Sheets: When a new lead is created in Instantly, the lead data is sent to RD Station. Upon lead conversion in RD Station, the lead information, campaign details, and conversion status are logged in a Google Sheets spreadsheet for performance analysis.
RD Station + Instantly + Slack: When a new lead conversion occurs in RD Station, the flow checks if this lead originated from an Instantly email campaign. If the lead exists in Instantly, a notification is sent to a designated Slack channel, alerting the sales team about the successful lead conversion and providing relevant lead details.
Instantly and RD Station integration alternatives
About Instantly
Use Instantly in Latenode to automate email outreach at scale. Connect Instantly to your CRM, database, or lead sources and build automated sequences based on triggers. Enrich data and route responses using Latenode's visual editor and JS node for custom logic — all without per-step pricing limits.
Similar apps
Related categories

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.
Similar apps
Related categories
See how Latenode works
FAQ Instantly and RD Station
How can I connect my Instantly account to RD Station using Latenode?
To connect your Instantly account to RD Station on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Instantly and click on "Connect".
- Authenticate your Instantly and RD Station accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add new Instantly leads to RD Station?
Yes, you can! Latenode's visual editor makes it easy to automate lead synchronization, ensuring all Instantly leads are instantly added to your RD Station for efficient nurturing.
What types of tasks can I perform by integrating Instantly with RD Station?
Integrating Instantly with RD Station allows you to perform various tasks, including:
- Create RD Station contacts from new Instantly leads.
- Update RD Station contact information based on Instantly data.
- Trigger email sequences in RD Station for Instantly leads.
- Segment Instantly leads in RD Station based on campaign data.
- Track Instantly campaign performance within RD Station dashboards.
How can I filter leads from Instantly before sending them to RD Station?
Use Latenode's no-code filters or JavaScript blocks to precisely qualify Instantly leads before they’re sent to RD Station, maximizing lead quality.
Are there any limitations to the Instantly and RD Station integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits of the Instantly and RD Station APIs may apply.
- Custom field mapping might require advanced configuration.
- Historical data synchronization might require custom workflows.