# How to connect Lexoffice to OpenClaw (paste one key, 41 tools) > Connect Lexoffice to OpenClaw with ClawLink: paste your Lexoffice key once and 41 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/lexoffice The usual route to Lexoffice access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Lexoffice setup: install one ClawHub skill, connect Lexoffice in the browser, and OpenClaw can call real Lexoffice actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Lexoffice. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Lexoffice** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect lexoffice # connect Lexoffice (browser OAuth) npx -y @useclawlink/cli actions lexoffice # list available actions npx -y @useclawlink/cli run lexoffice --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Lexoffice in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Lexoffice API key once. Verify the connection by asking OpenClaw: > Use Lexoffice to download file and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Lexoffice is connected in the dashboard, that agent calls the same 41 Lexoffice tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Lexoffice MCP for OpenClaw Looking for a Lexoffice MCP server for OpenClaw? ClawLink connects Lexoffice to OpenClaw and exposes 41 Lexoffice tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Lexoffice integration](https://claw-link.dev/hermes/lexoffice) works the same way. ## What the OpenClaw Lexoffice integration can do 41 Lexoffice tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 41. ### 30 of 41 Lexoffice tools for OpenClaw | Tool | What it does | |---|---| | **Download file** `lexoffice_download_file` | Download a file from lexoffice by its ID | | **Get article** `lexoffice_get_article` | Retrieve an article by ID from Lexoffice | | **Get contact** `lexoffice_get_contact` | Retrieve a specific contact by its ID | | **Get credit note** `lexoffice_get_credit_note` | Retrieve a credit note by its UUID from Lexoffice | | **Get credit note document** `lexoffice_get_credit_note_document` | Render a credit note document (PDF) | | **Get delivery note** `lexoffice_get_delivery_note` | Retrieve a specific delivery note from Lexoffice by its ID | | **Get dunning** `lexoffice_get_dunning` | Retrieve a dunning document by its ID | | **Get dunning document** `lexoffice_get_dunning_document` | Render and retrieve a dunning document (PDF) reference | | **Get event subscription** `lexoffice_get_event_subscription` | Retrieve a specific event subscription by its ID | | **Get invoice** `lexoffice_get_invoice` | Retrieve a specific invoice by its UUID | | **Get invoice document** `lexoffice_get_invoice_document` | Render an Invoice Document (PDF) by invoice ID | | **Get order confirmation** `lexoffice_get_order_confirmation` | Retrieve a specific order confirmation by its ID | | **Get order confirmation document** `lexoffice_get_order_confirmation_document` | Render an Order Confirmation Document as PDF | | **Get payment** `lexoffice_get_payment` | Retrieve payment information for a specific voucher (invoice or credit note) from Lexoffice | | **Get profile** `lexoffice_get_profile` | Retrieves the user and company profile information from Lexoffice | | **Get quotation** `lexoffice_get_quotation` | Retrieve a quotation by its ID | | **Get quotation document** `lexoffice_get_quotation_document` | Render a quotation document as a PDF file | | **Get voucher** `lexoffice_get_voucher` | Retrieve a specific voucher by its UUID | | **List articles** `lexoffice_list_articles` | List articles from Lexoffice using filters and pagination | | **List contacts** `lexoffice_list_contacts` | Retrieve all contacts from Lexoffice with optional filters | | **List countries** `lexoffice_list_countries` | Retrieve the list of all available countries with tax classifications from Lexoffice | | **List event subscriptions** `lexoffice_list_event_subscriptions` | Retrieve all event subscriptions for the current access token | | **List payment conditions** `lexoffice_list_payment_conditions` | Retrieve list of currently configured payment conditions from Lexoffice | | **List posting categories** `lexoffice_list_posting_categories` | Retrieve the list of posting categories for bookkeeping vouchers (revenue or expense) supported | | **List print layouts** `lexoffice_list_print_layouts` | Retrieve all print layouts for invoices and other documents | | **List recurring templates** `lexoffice_list_recurring_templates` | Retrieve all recurring templates from Lexoffice | | **List voucherlist** `lexoffice_list_voucherlist` | Retrieve voucherlist from Lexoffice including bookkeeping vouchers (salesinvoices | | **List vouchers** `lexoffice_list_vouchers` | Filter vouchers by voucher number from Lexoffice | | **Create article** `lexoffice_create_article` | Create a new article (product or service) in Lexoffice | | **Create contact** `lexoffice_create_contact` | Create a new contact (customer or vendor) in Lexoffice | ## Example prompts **Download File** > Use Lexoffice to download file and walk me through the result in plain English. **Get Article** > Pull the relevant data from Lexoffice, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Lexoffice, summarize it in plain English, and point out anything that needs attention. **Get Credit Note** > Pull the relevant data from Lexoffice, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Lexoffice working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Lexoffice API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lexoffice account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Lexoffice. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Lexoffice actions to the runtime in a format your agent can reliably use. | 41 tools for Lexoffice are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Lexoffice to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Lexoffice in the browser, and the 41 tools above work from chat. There is no SDK and no config file, and the Lexoffice key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Lexoffice skill but can't call the tools The ClawHub skill teaches OpenClaw about Lexoffice, but the calls run through the ClawLink plugin and your connected account. Make sure Lexoffice is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Lexoffice from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Lexoffice tools Lexoffice tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Lexoffice call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Lexoffice returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Lexoffice has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Lexoffice integration? Yes. ClawLink is the fastest way to connect OpenClaw to Lexoffice: link your Lexoffice account once in the browser and OpenClaw can call the Lexoffice API through 41 ready-made tools — no custom code or token handling. ### How do I add Lexoffice to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Lexoffice skill from ClawHub, then you click Connect in the dashboard to authorize Lexoffice. OpenClaw calls the tools from the next message — no config files, and the Lexoffice key you paste is stored server-side instead of in your environment. ### How long does it take to connect Lexoffice to OpenClaw? About two minutes. Sign in, click Connect next to Lexoffice in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Lexoffice up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Lexoffice working from chat. ### OpenClaw installed the Lexoffice skill but can't call the tools The ClawHub skill teaches OpenClaw about Lexoffice, but the calls run through the ClawLink plugin and your connected account. Make sure Lexoffice is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Zoho Books](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp tools](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts