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

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

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

Creatomate
⚙

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

Save and Activate the Scenario
After configuring Creatomate, 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 Creatomate and Lexoffice integration works as expected. Depending on your setup, data should flow between Creatomate 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 Creatomate and Lexoffice
Creatomate + Lexoffice + Airtable: When a new render is completed in Creatomate, the project data is used to create a new invoice in Lexoffice. A record of the invoice is then created in Airtable for tracking purposes.
Lexoffice + Creatomate + Google Drive: When a new voucher is created in Lexoffice (assuming this represents invoice payment), Creatomate renders a thank you video. This video is then saved to Google Drive.
Creatomate and Lexoffice integration alternatives
About Creatomate
Automate video creation with Creatomate in Latenode. Generate personalized videos from data: product demos, social media content, or reports. Connect Creatomate to any data source and automate complex workflows with Latenode's visual editor, JavaScript support, and flexible API. Scale video production without manual effort.
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 Creatomate and Lexoffice
How can I connect my Creatomate account to Lexoffice using Latenode?
To connect your Creatomate account to Lexoffice on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Creatomate and click on "Connect".
- Authenticate your Creatomate and Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate invoice video creation for new Lexoffice clients?
Yes, you can! Latenode allows you to trigger Creatomate video generation upon new Lexoffice client creation. Automate personalized client outreach and enhance their onboarding experience.
What types of tasks can I perform by integrating Creatomate with Lexoffice?
Integrating Creatomate with Lexoffice allows you to perform various tasks, including:
- Automatically creating personalized video invoices upon new invoice generation.
- Generating video summaries of financial reports directly from Lexoffice data.
- Creating promotional videos using Lexoffice customer data.
- Automatically sending payment reminder videos created via Creatomate.
- Updating Creatomate video templates with new Lexoffice client information.
What Creatomate video parameters can Latenode control dynamically?
Latenode lets you dynamically control Creatomate templates, text, images, video clips, and audio using data from Lexoffice and other connected apps.
Are there any limitations to the Creatomate and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex video editing within Latenode requires JavaScript knowledge.
- The number of Creatomate videos you can generate depends on your Creatomate subscription.
- Lexoffice API limitations may restrict the frequency of data retrieval.