How to connect Debitura to Hermes Agent
Connect Debitura to Hermes with ClawLink: paste your Debitura key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.


Debitura helps creditors manage debt collection cases, coverage, payments, divisions, tasks, and webhooks through its Customer API.. Once connected, Hermes Agent can read and act on Debitura from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Debitura access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Debitura setup: pair once in the browser and your always-on Hermes agent can act on Debitura for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Debitura.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Debitura
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Debitura?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Debitura in the ClawLink dashboard — paste your Debitura API key once.
Verify the connection by asking Hermes:
Use Debitura to check case eligibility and walk me through the result in plain English.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
Debitura MCP for Hermes
Looking for a Debitura MCP server for Hermes Agent? ClawLink connects Debitura to Hermes Agent and exposes 11 Debitura tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Debitura integration works the same way.
What the Hermes Agent Debitura integration can do
11 Debitura tools are ready for Hermes Agent once the account is connected.
All 11 Debitura tools for Hermes
| 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 |
Try it: find the Debitura tool you need
Browse the 11 Debitura tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Debitura to check case eligibility and walk me through the result in plain English.
Pull the relevant data from Debitura, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Debitura, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Debitura, group them by priority, and recommend what Hermes 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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Debitura
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Debitura integration?
Yes. ClawLink is the fastest way to connect Hermes to Debitura: link your Debitura account once in the browser and Hermes Agent can call the Debitura API through 11 ready-made tools — no custom code or token handling.
How do I connect Debitura to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Debitura in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Debitura in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Debitura working from chat.
Hermes paired but still can't use Debitura
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.