---
title: "Connect Lexware Office and Lokalise - APIANT.ai"
description: "When \"Contact updated (instant)\" fires in Lexware Office, your agent runs \"Create a Task\" in Lokalise."
canonical: "https://apiant.ai/connect/lexware-office-to-lokalise"
---

# Connect Lexware Office and Lokalise

When **Contact updated (instant)** fires in [Lexware Office](https://apiant.ai/connections/lexware-office), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Create a contact** in Lexware Office. Describe the whole flow and it is built, tested on every scenario and kept running.

Lexware Office **10** triggers Lexware Office **40** actions Lokalise **16** triggers Lokalise **26** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Lexware Office and Lokalise to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Lexware Office and Lokalise can do together

### From Lexware Office to Lokalise

- When **Contact updated (instant)** in Lexware Office then **Create a Task** in Lokalise
- When **Invoice status changed (instant)** in Lexware Office then **Create Comment** in Lokalise

### From Lokalise to Lexware Office

- When **Contributor Added** in Lokalise then **Create a contact** in Lexware Office
- When **Key Added** in Lokalise then **Create an invoice** in Lexware Office

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Lexware Office and Lokalise

## Triggers and actions 26 triggers · 66 actions

- Trigger

**Contact updated (instant)**

Fires when a contact changes in Lexware Office. Event type: contact.changed.

- Trigger

**Invoice status changed (instant)**

Fires when an invoice's status changes in Lexware Office. Event type: invoice.status.changed.

- Trigger

**New article (instant)**

Fires when a new article is created in Lexware Office. Event type: article.created.

- Trigger

**New contact (instant)**

Fires when a new contact is created in Lexware Office. Event type: contact.created.

- Trigger

**New credit note (instant)**

Fires when a new credit note is created in Lexware Office. Event type: credit-note.created.

- Trigger

**New invoice (instant)**

Fires when a new invoice is created in Lexware Office. Event type: invoice.created.

- Trigger

**New order confirmation (instant)**

Fires when a new order confirmation is created in Lexware Office. Event type: order-confirmation.created.

- Trigger

**New quotation (instant)**

Fires when a new quotation is created in Lexware Office. Event type: quotation.created.

- Trigger

**New voucher (instant)**

Fires when a new bookkeeping voucher is created in Lexware Office. Event type: voucher.created.

- Trigger

**Payment changed (instant)**

Fires when the payment status of a sales voucher changes in Lexware Office. Event type: payment.changed.

- Action

**Create a contact**

Creates a contact in Lexware Office as a person or a company, with optional billing address, email, phone and note, and returns the new contact's ID.

- Action

**Create a credit note**

Creates a credit note in Lexware Office for an existing contact or a typed-in address, with your line items. Saves it as a draft unless you choose to finalize it.

- Action

**Create a delivery note**

Creates a delivery note in Lexware Office for an existing contact or a typed-in address, with your delivered line items. Saves it as a draft unless you choose to finalize it.

- Action

**Create a dunning**

Creates a dunning (payment reminder) in Lexware Office, normally chasing an unpaid invoice. Saves it as a draft unless you choose to finalize it.

- Action

**Create an article**

Creates a product or service article in Lexware Office with its unit, price and tax rate, and returns the new article's ID.

- Action

**Create an invoice**

Creates an invoice in Lexware Office for an existing contact or a typed-in address, with your line items and payment terms. Saves it as a draft unless you choose to finalize it.

- Action

**Create an order confirmation**

Creates an order confirmation in Lexware Office for an existing contact or a typed-in address, with your confirmed line items. Saves it as a draft unless you choose to finalize it.

- Action

**Create a quotation**

Creates a quotation in Lexware Office for an existing contact or a typed-in address, with your quoted line items and an expiry date. Saves it as a draft unless you choose to finalize it.

- Action

**Create a voucher**

Books a voucher (an incoming or outgoing document) into Lexware Office with its booking lines, and returns the new voucher's ID.

- Action

**Delete an article**

Deletes an article from Lexware Office by its ID.

- Action

**Download a credit note file**

Returns the PDF file ID and download URL for a finalized credit note in Lexware Office.

- Action

**Download a delivery note file**

Returns the PDF file ID and download URL for a finalized delivery note in Lexware Office.

- Action

**Download a dunning file**

Returns the PDF file ID and download URL for a finalized dunning in Lexware Office.

- Action

**Download a file**

Downloads the actual bytes of a file stored in Lexware Office by its file ID — for example the PDF that "Download an invoice file" reports. Returns the file so a later step can email, upload or attach it.

- Action

**Download an invoice file**

Returns the PDF file ID and download URL for a finalized invoice in Lexware Office.

- Action

**Download an order confirmation file**

Returns the PDF file ID and download URL for a finalized order confirmation in Lexware Office.

- Action

**Download a quotation file**

Returns the PDF file ID and download URL for a finalized quotation in Lexware Office.

- Action

**Find articles**

Searches the Lexware Office article list by article number, barcode or type, and returns the matching articles a page at a time.

- Action

**Find contacts**

Searches Lexware Office contacts by email, name, number or role, and returns the matching contacts a page at a time.

- Action

**Find voucher list**

Lists Lexware Office documents (invoices, credit notes, quotations and the rest) filtered by type, status, contact and date, a page at a time.

- Action

**Find vouchers**

Finds booked vouchers in Lexware Office by their document number and returns the full voucher records.

- Action

**Get a contact**

Returns one Lexware Office contact by its ID, with its roles, person or company details, addresses, emails and phone numbers.

- Action

**Get a credit note**

Returns one Lexware Office credit note by its ID, with its recipient, line items, totals and status.

- Action

**Get a delivery note**

Returns one Lexware Office delivery note by its ID, with its recipient, delivered lines and delivery date.

- Action

**Get a dunning**

Returns a single dunning (payment reminder) by its ID, including its addressee, line items, totals and PDF file reference.

- Action

**Get an article**

Returns a single article (product or service) by its ID, including its name, article number, unit and pricing.

- Action

**Get an invoice**

Returns a single invoice by its ID, including its addressee, line items, totals, payment terms and PDF file reference.

- Action

**Get an order confirmation**

Returns a single order confirmation by its ID, including its addressee, line items, totals and PDF file reference.

- Action

**Get a quotation**

Returns a single quotation by its ID, including its addressee, line items, totals, expiry date and PDF file reference.

- Action

**Get a voucher**

Returns a single bookkeeping voucher by its ID, including its type, contact, amounts, line items and attached files.

- Action

**Get payment information**

Returns the payment status of a voucher, such as an invoice: how much is still open, when it was paid, and the individual payments booked against it.

- Action

**Pursue to a credit note**

Creates a credit note that follows on from an existing invoice, linking the two in Lexware Office. Copies the invoice's recipient, lines and tax settings unless you supply your own lines.

- Action

**Pursue to a delivery note**

Creates a delivery note that follows on from an existing order confirmation, linking the two in Lexware Office. Copies the recipient, lines and tax settings unless you supply your own lines.

- Action

**Pursue to a dunning**

Creates a dunning (payment reminder) that follows on from an unpaid invoice, linking the two in Lexware Office. Copies the recipient, lines and tax settings unless you supply your own lines.

- Action

**Pursue to an invoice**

Creates an invoice that follows on from an existing order confirmation, linking the two in Lexware Office. Copies the recipient, lines and tax settings unless you supply your own lines.

- Action

**Pursue to an order confirmation**

Creates an order confirmation that follows on from an existing quotation, linking the two in Lexware Office. Copies the recipient, lines and tax settings unless you supply your own lines.

- Action

**Update a contact**

Updates an existing contact in Lexware Office. Reads the contact first and changes only the details you fill in, leaving everything else as it was.

- Action

**Update an article**

Updates an existing article in Lexware Office. Reads the article first and changes only the details you fill in, leaving everything else as it was.

- Action

**Update a voucher**

Updates an existing bookkeeping voucher in Lexware Office. Reads the voucher first and changes only the details you fill in, leaving everything else as it was.

- Action

**Upload Document for Bookkeeping Purposes**

Uploads a receipt or other document to Lexware Office for bookkeeping and returns its file ID, which you can attach to a voucher.

- Trigger

**Contributor Added**

Triggers when a new contributor is added to a Lokalise project.

- Trigger

**Contributor Removed**

Triggers when a contributor is removed from the selected Lokalise project.

- Trigger

**Key Added**

Triggers when a new translation key is added to a Lokalise project, whether individually or in bulk (import, API or bulk action). Fires once per added key.

- Trigger

**Key Comment Added**

Triggers when someone adds a comment to a translation key in a Lokalise project.

- Trigger

**Key Modified**

Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).

