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

OpenPhone
⚙

SendPulse

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

SendPulse
Trigger on Webhook
⚙
OpenPhone
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring OpenPhone, SendPulse, 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 SendPulse integration works as expected. Depending on your setup, data should flow between OpenPhone and SendPulse (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 SendPulse
OpenPhone + HubSpot + SendPulse: When a new call event is recorded in OpenPhone, the automation checks if the contact exists in HubSpot. If not, it creates or updates the contact, then sends a personalized welcome SMS via SendPulse.
SendPulse + OpenPhone + Airtable: When a subscriber event occurs in SendPulse (e.g., campaign engagement), trigger a follow-up call via OpenPhone to the subscriber. Log the details of the call, including duration and outcome, in an Airtable base.
OpenPhone and SendPulse 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 SendPulse
Use SendPulse in Latenode for automated email & SMS marketing. Trigger campaigns based on real-time events, segment contacts dynamically, and personalize messages using data from any app. Automate list cleaning and optimize send times in response to user behavior. Connect SendPulse to any data source for smarter, event-driven communication workflows.
Related categories
See how Latenode works
FAQ OpenPhone and SendPulse
How can I connect my OpenPhone account to SendPulse using Latenode?
To connect your OpenPhone account to SendPulse 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 SendPulse accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate SMS campaign triggers from new OpenPhone calls?
Yes, you can! Latenode allows you to trigger SendPulse SMS campaigns based on OpenPhone call events. Automate follow-ups, boosting engagement & saving you time with no-code logic.
What types of tasks can I perform by integrating OpenPhone with SendPulse?
Integrating OpenPhone with SendPulse allows you to perform various tasks, including:
- Add new OpenPhone contacts to a SendPulse mailing list.
- Send SMS via SendPulse when a new OpenPhone call ends.
- Update contact details in SendPulse from OpenPhone call logs.
- Create new SendPulse subscribers from OpenPhone missed calls.
- Trigger personalized email sequences based on OpenPhone call tags.
Can I use JavaScript to enhance my OpenPhone automations?
Yes, Latenode allows you to use JavaScript code for complex data transformations within your OpenPhone workflows, creating highly customized solutions.
Are there any limitations to the OpenPhone and SendPulse integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time data synchronization depends on the APIs of both services.
- Complex logic may require JavaScript knowledge for advanced customization.
- Large data volumes may affect performance; consider optimizing workflows.