Resources · Make integration

Lexware Office Make integrationAutomate Lexware Office with Make.

Can Make handle your Lexware Office invoices, contacts and vouchers for you? The Lexware Office Make integration offers 17 modules, including 2 triggers. This guide is for anyone running the books who wants to link the account, build a first scenario and pick the right module.

Try the Lexware Office integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Lexware Office Make integration do?

The Lexware Office Make integration links your Lexware Office account to Make, a no-code tool where you build a scenario, meaning an automation made of modules. Each module is one brick: a trigger that starts things, an action that changes something, or a search that finds records. Together they move invoices, contacts and vouchers without copy and paste.

Keep your contact list in sync. When a deal is won in another tool, Search Contacts checks whether the customer already exists in Lexware Office, then Create a Contact or Update a Contact writes the right record. No duplicate customers, no retyping addresses.

Turn a receipt into a voucher. For a small agency collecting supplier bills, Create a Voucher records the expense and Upload a File to a Voucher attaches the scanned bill straight to it, so the bookkeeping entry and its proof live together.

Act on every new invoice. Watch Invoices spots each invoice created in Lexware Office, Get an Invoice reads its details, and Render an Invoice Document produces the file you can pass on to a shared folder or an email tool.

What the modules do not cover, the Make an API Call module can reach with the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you choose. For costs, see Make pricing, and if you prefer a guided path, Make training starts from scratch.

Connect

How do you connect Lexware Office to Make?

  1. 01

    Add a Lexware Office module

    Inside any scenario, add a Lexware Office module, for example Watch Invoices, and click Create a connection. A connection is your Lexware Office account linked to Make once, then reused by every Lexware Office module you add later.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off if you run more than one company. A label like the company name tells you at a glance which Lexware Office account a scenario writes to.

  3. 03

    Authorize and save

    Grant Make access on the Lexware Office page that opens, or paste the key Lexware Office gives you, then click Save. From that point, Make can list the contacts, vouchers and invoices it is allowed to read.

First scenario

Your first scenario with Lexware Office

GoalWhen a new invoice is created in Lexware Office, Make reads it and renders the invoice document.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. That first spot is where the trigger goes, the module that decides when everything starts.

  2. 02

    Add Watch Invoices

    Search for Lexware Office, pick Watch Invoices and select your connection, or click Create a connection if this is your first Lexware Office module.

  3. 03

    Read the invoice details

    Click the + on the right of the trigger and add Get an Invoice. Map the invoice from the previous module so Make fetches that exact invoice with all its details.

  4. 04

    Render the document

    Add Render an Invoice Document after it and map the same invoice. The module renders the invoice document and hands back a file ID that the next module in your chain can use.

  5. 05

    Test with Run once

    Create a test invoice in Lexware Office, then click Run once. Open the bubble above each module to read the bundles it received, a bundle being one item passed from module to module.

  6. 06

    Schedule and switch on

    Open the clock on the first module; a new scenario runs every 15 minutes by default. Keep that or adjust it within your plan, then switch the scenario on.

Triggers

What can start a Lexware Office scenario?

2 modules start a scenario when something happens in Lexware Office. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Lexware Office as soon as it happens.

Lexware Office1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an event occurs followed by the event type parameter.”

Watch Events starts your scenario the moment something happens in Lexware Office, for the event type you pick in the module. You get a reaction without waiting for the next scheduled check.

How it fires
instant, Lexware Office calls Make through a webhook as soon as it happens. This is the lightning badge on the module.
When to use it
pick it when a delay would hurt, for example when a follow-up must leave right after a change in your books.
Watch out
do not create the webhook yourself in Lexware Office; Make adds it automatically once you add and save this module in the scenario.
Lexware Office2Watch Invoices

Watch Invoices

Scheduled trigger

In Make“Triggers when a new invoice is created.”

Watch Invoices hands your scenario every new invoice created in Lexware Office, one bundle per invoice, ready for the next module to read or file away.

