# How to connect Fireflies to OpenClaw (paste one key, 26 tools) > Connect Fireflies to OpenClaw 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/openclaw/fireflies The usual route to Fireflies access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Fireflies setup: install one ClawHub skill, connect Fireflies in the browser, and OpenClaw can call real Fireflies actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Fireflies. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Fireflies** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Fireflies in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fireflies API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Fireflies, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw 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 OpenClaw Looking for a Fireflies MCP server for OpenClaw? ClawLink connects Fireflies to OpenClaw 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 Hermes instead? The [Hermes Fireflies integration](https://claw-link.dev/hermes/fireflies) works the same way. ## What the OpenClaw Fireflies integration can do 26 Fireflies tools are ready for OpenClaw 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 OpenClaw | 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 OpenClaw. 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 OpenClaw 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. ### OpenClaw installed the Fireflies skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireflies, but the calls run through the ClawLink plugin and your connected account. Make sure Fireflies is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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 OpenClaw Fireflies integration? Yes. ClawLink is the fastest way to connect OpenClaw to Fireflies: link your Fireflies account once in the browser and OpenClaw can call the Fireflies API through 26 ready-made tools — no custom code or token handling. ### How do I add Fireflies to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fireflies skill from ClawHub, then you click Connect in the dashboard to authorize Fireflies. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Fireflies in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Fireflies working from chat. ### OpenClaw installed the Fireflies skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireflies, but the calls run through the ClawLink plugin and your connected account. Make sure Fireflies is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/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. - [OpenClaw Just One API integration](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.