- Trigger

**Key Removed**

Triggers when one or more translation keys are removed from a Lokalise project, whether deleted individually, in bulk, through the API, or moved to another project. Fires once per removed key.

- Trigger

**Language Added**

Triggers when one or more languages are added to a Lokalise project, firing once for each language added.

- Trigger

**Language Removed**

Triggers when a language is removed from a Lokalise project.

- Trigger

**Poll Tasks**

Triggers when a new task is created in a Lokalise project.

- Trigger

**Project Exported**

Triggers when translation files are downloaded (exported) from a Lokalise project.

- Trigger

**Project Imported**

Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.

- Trigger

**Project Snapshot**

Triggers when a snapshot is taken of the selected Lokalise project.

- Trigger

**Task Created**

Triggers when a new translation or review task is created in a Lokalise project.

- Trigger

**Task Deleted**

Triggers when a task is deleted in a Lokalise project.

- Trigger

**Translation Reviewed**

Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.

- Trigger

**Translation Updated**

Triggers when a translation is changed in the selected Lokalise project, either one at a time or several at once through a bulk action, file upload or the API.

- Action

**Add Contributor**

Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.

- Action

**Add Languages**

Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.

- Action

**Create a Key**

Creates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key.

- Action

**Create a Task**

Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.

- Action

**Create Comment**

