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

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


Loyverse

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


Loyverse
β
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 Loyverse 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 Loyverse 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
β

Loyverse
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring Loyverse, 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 Loyverse and OpenPhone integration works as expected. Depending on your setup, data should flow between Loyverse 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 Loyverse and OpenPhone
Loyverse + OpenPhone + Slack: When a new receipt is created in Loyverse that exceeds a specified amount, a follow-up call is placed via OpenPhone. After the call, a message is sent to a designated Slack channel to notify a manager about the high-value transaction and the subsequent call.
OpenPhone + Loyverse + Google Sheets: When a call event is logged in OpenPhone, the flow retrieves corresponding transaction data from Loyverse using customer details extracted from the OpenPhone call. It then logs the OpenPhone call details along with the associated Loyverse transaction data into a Google Sheet for sales performance tracking.
Loyverse and OpenPhone integration alternatives

About Loyverse
Sync Loyverse sales data to your accounting or marketing tools using Latenode. Automate inventory updates based on Loyverse transactions. Trigger custom workflows for customer loyalty programs. Latenode lets you connect Loyverse data to any app without code, adding powerful automation to your POS system.
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 Loyverse and OpenPhone
How can I connect my Loyverse account to OpenPhone using Latenode?
To connect your Loyverse account to OpenPhone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Loyverse and click on "Connect".
- Authenticate your Loyverse and OpenPhone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically text new Loyverse customers using OpenPhone?
Yes, you can! Latenode's visual editor and advanced logic allow you to trigger OpenPhone texts when new customers are added in Loyverse, improving engagement.
What types of tasks can I perform by integrating Loyverse with OpenPhone?
Integrating Loyverse with OpenPhone allows you to perform various tasks, including:
- Send a welcome SMS to new Loyverse customers via OpenPhone.
- Log Loyverse sales data in OpenPhone contact notes.
- Create OpenPhone contacts from new Loyverse customer profiles.
- Send appointment reminders via OpenPhone based on Loyverse data.
- Notify staff via OpenPhone of large Loyverse transactions.
HowdoIaccessLoyversedataforcomplexcalculationswithinLatenode?
Use Latenode's JavaScript blocks to parse Loyverse data, perform calculations, and format it for OpenPhone automations.
Are there any limitations to the Loyverse and OpenPhone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Initial data sync might take time for very large Loyverse databases.
- Complex JavaScript transformations require programming knowledge.
- OpenPhone API rate limits may affect high-volume message sending.