# How to connect Sevdesk to OpenClaw (paste one key, 115 tools) > Connect Sevdesk to OpenClaw with ClawLink: paste your Sevdesk key once and 115 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/sevdesk The usual route to Sevdesk 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 Sevdesk setup: install one ClawHub skill, connect Sevdesk in the browser, and OpenClaw can call real Sevdesk actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/sevdesk ## Setup It takes three steps to connect OpenClaw to Sevdesk. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Sevdesk** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 sevdesk # connect Sevdesk (browser OAuth) npx -y @useclawlink/cli actions sevdesk # list available actions npx -y @useclawlink/cli run sevdesk --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 Sevdesk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Sevdesk API key once. Verify the connection by asking OpenClaw: > Use Sevdesk to book invoice amount 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 Sevdesk is connected in the dashboard, that agent calls the same 115 Sevdesk 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). ## Sevdesk MCP for OpenClaw Looking for a Sevdesk MCP server for OpenClaw? ClawLink connects Sevdesk to OpenClaw and exposes 115 Sevdesk 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 Sevdesk integration](https://claw-link.dev/hermes/sevdesk) works the same way. ## What the OpenClaw Sevdesk integration can do 115 Sevdesk 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 115. ### 30 of 115 Sevdesk tools for OpenClaw | Tool | What it does | |---|---| | **Book invoice amount** `sevdesk_book_invoice_amount` | Book an invoice amount in SevDesk | | **Check customer number availability** `sevdesk_check_customer_number_availability` | Check if a customer number is available in sevDesk | | **Create accounting contact** `sevdesk_create_accounting_contact` | Create a new accounting contact in sevDesk | | **Create check account transaction** `sevdesk_create_check_account_transaction` | Create a new check account transaction in SevDesk | | **Create clearing account** `sevdesk_create_clearing_account` | Create a new clearing account in sevDesk | | **Export credit note CSV** `sevdesk_export_credit_note_csv` | Export credit notes as CSV from SevDesk | | **Fetch dictionary entries by type** `sevdesk_fetch_dictionary_entries_by_type` | Retrieve placeholders (dictionary entries) for a specific object type in sevDesk | | **Find contacts by custom field value** `sevdesk_find_contacts_by_custom_field_value` | Find contacts by custom field value | | **Generate progress download hash** `sevdesk_generate_progress_download_hash` | Generate a download hash for an export job progress | | **Get account invoices** `sevdesk_get_account_invoices` | Retrieves all sevDesk account invoices for the authenticated client | | **Get accounting contact by ID** `sevdesk_get_accounting_contact_by_id` | Retrieve accounting contact details by ID | | **Get accounting contacts** `sevdesk_get_accounting_contacts` | Retrieve accounting contacts from sevDesk | | **Get check account balance at date** `sevdesk_get_check_account_balance_at_date` | Get the balance of a check account at a specific date | | **Get check account by ID** `sevdesk_get_check_account_by_id` | Retrieve details of a specific check account by ID | | **Get check account transaction by ID** `sevdesk_get_check_account_transaction_by_id` | Retrieve a specific check account transaction by its ID | | **Get check account transactions** `sevdesk_get_check_account_transactions` | Retrieve list of check account transactions | | **Get check accounts** `sevdesk_get_check_accounts` | Retrieve a list of all check accounts | | **Get communication way keys** `sevdesk_get_communication_way_keys` | Retrieve a list of communication way keys from sevDesk | | **Get communication ways** `sevdesk_get_communication_ways` | Retrieve communication ways from sevDesk | | **Get communicationway by ID** `sevdesk_get_communicationway_by_id` | Retrieve details of a specific communication way by ID | | **Get contact address by ID** `sevdesk_get_contact_address_by_id` | Retrieve details of a specific contact address by ID | | **Get contact addresses** `sevdesk_get_contact_addresses` | Retrieve contact addresses from sevdesk | | **Get contact by ID** `sevdesk_get_contact_by_id` | Retrieve details of a specific contact by ID | | **Get contact custom field by ID** `sevdesk_get_contact_custom_field_by_id` | Retrieve a contact custom field by its ID | | **Get contact custom field setting by ID** `sevdesk_get_contact_custom_field_setting_by_id` | Retrieve details of a specific contact custom field setting by ID | | **Get contact custom field setting reference count** `sevdesk_get_contact_custom_field_setting_reference_count` | Receive the count of references for a contact custom field setting | | **Get contact custom field settings** `sevdesk_get_contact_custom_field_settings` | Retrieve contact custom field settings from sevDesk | | **Get contact custom fields** `sevdesk_get_contact_custom_fields` | Retrieve contact custom fields from sevDesk | | **Get contact tabs item count** `sevdesk_get_contact_tabs_item_count` | Get the count of items across all tabs for a specific contact | | **Get contacts** `sevdesk_get_contacts` | Retrieve a list of contacts | ## Example prompts **Book Invoice Amount** > Use Sevdesk to book invoice amount and walk me through the result in plain English. **Check Customer Number Availability** > Use Sevdesk to check customer number availability and walk me through the result in plain English. **Create Accounting Contact** > Create it in Sevdesk for me, then confirm the important fields before you finish. **Create Check Account Transaction** > Create it in Sevdesk for me, then confirm the important fields before you finish. ## 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 Sevdesk working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Sevdesk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Sevdesk 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 Sevdesk. | 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 Sevdesk actions to the runtime in a format your agent can reliably use. | 115 tools for Sevdesk are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Sevdesk 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 Sevdesk in the browser, and the 115 tools above work from chat. There is no SDK and no config file, and the Sevdesk 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 Sevdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Sevdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Sevdesk 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 Sevdesk 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 Sevdesk tools Sevdesk 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 Sevdesk 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. ### Sevdesk 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 Sevdesk has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Sevdesk integration? Yes. ClawLink is the fastest way to connect OpenClaw to Sevdesk: link your Sevdesk account once in the browser and OpenClaw can call the Sevdesk API through 115 ready-made tools — no custom code or token handling. ### How do I add Sevdesk to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Sevdesk skill from ClawHub, then you click Connect in the dashboard to authorize Sevdesk. OpenClaw calls the tools from the next message — no config files, and the Sevdesk key you paste is stored server-side instead of in your environment. ### How long does it take to connect Sevdesk to OpenClaw? About two minutes. Sign in, click Connect next to Sevdesk in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Sevdesk 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 Sevdesk working from chat. ### OpenClaw installed the Sevdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Sevdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Sevdesk 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 - [Zoho Books tools](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Zoho Invoice](https://claw-link.dev/openclaw/zoho-invoice) — Create and send invoices, track payments, and manage billing - [OpenClaw Square integration](https://claw-link.dev/openclaw/square) — Process payments and manage POS