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


Lexoffice
⚙
Captions

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

Lexoffice
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Lexoffice, Captions, 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 Captions integration works as expected. Depending on your setup, data should flow between Lexoffice and Captions (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 Captions
Lexoffice + Captions + Slack: When a new voucher is created in Lexoffice, the system checks if a corresponding sales call recording exists in Captions. If found, a message is sent to a designated Slack channel with a link to the recording for team review.
Captions + Lexoffice + Google Drive: When a new video is generated in Captions, the system uploads the file to Google Drive. Afterwards, the system uploads the file to a specific voucher in Lexoffice using the document ID. This creates a record of sales call recordings.
Lexoffice and Captions 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 Captions
Need accurate, automated captions for videos? Integrate Captions with Latenode to generate and sync subtitles across platforms. Automate video accessibility for marketing, training, or support. Latenode adds scheduling, file handling, and error control to Captions, making scalable captioning workflows simple and efficient.
Related categories
See how Latenode works
FAQ Lexoffice and Captions
How can I connect my Lexoffice account to Captions using Latenode?
To connect your Lexoffice account to Captions 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 Captions accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create invoices from new Captions projects?
Yes, you can! Latenode enables automated workflows, instantly creating Lexoffice invoices for new Captions projects. Enjoy seamless project billing and save valuable time.
What types of tasks can I perform by integrating Lexoffice with Captions?
Integrating Lexoffice with Captions allows you to perform various tasks, including:
- Create Lexoffice invoices from completed Captions projects automatically.
- Update customer information in Lexoffice based on Captions project details.
- Send payment reminders for Lexoffice invoices via Captions video messages.
- Generate financial reports in Lexoffice based on Captions usage data.
- Trigger Captions video creation upon payment of Lexoffice invoices.
What Lexoffice data can I access within Latenode workflows?
You can access customer details, invoice information, product lists, and payment statuses directly within Latenode.
Are there any limitations to the Lexoffice and Captions integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Lexoffice invoice customizations may require custom JavaScript code.
- Real-time synchronization depends on Lexoffice and Captions API availability.
- Initial setup requires understanding of both Lexoffice and Captions data structures.