# How to connect Finmo to Hermes Agent (paste one key, 19 tools) > Connect Finmo to Hermes with ClawLink: paste your Finmo key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/finmo Most guides for giving Hermes Agent Finmo 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 Finmo setup: pair once in the browser and your always-on Hermes agent can act on Finmo 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 Finmo. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Finmo** — 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 finmo # connect Finmo (browser OAuth) npx -y @useclawlink/cli actions finmo # list available actions npx -y @useclawlink/cli run finmo --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 Finmo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Finmo API key once. Verify the connection by asking Hermes: > Pull the relevant data from Finmo, summarize it in plain English, and point out anything that needs attention. ### 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 Finmo is connected in the dashboard, that agent calls the same 19 Finmo 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). ## Finmo MCP for Hermes Looking for a Finmo MCP server for Hermes Agent? ClawLink connects Finmo to Hermes Agent and exposes 19 Finmo 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 Finmo integration](https://claw-link.dev/openclaw/finmo) works the same way. ## What the Hermes Agent Finmo integration can do 19 Finmo tools are ready for Hermes Agent once the account is connected. ### All 19 Finmo tools for Hermes | Tool | What it does | |---|---| | **Get payin method requirements** `finmo_get_payin_method_requirements` | Return the dynamic required fields, validation regexes, limits, instructions, and capabilities | | **Get payment** `finmo_get_payment` | Get one payin, payout, or refund by its Finmo reference ID | | **Get payout method requirements** `finmo_get_payout_method_requirements` | Return the dynamic payout, beneficiary, and sender field requirements for one Finmo payout | | **Get wallet** `finmo_get_wallet` | Get one wallet and its currency accounts, including actual and available balances | | **List customers** `finmo_list_customers` | List one page of individual or company customer profiles and wallet-readiness state | | **List payin methods** `finmo_list_payin_methods` | List one page of enabled ways to collect money for a country and currency, with a continuation | | **List payins** `finmo_list_payins` | List inbound payment attempts with status, method, customer, wallet, and time filters | | **List payout beneficiaries** `finmo_list_payout_beneficiaries` | List one page of stored payout beneficiaries and their destination details | | **List payout methods** `finmo_list_payout_methods` | List one page of enabled payout rails for a sender and beneficiary country/currency pair | | **List payouts** `finmo_list_payouts` | List one page of outbound payments with status, payout method, and time filters | | **List refunds** `finmo_list_refunds` | List one page of refunds with status, originating payin, amount, and time filters | | **List transactions** `finmo_list_transactions` | List organization-level financial transactions for reconciliation, filtered by customer, event | | **List wallets** `finmo_list_wallets` | List one page of Finmo wallets available to the connected organization or a customer | | **Create customer** `finmo_create_customer` | Create a real production Finmo customer profile containing personal or company identity data | | **Create payout beneficiary** `finmo_create_payout_beneficiary` | Create a real payout beneficiary in the connected Finmo production account | | **Create payin** `finmo_create_payin` | Create a real production payin that can collect money from a customer and credit a customer or | | **Create payout** `finmo_create_payout` | Send real production funds from a Finmo wallet to a beneficiary | | **Create refund** `finmo_create_refund` | Issue a real production full refund for a completed Finmo payin | | **Transfer wallet funds** `finmo_transfer_wallet_funds` | Move real production funds immediately between two Finmo wallets | ## Example prompts **Get Payin Method Requirements** > Pull the relevant data from Finmo, summarize it in plain English, and point out anything that needs attention. **Get Payment** > Pull the relevant data from Finmo, summarize it in plain English, and point out anything that needs attention. **Get Payout Method Requirements** > Pull the relevant data from Finmo, summarize it in plain English, and point out anything that needs attention. **Get Wallet** > Pull the relevant data from Finmo, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Finmo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Finmo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Finmo 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 Finmo. | 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 Finmo actions to the runtime in a format your agent can reliably use. | 19 tools for Finmo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Finmo 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 Finmo in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Finmo 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 Finmo 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 Finmo 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 Finmo tools Finmo 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 Finmo 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. ### Finmo 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 Finmo 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 Finmo integration? Yes. ClawLink is the fastest way to connect Hermes to Finmo: link your Finmo account once in the browser and Hermes Agent can call the Finmo API through 19 ready-made tools — no custom code or token handling. ### How do I connect Finmo 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 Finmo in the dashboard and Hermes can use it from the next message — no config files, and the Finmo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Finmo to Hermes Agent? About two minutes. Sign in, click Connect next to Finmo in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Finmo 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 Finmo working from chat. ### Hermes paired but still can't use Finmo 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](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