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


Lexoffice
⚙
Microsoft Outlook

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

Lexoffice
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Lexoffice, Microsoft Outlook, 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 Microsoft Outlook integration works as expected. Depending on your setup, data should flow between Lexoffice and Microsoft Outlook (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 Microsoft Outlook
Lexoffice + Microsoft Outlook + Google Calendar: When a new voucher is created in Lexoffice, create an event in Google Calendar via Microsoft Outlook to remind users to track payments.
Microsoft Outlook + Lexoffice + Slack: When a new message is sent via Outlook, check if it creates a voucher in Lexoffice. Then, a Slack notification informs the team about new Lexoffice invoices.
Lexoffice and Microsoft Outlook 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 Microsoft Outlook
Automate email tasks with Microsoft Outlook in Latenode. Send personalized emails, track replies, or create calendar events based on triggers from other apps. Latenode lets you integrate Outlook with your CRM, database, or other tools in visual workflows. Manage email flow without manual work, customize it with code, and scale it on demand.
Similar apps
Related categories
See how Latenode works
FAQ Lexoffice and Microsoft Outlook
How can I connect my Lexoffice account to Microsoft Outlook using Latenode?
To connect your Lexoffice account to Microsoft Outlook 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 Microsoft Outlook accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Outlook calendar events from Lexoffice invoices?
Yes, you can! Latenode allows you to automate this, instantly creating calendar entries for payment deadlines. Never miss a payment deadline again.
What types of tasks can I perform by integrating Lexoffice with Microsoft Outlook?
Integrating Lexoffice with Microsoft Outlook allows you to perform various tasks, including:
- Automatically saving new Lexoffice contacts to Outlook.
- Sending payment reminders from Outlook for Lexoffice invoices.
- Creating Lexoffice invoices from Outlook email requests.
- Tracking invoice status changes in Outlook.
- Generating daily financial reports in Outlook from Lexoffice data.
Can I use JavaScript to transform data between Lexoffice and Outlook?
Yes! Latenode supports JavaScript code blocks, letting you customize data transformations beyond simple field mapping for complex integrations.
Are there any limitations to the Lexoffice and Microsoft Outlook integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Attachment size limits are subject to Lexoffice and Outlook API restrictions.
- Custom field mappings might require JavaScript coding.
- Real-time synchronization depends on the polling frequency.