# How to connect Debitura to OpenClaw (paste one key, 11 tools) > Connect Debitura to OpenClaw with ClawLink: paste your Debitura key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/debitura The usual route to Debitura 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 Debitura setup: install one ClawHub skill, connect Debitura in the browser, and OpenClaw can call real Debitura 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 Debitura. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Debitura** — 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 debitura # connect Debitura (browser OAuth) npx -y @useclawlink/cli actions debitura # list available actions npx -y @useclawlink/cli run debitura --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 Debitura in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Debitura API key once. Verify the connection by asking OpenClaw: > Use Debitura to check case eligibility 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 Debitura is connected in the dashboard, that agent calls the same 11 Debitura 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). ## Debitura MCP for OpenClaw Looking for a Debitura MCP server for OpenClaw? ClawLink connects Debitura to OpenClaw and exposes 11 Debitura 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 Debitura integration](https://claw-link.dev/hermes/debitura) works the same way. ## What the OpenClaw Debitura integration can do 11 Debitura tools are ready for OpenClaw once the account is connected. ### All 11 Debitura tools for OpenClaw | Tool | What it does | |---|---| | **Check case eligibility** `debitura_check_case_eligibility` | Check whether Debitura covers a proposed debtor jurisdiction and amount, returning the matched | | **Get case context** `debitura_get_case_context` | Get one case by Debitura ID, Debitura reference, or creditor reference | | **Get creditor status** `debitura_get_creditor_status` | Return the connected creditor profile together with debt-collection contract onboarding status | | **List divisions** `debitura_list_divisions` | List creditor divisions, optionally including archived divisions | | **List payments** `debitura_list_payments` | List payments across all creditor cases | | **List tasks** `debitura_list_tasks` | List the creditor's action-item work queue across cases | | **Preview case** `debitura_preview_case` | Preview collection eligibility, partner assignment, blocking signing actions, jurisdiction, and | | **Search cases** `debitura_search_cases` | Search the creditor's collection cases by lifecycle status, case IDs, debtor IDs, division IDs | | **Search coverage** `debitura_search_coverage` | Find Debitura collection coverage by exact jurisdiction ID or by filtering the canonical | | **Create division** `debitura_create_division` | Create a creditor division with its company, address, and office contact profile | | **Update division** `debitura_update_division` | Fully replace an existing creditor division's editable company, address, and office contact | ## Example prompts **Check Case Eligibility** > Use Debitura to check case eligibility and walk me through the result in plain English. **Get Case Context** > Pull the relevant data from Debitura, summarize it in plain English, and point out anything that needs attention. **Get Creditor Status** > Pull the relevant data from Debitura, summarize it in plain English, and point out anything that needs attention. **List Divisions** > List the relevant items in Debitura, group them by priority, and recommend what OpenClaw should do next. ## 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 Debitura working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Debitura API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Debitura 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 Debitura. | 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 Debitura actions to the runtime in a format your agent can reliably use. | 11 tools for Debitura are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Debitura 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 Debitura in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Debitura 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 Debitura skill but can't call the tools The ClawHub skill teaches OpenClaw about Debitura, but the calls run through the ClawLink plugin and your connected account. Make sure Debitura 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 Debitura 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 Debitura tools Debitura 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 Debitura 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. ### Debitura 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 Debitura has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Debitura integration? Yes. ClawLink is the fastest way to connect OpenClaw to Debitura: link your Debitura account once in the browser and OpenClaw can call the Debitura API through 11 ready-made tools — no custom code or token handling. ### How do I add Debitura to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Debitura skill from ClawHub, then you click Connect in the dashboard to authorize Debitura. OpenClaw calls the tools from the next message — no config files, and the Debitura key you paste is stored server-side instead of in your environment. ### How long does it take to connect Debitura to OpenClaw? About two minutes. Sign in, click Connect next to Debitura in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Debitura 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 Debitura working from chat. ### OpenClaw installed the Debitura skill but can't call the tools The ClawHub skill teaches OpenClaw about Debitura, but the calls run through the ClawLink plugin and your connected account. Make sure Debitura 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 - [OpenClaw HubSpot integration](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [OpenClaw CentralStationCRM integration](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows