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

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

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

OpenPhone
⚙
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 OpenPhone 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 OpenPhone 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
⚙
OpenPhone
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring OpenPhone, 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 OpenPhone and Recruitee integration works as expected. Depending on your setup, data should flow between OpenPhone 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 OpenPhone and Recruitee
OpenPhone + Recruitee + Slack: When a new call event occurs in OpenPhone, the workflow searches for the candidate in Recruitee. If the candidate is found, a Slack message is sent with a link to their Recruitee profile. If the candidate is not found, a Slack message is sent to notify the team about a potential new candidate.
OpenPhone + Recruitee + Google Sheets: When a call ends in OpenPhone, the details are logged to a Google Sheet. The workflow then attempts to find the candidate in Recruitee and updates the profile with information about the call, if found.
OpenPhone and Recruitee integration alternatives
About OpenPhone
Use OpenPhone in Latenode to automate SMS and call workflows. Log activities, trigger actions based on call outcomes, and sync data to CRMs. By using Latenode, you orchestrate OpenPhone within complex workflows, adding logic and integrations not available in OpenPhone alone. Scale customer communication using no-code tools and AI.
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 OpenPhone and Recruitee
How can I connect my OpenPhone account to Recruitee using Latenode?
To connect your OpenPhone account to Recruitee on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select OpenPhone and click on "Connect".
- Authenticate your OpenPhone and Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically SMS new candidates using OpenPhone?
Yes, you can! Latenode lets you trigger SMS messages in OpenPhone when new candidates are added to Recruitee, instantly engaging top talent. Add custom logic or AI to personalize texts.
What types of tasks can I perform by integrating OpenPhone with Recruitee?
Integrating OpenPhone with Recruitee allows you to perform various tasks, including:
- Create new Recruitee candidates from OpenPhone call logs.
- Send SMS updates to candidates when their application status changes.
- Log OpenPhone calls and texts as activities on Recruitee profiles.
- Trigger OpenPhone calls when a candidate reaches a specific stage.
- Automatically update candidate details in Recruitee from OpenPhone.
Can I use custom JavaScript with my OpenPhone automations?
Yes! Latenode's JavaScript blocks allow you to manipulate data and create highly customized workflows beyond simple point-and-click integrations.
Are there any limitations to the OpenPhone and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require JavaScript coding.
- Real-time synchronization depends on API rate limits of both apps.
- The integration is limited to the data fields exposed by both APIs.