How it fires
scheduled, Make checks Lexware Office on the scenario's schedule. The clock badge shows it, and a new scenario checks every 15 minutes by default.
When to use it
choose it when invoices are the only thing you care about and a short wait between checks is fine, such as archiving each invoice after it is written.
Watch out
on the Free plan, checks cannot run closer than 15 minutes apart, so the scenario never reacts in the second an invoice appears.
Modules

What can Make do in Lexware Office?

Lexware Office gives you 15 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Document

2 modules
Lexware Office1

Upload a Document

Action

In Make“Uploads a document for bookkeeping purposes.”

Upload a Document sends a file into Lexware Office for bookkeeping, so a receipt caught elsewhere lands where your accountant looks for it.

When to use it
when scans arrive by email or in a cloud folder and you want them in Lexware Office without attaching them to a voucher yet.
Watch out
if the file belongs to a voucher you already have, Upload a File to a Voucher links it directly and saves a step.
Lexware Office2

Download a Document

Action

In Make“Downloads a document.”

Download a Document pulls a file out of Lexware Office into your scenario, so the next module can store it, send it or archive it.

When to use it
when a document stored in Lexware Office also has to reach a shared drive or a client portal.
Watch out
the file itself travels through Make, and the Free plan caps files at 5 MB, so large scans may need a paid plan.

Contact

4 modules
Lexware Office3

Search Contacts

Search

In Make“Searches for contacts by a filter parameter.”

Search Contacts finds the Lexware Office contacts that match a filter, which tells you whether a customer or supplier is already on file before you add anyone.

When to use it
right before Create a Contact, to avoid writing the same company twice.
Watch out
a search can return zero, one or several bundles; plan for the empty case and for several matches, or the next module runs once per result.
Lexware Office4

Get a Contact

Action

In Make“Gets a specified contact.”

Get a Contact reads one specific contact in full, giving later modules the name and details they need without a search.

When to use it
when an earlier module already hands you the contact, for instance a customer picked in your CRM, and you only need its complete record.
Watch out
it expects one precise contact; if all you have is a name or an email, start with Search Contacts instead.
Lexware Office5

Create a Contact

Action

In Make“Creates a new contact.”

Create a Contact adds a new customer or supplier to Lexware Office from data your scenario already holds, so nobody retypes it.

When to use it
when a signed quote, a web form or a new client in your CRM should become a Lexware Office contact ready to invoice.
Watch out
it always creates a fresh record; put Search Contacts in front of it, otherwise a returning customer ends up duplicated.
Lexware Office6

Update a Contact

Action

In Make“Updates an existing contact.”

Update a Contact changes an existing contact, which keeps an address or a company name correct in Lexware Office when it changes elsewhere.

When to use it
when your CRM is the place where the team edits customer data and Lexware Office should follow it.
Watch out
you need to point at the right contact, so pair it with Search Contacts or Get a Contact, and test with Run once before switching the scenario on.

Voucher

4 modules
Lexware Office7

Search Vouchers

Search

In Make“Retrieves a list of vouchers.”

Search Vouchers returns a list of vouchers from Lexware Office, handy for reviewing expenses and receipts outside the app.

When to use it
when a report, a spreadsheet or a check between two tools needs several vouchers at once.
Watch out
each voucher found becomes its own bundle and every module after it runs once per voucher, which adds up in operations, the unit Make counts on your plan.
Lexware Office8

List Voucher

SearchIn the docs only

List Voucher is a second voucher search that appears in the Make documentation only, without an official description, so what it returns is best read in a test.

When to use it
when Search Vouchers does not give you the view you expect and you want to compare the two in the editor.
Watch out
run it once with Run once and read its bundles before building on it, since nothing more is documented.
Lexware Office9

Create a Voucher

Action

In Make“Creates a new voucher.”

Create a Voucher records a new voucher in Lexware Office, turning a purchase or an expense spotted elsewhere into a bookkeeping entry.

When to use it
when a supplier bill reaches your inbox or an expense tool and should become a voucher without manual entry.
Watch out
the voucher is created empty of proof; chain Upload a File to a Voucher right after if the receipt has to travel with it.
Lexware Office10

Upload a File to a Voucher

Action

