# How to connect Fireflies to Hermes Agent (paste one key, 26 tools) > Connect Fireflies to Hermes with ClawLink: paste your Fireflies key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/fireflies Most guides for giving Hermes Agent Fireflies 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 Fireflies setup: pair once in the browser and your always-on Hermes agent can act on Fireflies 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 Fireflies. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Fireflies** — 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 fireflies # connect Fireflies (browser OAuth) npx -y @useclawlink/cli actions fireflies # list available actions npx -y @useclawlink/cli run fireflies --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 Fireflies in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fireflies API key once. Verify the connection by asking Hermes: > Pull the relevant data from Fireflies, 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 Fireflies is connected in the dashboard, that agent calls the same 26 Fireflies 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). ## Fireflies MCP for Hermes Looking for a Fireflies MCP server for Hermes Agent? ClawLink connects Fireflies to Hermes Agent and exposes 26 Fireflies 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 Fireflies integration](https://claw-link.dev/openclaw/fireflies) works the same way. ## What the Hermes Agent Fireflies integration can do 26 Fireflies tools are ready for Hermes Agent once the account is connected. The 25 below are the ones people reach for most; your agent can call all 26. ### 25 of 26 Fireflies tools for Hermes | Tool | What it does | |---|---| | **Fetch AI app outputs2** `fireflies_fetch_ai_app_outputs2` | Fetch AI App outputs for specific apps or transcripts | | **Get ask fred thread** `fireflies_get_ask_fred_thread` | Get a specific AskFred conversation thread with full history | | **Get ask fred threads** `fireflies_get_ask_fred_threads` | Retrieve a summary of all AskFred conversation threads for the current user | | **Get bite by ID** `fireflies_get_bite_by_id` | Fetches details for a specific bite by ID | | **Get bites** `fireflies_get_bites` | Fetches a list of bites (highlights) against input arguments | | **Get meeting analytics** `fireflies_get_meeting_analytics` | Retrieves comprehensive meeting analytics including team-level conversation metrics, sentiment | | **Get meeting participants** `fireflies_get_meeting_participants` | Retrieves the list of participants who attended a specific Fireflies meeting along with their | | **Get meeting topics** `fireflies_get_meeting_topics` | Retrieves AI-extracted topics, keywords, and meeting type for a specific Fireflies transcript | | **Get transcript by ID** `fireflies_get_transcript_by_id` | Fetches details for a specific Fireflies transcript ID | | **Get transcripts** `fireflies_get_transcripts` | Fetches a list of transcripts against input filters | | **Get user by ID** `fireflies_get_user_by_id` | The GetUser Action is designed to fetch details associated with a specific user id | | **Get user groups** `fireflies_get_user_groups` | Fetch a list of all user groups within the team with information about user groups including | | **Get users** `fireflies_get_users` | Fetches a list of all users within the team, including their full email addresses | | **Graphql query** `fireflies_graphql_query` | Execute an authenticated, read-only Fireflies GraphQL operation (query) and return the full raw | | **List channels** `fireflies_list_channels` | Fetches a list of all channels accessible to the authenticated user, including both public | | **Search transcripts** `fireflies_search_transcripts` | Search transcripts using keyword-based full-text search across meeting titles and/or spoken | | **Add to live** `fireflies_add_to_live` | The AddToLive Action allows you to add the Fireflies.ai bot to an ongoing meeting | | **Continue ask fred thread** `fireflies_continue_ask_fred_thread` | Continue an existing AskFred conversation thread with follow-up questions | | **Create ask fred thread** `fireflies_create_ask_fred_thread` | Start a new AskFred conversation thread with a question about meetings | | **Create bite** `fireflies_create_bite` | Create a bite (short video or audio clip) from a transcript segment | | **Set user role** `fireflies_set_user_role` | Update a user's role within a team | | **Update meeting channel** `fireflies_update_meeting_channel` | Batch update channel assignments for 1-5 meeting transcripts | | **Update meeting privacy** `fireflies_update_meeting_privacy` | Update the privacy setting of a meeting transcript | | **Update meeting title** `fireflies_update_meeting_title` | Update the title of a meeting transcript | | **Upload audio** `fireflies_upload_audio` | The UploadAudio Action allows you to upload audio files to Fireflies.ai for transcription | ## Example prompts **Fetch Ai App Outputs2** > Pull the relevant data from Fireflies, summarize it in plain English, and point out anything that needs attention. **Get Ask Fred Thread** > Pull the relevant data from Fireflies, summarize it in plain English, and point out anything that needs attention. **Get Ask Fred Threads** > Pull the relevant data from Fireflies, summarize it in plain English, and point out anything that needs attention. **Get Bite By Id** > Pull the relevant data from Fireflies, 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 Fireflies working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fireflies API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fireflies 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 Fireflies. | 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 Fireflies actions to the runtime in a format your agent can reliably use. | 26 tools for Fireflies are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fireflies 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 Fireflies in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Fireflies 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 Fireflies 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 Fireflies 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 Fireflies tools Fireflies 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 Fireflies 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. ### Fireflies 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 Fireflies 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 Fireflies integration? Yes. ClawLink is the fastest way to connect Hermes to Fireflies: link your Fireflies account once in the browser and Hermes Agent can call the Fireflies API through 26 ready-made tools — no custom code or token handling. ### How do I connect Fireflies 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 Fireflies in the dashboard and Hermes can use it from the next message — no config files, and the Fireflies key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fireflies to Hermes Agent? About two minutes. Sign in, click Connect next to Fireflies in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Fireflies 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 Fireflies working from chat. ### Hermes paired but still can't use Fireflies 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 DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Connect Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.