# How to connect Feathery to Hermes Agent (paste one key, 19 tools) > Connect Feathery to Hermes with ClawLink: paste your Feathery 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/feathery Most guides for giving Hermes Agent Feathery 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 Feathery setup: pair once in the browser and your always-on Hermes agent can act on Feathery 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 Feathery. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Feathery** — 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 feathery # connect Feathery (browser OAuth) npx -y @useclawlink/cli actions feathery # list available actions npx -y @useclawlink/cli run feathery --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 Feathery in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Feathery API key once. Verify the connection by asking Hermes: > Use Feathery to account get info 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 Feathery is connected in the dashboard, that agent calls the same 19 Feathery 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). ## Feathery MCP for Hermes Looking for a Feathery MCP server for Hermes Agent? ClawLink connects Feathery to Hermes Agent and exposes 19 Feathery 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 Feathery integration](https://claw-link.dev/openclaw/feathery) works the same way. ## What the Hermes Agent Feathery integration can do 19 Feathery tools are ready for Hermes Agent once the account is connected. The 17 below are the ones people reach for most; your agent can call all 19. ### 17 of 19 Feathery tools for Hermes | Tool | What it does | |---|---| | **Account get info** `feathery_account_get_info` | Get your Feathery team name and list of accounts | | **Document list envelopes** `feathery_document_list_envelopes` | List generated document envelopes by document or user ID | | **Form get schema** `feathery_form_get_schema` | Retrieve the complete schema of a Feathery form including all steps, fields, rules, and | | **Form list** `feathery_form_list` | List all forms in your Feathery account | | **Form list hidden fields** `feathery_form_list_hidden_fields` | List all hidden form fields in the account | | **Log list API connector errors** `feathery_log_list_api_connector_errors` | List recent API connector error logs for a form | | **Log list email issues** `feathery_log_list_email_issues` | List email bounce and complaint events | | **Log list emails** `feathery_log_list_emails` | List recently sent emails for a form | | **Log list quick requests** `feathery_log_list_quick_requests` | List recent Quik integration request logs for a form | | **User get all data** `feathery_user_get_all_data` | Retrieve all stored data fields for a user or all field definitions in your Feathery account | | **User get session** `feathery_user_get_session` | Get a user's form session and progress | | **User list** `feathery_user_list` | List all users in your Feathery account | | **Account edit** `feathery_account_edit` | Edit an existing account’s role and permissions | | **Document fill template** `feathery_document_fill_template` | Fill or sign a Feathery document template | | **Form create hidden field** `feathery_form_create_hidden_field` | Creates a new hidden field in the Feathery account | | **User create or fetch** `feathery_user_create_or_fetch` | Create a new user or fetch an existing one | | **Workspace generate login token** `feathery_workspace_generate_login_token` | Generate a login JWT for a Feathery workspace | ## Example prompts **Account Get Info** > Use Feathery to account get info and walk me through the result in plain English. **Document List Envelopes** > Use Feathery to document list envelopes and walk me through the result in plain English. **Form Get Schema** > Use Feathery to form get schema and walk me through the result in plain English. **Form List** > Use Feathery to form list and walk me through the result in plain English. ## 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 Feathery working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Feathery API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Feathery 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 Feathery. | 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 Feathery actions to the runtime in a format your agent can reliably use. | 19 tools for Feathery are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Feathery 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 Feathery in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Feathery 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 Feathery 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 Feathery 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 Feathery tools Feathery 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 Feathery 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. ### Feathery 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 Feathery 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 Feathery integration? Yes. ClawLink is the fastest way to connect Hermes to Feathery: link your Feathery account once in the browser and Hermes Agent can call the Feathery API through 19 ready-made tools — no custom code or token handling. ### How do I connect Feathery 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 Feathery in the dashboard and Hermes can use it from the next message — no config files, and the Feathery key you paste is stored server-side instead of in your environment. ### How long does it take to connect Feathery to Hermes Agent? About two minutes. Sign in, click Connect next to Feathery in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Feathery 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 Feathery working from chat. ### Hermes paired but still can't use Feathery 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.