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

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


Lexoffice

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


Lexoffice
⚙
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 Lexoffice 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 Lexoffice 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
⚙

Lexoffice
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Lexoffice, 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 Lexoffice and OpenPhone integration works as expected. Depending on your setup, data should flow between Lexoffice 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 Lexoffice and OpenPhone
Lexoffice + OpenPhone + Slack: When a new invoice is created in Lexoffice, send a text message via OpenPhone to the customer. Then, notify the finance team about the new invoice in a Slack channel.
OpenPhone + Lexoffice + Google Sheets: When a call ends in OpenPhone and a call summary is available, create a contact in Lexoffice using the caller's information, and then save the call data, including the call summary, to a new row in Google Sheets.
Lexoffice and OpenPhone integration alternatives

About Lexoffice
Automate accounting tasks by connecting Lexoffice to Latenode. Automatically create invoices, track expenses, or update customer data based on triggers from other apps. Latenode lets you build custom workflows around Lexoffice without code, adding features like advanced data validation or conditional logic that Lexoffice lacks natively.
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 Lexoffice and OpenPhone
How can I connect my Lexoffice account to OpenPhone using Latenode?
To connect your Lexoffice account to OpenPhone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Lexoffice and click on "Connect".
- Authenticate your Lexoffice and OpenPhone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update customer info in Lexoffice from OpenPhone?
Yes, with Latenode you can automatically update Lexoffice contacts from new OpenPhone call logs. Centralize data entry & use JavaScript blocks for advanced transformations.
What types of tasks can I perform by integrating Lexoffice with OpenPhone?
Integrating Lexoffice with OpenPhone allows you to perform various tasks, including:
- Create new Lexoffice customers from new OpenPhone contacts automatically.
- Log OpenPhone call details as notes on Lexoffice customer records.
- Send SMS confirmations via OpenPhone after a new Lexoffice invoice is created.
- Trigger OpenPhone calls when a Lexoffice payment is overdue.
- Update Lexoffice customer addresses based on OpenPhone contact updates.
Can I use custom fields from Lexoffice within OpenPhone messages on Latenode?
Yes, Latenode's data mapping and JavaScript functions allow you to use custom Lexoffice fields in personalized OpenPhone SMS messages.
Are there any limitations to the Lexoffice and OpenPhone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical data migration between Lexoffice and OpenPhone is not directly supported.
- Complex conditional logic may require JavaScript knowledge within Latenode.
- Rate limits of Lexoffice and OpenPhone APIs still apply through Latenode.