How to connect Granola to OpenClaw
Connect Granola to OpenClaw with ClawLink in one click — 6 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
GranolaOAUTH2MCPAI meeting notes and transcripts. Once connected, OpenClaw can read and act on Granola from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Granola 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 Granola setup: install one ClawHub skill, connect Granola in the browser, and OpenClaw can call real Granola 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 Granola.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Granola
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Granola?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Granola in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Granola to mcp get account info and walk me through the result in plain English.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Granola is connected in the dashboard, that agent calls the same 6 Granola tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Granola MCP for OpenClaw
Looking for a Granola MCP server for OpenClaw? ClawLink connects Granola to OpenClaw and exposes 6 Granola tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Granola integration works the same way.
What the OpenClaw Granola integration can do
6 Granola tools are ready for OpenClaw once the account is connected.
All 6 Granola tools for OpenClaw
| Tool | What it does |
|---|---|
Mcp get account info granola_mcp_get_account_info | Get the email, active workspace, and effective note-access scopes for the Granola account |
Mcp get meeting transcript granola_mcp_get_meeting_transcript | Get the full transcript for a specific Granola meeting by ID |
Mcp get meetings granola_mcp_get_meetings | Get detailed meeting information for one or more Granola meetings by ID |
Mcp list meeting folders granola_mcp_list_meeting_folders | List the user's Granola meeting folders |
Mcp list meetings granola_mcp_list_meetings | List the user's Granola meeting notes within a time range |
Mcp query granola meetings granola_mcp_query_granola_meetings | Query Granola about the user's meetings using natural language |
Try it: find the Granola tool you need
Browse the 6 Granola tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Granola to mcp get account info and walk me through the result in plain English.
Use Granola to mcp get meeting transcript and walk me through the result in plain English.
Use Granola to mcp get meetings and walk me through the result in plain English.
Use Granola to mcp list meeting folders and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Granola working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Granola app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Granola through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Granola. | 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 Granola actions to the runtime in a format your agent can reliably use. | 6 tools for Granola are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Granola 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 Granola in the browser, and the 6 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Granola skill but can't call the tools
The ClawHub skill teaches OpenClaw about Granola, but the calls run through the ClawLink plugin and your connected account. Make sure Granola 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 Granola 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 Granola tools
Granola 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 Granola 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.
Granola 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Granola and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Granola integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Granola: link your Granola account once in the browser and OpenClaw can call the Granola API through 6 ready-made tools — no custom code or token handling.
How do I add Granola to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Granola skill from ClawHub, then you click Connect in the dashboard to authorize Granola. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Granola to OpenClaw?
About two minutes. Sign in, click Connect next to Granola in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Granola up myself?
The alternative to ClawLink is usually manual OAuth app 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 Granola working from chat.
OpenClaw installed the Granola skill but can't call the tools
The ClawHub skill teaches OpenClaw about Granola, but the calls run through the ClawLink plugin and your connected account. Make sure Granola 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.
