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

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

ReachInbox
Configure the ReachInbox
Click on the ReachInbox node to configure it. You can modify the ReachInbox 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 ReachInbox node, select Recruitee from the list of available apps, and choose the action you need from the list of nodes within Recruitee.

ReachInbox
⚙
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 ReachInbox 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 ReachInbox 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
⚙
ReachInbox
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring ReachInbox, 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 ReachInbox and Recruitee integration works as expected. Depending on your setup, data should flow between ReachInbox 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 ReachInbox and Recruitee
ReachInbox + Recruitee + Slack: When a new lead sends a message in ReachInbox, find the corresponding recruiter in Recruitee (based on candidate details) and send a Slack notification to them.
Recruitee + ReachInbox + Google Sheets: Whenever a candidate is created in Recruitee, their contact information is used to find the lead in ReachInbox and the outreach success data is then logged into a Google Sheet for performance tracking.
ReachInbox and Recruitee integration alternatives
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
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 ReachInbox and Recruitee
How can I connect my ReachInbox account to Recruitee using Latenode?
To connect your ReachInbox account to Recruitee on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select ReachInbox and click on "Connect".
- Authenticate your ReachInbox and Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate candidate follow-ups using ReachInbox and Recruitee integration?
Yes, you can! Latenode allows automated triggers so new Recruitee candidates instantly get personalized ReachInbox messages, boosting engagement and saving recruiter time.
What types of tasks can I perform by integrating ReachInbox with Recruitee?
Integrating ReachInbox with Recruitee allows you to perform various tasks, including:
- Automatically sending interview confirmations via ReachInbox to new Recruitee candidates.
- Updating Recruitee candidate profiles based on ReachInbox engagement metrics.
- Triggering personalized ReachInbox follow-ups when a Recruitee application is moved to a new stage.
- Creating Recruitee tasks based on ReachInbox message replies or interactions.
- Adding new qualified ReachInbox leads as candidates directly into Recruitee.
How secure is my ReachInbox data when using Latenode?
Latenode uses secure OAuth authentication and encrypts your data, ensuring the privacy of your ReachInbox information when integrating with Recruitee.
Are there any limitations to the ReachInbox and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require custom JavaScript code.
- Rate limits of ReachInbox and Recruitee APIs apply.
- Historical data migration between the two platforms requires separate handling.