# How to connect Quaderno to Hermes Agent (paste one key, 76 tools) > Connect Quaderno to Hermes with ClawLink: paste your Quaderno key once and 76 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/quaderno Most guides for giving Hermes Agent Quaderno 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 Quaderno setup: pair once in the browser and your always-on Hermes agent can act on Quaderno 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 Quaderno. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Quaderno** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 quaderno # connect Quaderno (browser OAuth) npx -y @useclawlink/cli actions quaderno # list available actions npx -y @useclawlink/cli run quaderno --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Quaderno in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Quaderno API key once. Verify the connection by asking Hermes: > Use Quaderno to calculate tax rate 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Quaderno is connected in the dashboard, that agent calls the same 76 Quaderno 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). ## Quaderno MCP for Hermes Looking for a Quaderno MCP server for Hermes Agent? ClawLink connects Quaderno to Hermes Agent and exposes 76 Quaderno 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 OpenClaw instead? The [OpenClaw Quaderno integration](https://claw-link.dev/openclaw/quaderno) works the same way. ## What the Hermes Agent Quaderno integration can do 76 Quaderno tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 76. ### 30 of 76 Quaderno tools for Hermes | Tool | What it does | |---|---| | **Calculate tax rate** `quaderno_calculate_tax_rate` | Calculate applicable tax rate for given address and transaction type | | **Get authorization** `quaderno_get_authorization` | Retrieve account credentials and verify API access | | **Get estimate** `quaderno_get_estimate` | Retrieve the details of an existing estimate by ID | | **List contacts** `quaderno_list_contacts` | List contacts, paginated and filterable by name, email, or tax ID | | **List coupons** `quaderno_list_coupons` | List all coupons | | **List credits** `quaderno_list_credits` | List all credit notes from Quaderno | | **List estimates** `quaderno_list_estimates` | List all estimates in the account, paginated and sorted by creation date (newest first) | | **List evidence** `quaderno_list_evidence` | List all evidence objects | | **List expenses** `quaderno_list_expenses` | List all expenses from Quaderno with pagination support | | **List invoices** `quaderno_list_invoices` | List all invoices from Quaderno with filtering support | | **List jurisdictions** `quaderno_list_jurisdictions` | List all tax jurisdictions | | **List products** `quaderno_list_products` | List all products (goods and services) from your Quaderno account | | **List receipts** `quaderno_list_receipts` | List all receipts from Quaderno with optional filtering by search query, date range, payment | | **List recurrings** `quaderno_list_recurrings` | List all recurring documents (invoices, expenses, or estimates) from your Quaderno account | | **List registered tax i ds** `quaderno_list_registered_tax_i_ds` | List all registered tax IDs | | **List reporting requests** `quaderno_list_reporting_requests` | Retrieves all reporting requests for the account with their current status and download URLs | | **List sessions** `quaderno_list_sessions` | List Quaderno Checkout sessions with optional filtering and pagination | | **List tax codes** `quaderno_list_tax_codes` | List all supported tax codes | | **List webhooks** `quaderno_list_webhooks` | List all webhooks | | **Ping** `quaderno_ping` | Check if the Quaderno API service is up and verify credentials | | **Retrieve contact** `quaderno_retrieve_contact` | Retrieve details of an existing contact by ID | | **Retrieve contact by processor ID** `quaderno_retrieve_contact_by_processor_id` | Retrieve a contact by external payment processor customer ID and gateway name | | **Retrieve coupon** `quaderno_retrieve_coupon` | Retrieve detailed information about a specific coupon by its ID | | **Retrieve credit** `quaderno_retrieve_credit` | Retrieve details of an existing credit note by ID | | **Retrieve evidence** `quaderno_retrieve_evidence` | Retrieves a specific evidence object by its ID | | **Retrieve expense** `quaderno_retrieve_expense` | Retrieve details of an existing expense by ID | | **Retrieve invoice** `quaderno_retrieve_invoice` | Retrieve details of an existing invoice by ID | | **Retrieve jurisdiction** `quaderno_retrieve_jurisdiction` | Retrieve a tax jurisdiction by ID | | **Retrieve product** `quaderno_retrieve_product` | Retrieve details of an existing product by ID | | **Retrieve receipt** `quaderno_retrieve_receipt` | Retrieve details of an existing receipt by ID | ## Example prompts **Calculate Tax Rate** > Use Quaderno to calculate tax rate and walk me through the result in plain English. **Get Authorization** > Pull the relevant data from Quaderno, summarize it in plain English, and point out anything that needs attention. **Get Estimate** > Pull the relevant data from Quaderno, summarize it in plain English, and point out anything that needs attention. **List Contacts** > List the relevant items in Quaderno, 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 Quaderno working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Quaderno API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Quaderno 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 Quaderno. | 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 Quaderno actions to the runtime in a format your agent can reliably use. | 76 tools for Quaderno are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Quaderno 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 Quaderno in the browser, and the 76 tools above work from chat. There is no SDK and no config file, and the Quaderno 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. ### Hermes paired but still can't use Quaderno 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 Quaderno 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 Quaderno tools Quaderno 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 Quaderno 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. ### Quaderno 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 Quaderno has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Quaderno integration? Yes. ClawLink is the fastest way to connect Hermes to Quaderno: link your Quaderno account once in the browser and Hermes Agent can call the Quaderno API through 76 ready-made tools — no custom code or token handling. ### How do I connect Quaderno 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 Quaderno in the dashboard and Hermes can use it from the next message — no config files, and the Quaderno key you paste is stored server-side instead of in your environment. ### How long does it take to connect Quaderno to Hermes Agent? About two minutes. Sign in, click Connect next to Quaderno in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Quaderno 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 Quaderno working from chat. ### Hermes paired but still can't use Quaderno 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`. ## Related - [Stripe](https://claw-link.dev/hermes/stripe) — Manage payments, customers, and invoices - [Zoho Books tools](https://claw-link.dev/hermes/zoho-books) — Organize finances, invoices, bills, and accounting - [Hermes Ramp integration](https://claw-link.dev/hermes/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts