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

OpenPhone
β

Lexoffice

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

Lexoffice
Trigger on Webhook
β
OpenPhone
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring OpenPhone, Lexoffice, 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 Lexoffice integration works as expected. Depending on your setup, data should flow between OpenPhone and Lexoffice (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 Lexoffice
OpenPhone + Lexoffice + Slack: When a new call event is recorded in OpenPhone, a new voucher is created in Lexoffice to track call costs. A summary of the call details and the Lexoffice voucher is then sent to a designated Slack channel.
Lexoffice + OpenPhone + HubSpot: When a new invoice is created in Lexoffice, a new contact is created (or updated) in HubSpot. Subsequently, a task engagement to call the contact is logged in OpenPhone.
OpenPhone and Lexoffice 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 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
See how Latenode works
FAQ OpenPhone and Lexoffice
How can I connect my OpenPhone account to Lexoffice using Latenode?
To connect your OpenPhone account to Lexoffice 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 Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Lexoffice invoices from OpenPhone calls?
Yes, you can! Latenode allows you to trigger invoice creation in Lexoffice based on OpenPhone call events. Automate accounting and save time with this powerful integration.
What types of tasks can I perform by integrating OpenPhone with Lexoffice?
Integrating OpenPhone with Lexoffice allows you to perform various tasks, including:
- Create new Lexoffice contacts from OpenPhone call recordings.
- Log OpenPhone call details as notes in Lexoffice customer profiles.
- Generate invoices in Lexoffice for billable OpenPhone support calls.
- Update Lexoffice customer data based on OpenPhone contact information.
- Send payment reminders via OpenPhone SMS for overdue Lexoffice invoices.
Can I use JavaScript to transform OpenPhone data before sending it to Lexoffice?
Yes! Latenode allows you to use JavaScript code blocks to manipulate OpenPhone data, ensuring seamless and customized integration with Lexoffice.
Are there any limitations to the OpenPhone and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical OpenPhone data prior to integration setup isn't automatically synced.
- Complex data transformations might require advanced JavaScript knowledge.
- The number of tasks per month depends on your Latenode subscription plan.