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

Add the Follow Up Boss Node
Select the Follow Up Boss node from the app selection panel on the right.


Follow Up Boss

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


Follow Up Boss
⚙
OpenPhone

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

Follow Up Boss
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Follow Up Boss, OpenPhone, 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 Follow Up Boss and OpenPhone integration works as expected. Depending on your setup, data should flow between Follow Up Boss and OpenPhone (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Follow Up Boss and OpenPhone
OpenPhone + Follow Up Boss + Google Sheets: When a call is logged in OpenPhone, find the corresponding contact in Follow Up Boss and log the call details there. Then, add a summary of the call to a Google Sheet for reporting purposes.
OpenPhone + Follow Up Boss + Slack: When a call is logged in OpenPhone and linked to a lead in Follow Up Boss, this automation finds the lead in Follow Up Boss. Then, it sends a notification to a designated Slack channel informing the sales team about the call and the associated lead.
Follow Up Boss and OpenPhone integration alternatives

About Follow Up Boss
Sync Follow Up Boss with Latenode to automate lead management. Trigger custom actions based on lead stages or properties. Update FUB contacts from other apps, create tasks, or send automated follow-ups. Latenode adds flexible logic, data transformations, and multi-app workflows for smarter real estate automation.
Similar apps
Related categories
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
See how Latenode works
FAQ Follow Up Boss and OpenPhone
How can I connect my Follow Up Boss account to OpenPhone using Latenode?
To connect your Follow Up Boss account to OpenPhone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Follow Up Boss and click on "Connect".
- Authenticate your Follow Up Boss and OpenPhone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically log OpenPhone calls in Follow Up Boss?
Yes, you can! Latenode's visual editor makes this easy, logging call details as activities. This improves reporting and lead tracking, without manual data entry.
What types of tasks can I perform by integrating Follow Up Boss with OpenPhone?
Integrating Follow Up Boss with OpenPhone allows you to perform various tasks, including:
- Automatically creating Follow Up Boss leads from new OpenPhone contacts.
- Sending personalized SMS messages via OpenPhone when deals reach a stage.
- Updating Follow Up Boss deal notes with transcripts of OpenPhone calls.
- Triggering OpenPhone calls when a Follow Up Boss task is created or updated.
- Syncing Follow Up Boss contact information with OpenPhone's address book.
HowdoesLatenodehelpmemanagemultipleFollowUpBossaccounts?
Latenode supports multiple Follow Up Boss accounts, letting you build complex workflows that span different business units, with detailed activity logs.
Are there any limitations to the Follow Up Boss and OpenPhone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time sync depends on API availability and rate limits of both services.
- Deep customization may require JavaScript knowledge for advanced workflows.
- Large data transfers can impact performance, depending on plan specifications.