How to connect Flatfile to Hermes Agent
Connect Flatfile to Hermes with ClawLink: paste your Flatfile key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.
FlatfileAPI KEYMCPFlatfile is a data exchange platform for collecting, validating, transforming, and managing structured data across collaborative workflows.. Once connected, Hermes Agent can read and act on Flatfile from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Flatfile 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 Flatfile setup: pair once in the browser and your always-on Hermes agent can act on Flatfile 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 Flatfile.
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 Flatfile
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Flatfile?"
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 Flatfile in the ClawLink dashboard — paste your Flatfile API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Flatfile, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Flatfile is connected in the dashboard, that agent calls the same 12 Flatfile tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Flatfile MCP for Hermes
Looking for a Flatfile MCP server for Hermes Agent? ClawLink connects Flatfile to Hermes Agent and exposes 12 Flatfile tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Flatfile integration works the same way.
What the Hermes Agent Flatfile integration can do
12 Flatfile tools are ready for Hermes Agent once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12.
11 of 12 Flatfile tools for Hermes
| Tool | What it does |
|---|---|
Get job flatfile_get_job | Get detailed status, outcome, result, and diagnostic information for one Flatfile asynchronous |
Get sheet flatfile_get_sheet | Get one sheet's field configuration and record counts before reading or writing records |
Get space flatfile_get_space | Get safe metadata for one Flatfile space without exposing transient access credentials or |
List environments flatfile_list_environments | List Flatfile environments visible to the connected environment secret key and return the IDs |
List files flatfile_list_files | Discover import or export files and their processing status, optionally within a Flatfile space |
List jobs flatfile_list_jobs | Find asynchronous Flatfile jobs by environment, space, workbook, file, or parent job and |
List records flatfile_list_records | Read one page of records from a Flatfile sheet, optionally filtering by validity, field, record |
List spaces flatfile_list_spaces | Find Flatfile spaces by environment, text, namespace, archive state, or template status |
List workbooks flatfile_list_workbooks | List workbooks, optionally within a space, with their nested sheets so an agent can continue to |
Insert records flatfile_insert_records | Insert one or more rows into a Flatfile sheet using simple field-key to value objects |
Update records flatfile_update_records | Update one or more existing Flatfile records by ID using simple field-key to value objects |
Try it: find the Flatfile tool you need
Browse the 11 Flatfile tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Flatfile, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Flatfile, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Flatfile, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Flatfile, 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 Flatfile working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Flatfile API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Flatfile 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 Flatfile. | 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 Flatfile actions to the runtime in a format your agent can reliably use. | 12 tools for Flatfile are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Flatfile 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 Flatfile in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Flatfile 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 Flatfile
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 Flatfile 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 Flatfile tools
Flatfile 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 Flatfile 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.
Flatfile 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 Flatfile 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 Flatfile integration?
Yes. ClawLink is the fastest way to connect Hermes to Flatfile: link your Flatfile account once in the browser and Hermes Agent can call the Flatfile API through 12 ready-made tools — no custom code or token handling.
How do I connect Flatfile 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 Flatfile in the dashboard and Hermes can use it from the next message — no config files, and the Flatfile key you paste is stored server-side instead of in your environment.
How long does it take to connect Flatfile to Hermes Agent?
About two minutes. Sign in, click Connect next to Flatfile in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Flatfile 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 Flatfile working from chat.
Hermes paired but still can't use Flatfile
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.