In Make“Uploads a file and assign it directly to a voucher.”

Upload a File to a Voucher sends a file and assigns it directly to a voucher, so the entry and its receipt sit together for whoever checks the books.

When to use it
right after Create a Voucher, or when a late receipt shows up for a voucher that already exists.
Watch out
the file passes through Make, and the Free plan limits files to 5 MB.

Invoice

2 modules
Lexware Office11

Get an Invoice

Action

In Make“Gets a specified invoice.”

Get an Invoice reads a single invoice from Lexware Office with its details, so every detail of that invoice is available to the modules further down the scenario.

When to use it
after Watch Invoices or Watch Events, when the next modules need more than what the trigger delivered.
Watch out
it reads one invoice you already know; it does not search, so map the invoice from an earlier module.
Lexware Office12

Render an Invoice Document

Action

In Make“Renders an invoice document to a file ID.”

Render an Invoice Document turns an invoice into its document and returns a file ID, the starting point for sending or archiving the invoice as a file.

When to use it
when a customer, a shared folder or your accountant should receive the invoice itself, not just its data.
Watch out
the module gives a file ID rather than the file; check with Run once what the bundle contains before choosing the next step.

Other

1 module
Lexware Office13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Nothing in the list fits? Make an API Call reaches any endpoint of the Lexware Office API from your scenario, with the connection you already set up.

When to use it
when the task you need has no ready-made module in this list, and the Lexware Office API offers it.
Watch out
you write the request yourself, so keep the API reference open. Anything the other modules already cover stays simpler with them.

Other modules

2 modules
Lexware Office14

Create an Invoice

Action

In Make“Creates a new invoice.”

Create an Invoice writes a new invoice in Lexware Office from data coming out of another tool, so billing starts without opening the app.

When to use it
when a closed deal, a paid order or a finished project should turn into an invoice for that customer.
Watch out
it writes a real invoice in your books. Try it on a test customer with Run once before switching the scenario on.
Lexware Office15

Get Vouchers by Voucher Number

Search

In Make“Searches for vouchers with a voucher number.”

Get Vouchers by Voucher Number looks up vouchers using their number, the quickest way to land on a known entry.

When to use it
when a supplier email, a bank line or a spreadsheet quotes a voucher number and you want the matching record in Lexware Office.
Watch out
like any search, it may return nothing, or several vouchers; test with Run once and check what the bundles hold before mapping them.
Need help

Need help automating Lexware Office with Make?

A person reads every message.

FAQ

Lexware Office Make integration: frequent questions

01Is the Lexware Office Make integration free?
Yes, Lexware Office is a standard app, so it works on the Free plan of Make. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. Your Lexware Office subscription is a separate matter.
02What do you need to connect Lexware Office to Make?
A Lexware Office account you can sign in to and a Make account. The documentation lists no other prerequisite. Add any Lexware Office module, click Create a connection, give it a name if you like, then authorize Make on the Lexware Office page or paste the key the app provides, and click Save. That single connection then serves every Lexware Office module in all your scenarios, so you do it once per account.
03Does the Lexware Office trigger react in real time?
It depends on the trigger. Watch Events is instant: Lexware Office calls Make through a webhook as soon as the event happens, and Make registers that webhook by itself once you save the module. Watch Invoices is scheduled: Make checks for new invoices on the scenario's schedule, every 15 minutes by default. On the Free plan the shortest gap is 15 minutes, on paid plans it is 1 minute. Pick Watch Events when speed matters.
04What if a Lexware Office module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Lexware Office API with the connection you already have, so a task without its own module is still possible, as long as the API offers it. You write the request yourself, which takes a look at the API reference. For contacts, vouchers, invoices and documents, the 17 listed modules are the simpler route and easier to hand over to a colleague later.
05Make or n8n for Lexware Office?
Both can work, so compare them on your own criteria. Make offers 17 Lexware Office modules, including an instant trigger and Make an API Call for the rest, and it runs on the Free plan as a standard app. The same app often has an n8n node as well. Check whether the modules you need exist on each side, then weigh how your team prefers to build and maintain its automations before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations