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

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

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

ReachInbox
⚙

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 ReachInbox 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 ReachInbox 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
⚙
ReachInbox
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring ReachInbox, 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 ReachInbox and Lexoffice integration works as expected. Depending on your setup, data should flow between ReachInbox 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 ReachInbox and Lexoffice
ReachInbox + Lexoffice + Slack: When a new lead is added in ReachInbox, a new voucher is created in Lexoffice and a notification is sent to a Slack channel.
Lexoffice + ReachInbox + Pipedrive: When a voucher's payment fails in Lexoffice (simulated by a custom trigger), a task is created in ReachInbox to follow up with the customer and the corresponding deal is updated in Pipedrive.
ReachInbox and Lexoffice integration alternatives
About ReachInbox
ReachInbox + Latenode: Automate cold outreach & personalize follow-ups at scale. Trigger campaigns from new leads, scraped data, or CRM updates. Latenode manages complex logic (filtering, scheduling, AI content creation) while ReachInbox handles email sending. Optimize deliverability and engagement in automated workflows.
Similar apps
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 ReachInbox and Lexoffice
How can I connect my ReachInbox account to Lexoffice using Latenode?
To connect your ReachInbox account to Lexoffice on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select ReachInbox and click on "Connect".
- Authenticate your ReachInbox and Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Lexoffice invoices from new ReachInbox leads?
Yes! Latenode lets you automate invoice creation from ReachInbox leads, saving time. Use our visual editor and JavaScript blocks to customize data transformations for perfect invoice details.
What types of tasks can I perform by integrating ReachInbox with Lexoffice?
Integrating ReachInbox with Lexoffice allows you to perform various tasks, including:
- Create new Lexoffice customers from new ReachInbox contacts.
- Update customer information in Lexoffice based on ReachInbox data.
- Generate invoices in Lexoffice for successfully closed deals in ReachInbox.
- Track invoice payments in Lexoffice and update deal status in ReachInbox.
- Send payment reminders via ReachInbox based on Lexoffice invoice due dates.
Can I use JavaScript to customize ReachInbox data before it reaches Lexoffice?
Yes, Latenode’s JavaScript blocks allow for powerful data transformations. Clean, format, and enrich ReachInbox data for accurate Lexoffice entries every time.
Are there any limitations to the ReachInbox and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript knowledge.
- Real-time synchronization depends on the API limits of both ReachInbox and Lexoffice.
- Custom field mappings beyond standard fields might require advanced configuration.