How to connect RD Station and Recruitee
Create a New Scenario to Connect RD Station and Recruitee
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 Recruitee will be your first step. To do this, click "Choose an app," find RD Station or Recruitee, 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 Recruitee Node
Next, click the plus (+) icon on the RD Station node, select Recruitee from the list of available apps, and choose the action you need from the list of nodes within Recruitee.


RD Station
β
Recruitee

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

RD Station
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring RD Station, Recruitee, 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 Recruitee integration works as expected. Depending on your setup, data should flow between RD Station and Recruitee (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 Recruitee
RD Station + Recruitee + Slack: When a new opportunity is created in RD Station, a candidate profile is automatically created in Recruitee. Subsequently, a notification is sent via Slack to the hiring manager, informing them about the new candidate profile created from the RD Station opportunity.
Recruitee + RD Station + Google Sheets: When a candidate is hired in Recruitee, their information is added to RD Station as a new lead conversion, and a new row is added to a Google Sheets spreadsheet to track the hiring data.
RD Station and Recruitee 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 Recruitee
Automate your hiring process with Recruitee in Latenode. Trigger workflows on new applications to screen candidates, send automated messages, and update other systems. Connect Recruitee to HR tools for seamless data flow and custom talent pipelines. Simplify recruiting tasks using Latenode's visual editor and scaling options.
Related categories
See how Latenode works
FAQ RD Station and Recruitee
How can I connect my RD Station account to Recruitee using Latenode?
To connect your RD Station account to Recruitee 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 Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update candidate info in RD Station?
Yes, you can! Latenode's flexible data mapping ensures seamless updates, enriching your RD Station leads with Recruitee data for targeted marketing campaigns.
What types of tasks can I perform by integrating RD Station with Recruitee?
Integrating RD Station with Recruitee allows you to perform various tasks, including:
- Add new Recruitee candidates as leads in RD Station.
- Update RD Station lead information based on Recruitee activity.
- Trigger RD Station marketing automations upon candidate status changes.
- Sync contact details between RD Station and Recruitee profiles.
- Analyze recruitment campaign performance using RD Station data.
Can I use JavaScript to transform data between RD Station?
Yes! Latenode supports custom JavaScript code, letting you tailor data transformations beyond basic field mapping for complex requirements.
Are there any limitations to the RD Station and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require advanced JavaScript knowledge.
- Real-time data synchronization depends on the API rate limits of RD Station and Recruitee.
- Custom fields need to be manually mapped during the workflow setup.