Adds a comment to a translation key in a Lokalise project.

- Action

**Create Project**

Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.

- Action

**Create Snapshot**

Creates a snapshot of a Lokalise project, saving its current state so it can be restored later.

- Action

**Delete a Key**

Deletes a key, with its translations, from a Lokalise project.

- Action

**Delete a Language**

Removes a language from a Lokalise project.

- Action

**Delete a Task**

Deletes a task from a Lokalise project.

- Action

**Download Files**

Exports a Lokalise project's translation files as a.zip bundle and returns the download URL of the bundle.

- Action

**List All Orders**

Returns all translation orders placed under a Lokalise team.

- Action

**List All Tasks**

Returns the tasks in a Lokalise project, optionally filtered by title or status.

- Action

**List All Translations**

Returns the translation items of a Lokalise project (one row per key and language), optionally filtered by language, review status, QA issues or task.

- Action

**List Project Languages**

Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.

- Action

**List Snapshots**

Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.

- Action

**Remove Contributor**

Removes a contributor from a Lokalise project.

- Action

**Retrieve a Comment**

Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added.

- Action

**Retrieve a Contributor**

Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.

- Action

**Retrieve a Key**

Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.

- Action

**Retrieve a Task**

Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.

- Action

**Retrieve Project**

Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics.

- Action

**Update a Key**

Updates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key.

- Action

**Update a Translation**

Updates the text and review flags of a translation in a Lokalise project.

- Action

**Update Language**

Updates a language in a Lokalise project, changing its code, name or plural forms.

- Action

**Upload File**

Uploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status.

## Each app on its own

- [ **Lexware Office** Lexware Office is a cloud app for german accounting.](https://apiant.ai/connections/lexware-office)
- [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise)

Reviews

## What our customers say

## More from Lexware Office

- [ **Lexware Office to Base44** Base44 is a platform that allows non-technical people to build their own Apps using AI.](https://apiant.ai/connect/lexware-office-to-base44)
- [ **Lexware Office to Browserless** Browserless allows you to run Chrome instances in the cloud for Data Extraction, Automation, PDF &...](https://apiant.ai/connect/lexware-office-to-browserless)
- [ **Lexware Office to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/lexware-office-to-salesforce)
- [ **Lexware Office to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/lexware-office-to-slack)
- [ **Lexware Office to Google Sheets** Google Sheets](https://apiant.ai/connect/lexware-office-to-google-sheets)
- [ **Lexware Office to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/lexware-office-to-gmail)

## More into Lokalise

- [ **HubSpot to Lokalise** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-lokalise)
- [ **Google Sheets to Lokalise** Google Sheets](https://apiant.ai/connect/google-sheets-to-lokalise)
- [ **Gmail to Lokalise** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-lokalise)
- [ **Google Calendar to Lokalise** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-lokalise)
- [ **Google Drive to Lokalise** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-lokalise)
- [ **ActiveCampaign to Lokalise** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-lokalise)

Questions

## Lexware Office and Lokalise, answered

###

### What can start an automation from Lexware Office?

Any of Lexware Office's 10 triggers in the catalog, including Contact updated (instant), Invoice status changed (instant), New article (instant) and New contact (instant). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Lokalise when something happens in Lexware Office?

Any of Lokalise's 26 actions, including Create a Key, Create a Task, Create Comment and Create Project. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Lokalise to Lexware Office?

Yes. When something happens in Lokalise, your agent can act in Lexware Office too. This page covers both directions: Lokalise's triggers and Lexware Office's actions are listed here as well.

###

### Do I have to build a connector for Lexware Office or Lokalise?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Lexware Office and Lokalise without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
