# How to connect Coda to OpenClaw > Connect Coda to OpenClaw in one click. 8 Coda tools your agent can call from chat. No API keys. Web version: https://claw-link.dev/openclaw/coda ClawLink gives OpenClaw a more practical Coda setup than rolling your own integration. Install one ClawHub skill, connect Coda in the browser, and OpenClaw can call real Coda actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Coda MCP for OpenClaw Looking for a Coda MCP server for OpenClaw? ClawLink connects Coda to OpenClaw and exposes 8 Coda 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 Coda integration](https://claw-link.dev/hermes/coda) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/coda ## Setup It takes three steps to connect OpenClaw to Coda. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Coda** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 coda # connect Coda (browser OAuth) npx -y @useclawlink/cli actions coda # list available actions npx -y @useclawlink/cli run coda --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Coda integration can do 8 Coda tools are ready for OpenClaw once the account is connected. ### All 8 Coda tools for OpenClaw | Tool | What it does | |---|---| | **Get a column** `coda_get_a_column` | Returns detailed information about a specific column in a Coda table | | **Get content types** `coda_get_content_types` | Returns all content types in a Coda doc | | **Content export status** `coda_content_export_status` | Check the status of a page content export operation | | **Get acl settings** `coda_get_acl_settings` | Returns ACL settings for a Coda doc | | **Add a permission for pack** `coda_add_a_permission_for_pack` | Create or modify permissions for a Pack | | **Add custom domain** `coda_add_custom_domain` | Add a custom domain to a published doc | | **Archive asset** `coda_archive_asset` | Archive an asset in Coda | | **Archive entry** `coda_archive_entry` | Archive an entry in Coda | ## Example prompts **Get A Column** > Pull the relevant data from Coda, summarize it in plain English, and point out anything that needs attention. **Get Content Types** > Pull the relevant data from Coda, summarize it in plain English, and point out anything that needs attention. **Content Export Status** > Use Coda to content export status and walk me through the result in plain English. **Get Acl Settings** > Pull the relevant data from Coda, summarize it in plain English, and point out anything that needs attention. ## 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 Coda working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Coda app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Coda 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 Coda. | 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 Coda actions to the runtime in a format your agent can reliably use. | 8 tools for Coda are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Coda 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 Coda in the browser, and the 8 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Coda skill but can't call the tools The ClawHub skill teaches OpenClaw about Coda, but the calls run through the ClawLink plugin and your connected account. Make sure Coda 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 Coda from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### The Coda account is connected but the action fails Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Coda and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Coda integration? Yes. ClawLink is the fastest way to connect OpenClaw to Coda: link your Coda account once in the browser and OpenClaw can call the Coda API through 8 ready-made tools — no custom code or token handling. ### How do I add Coda to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Coda skill from ClawHub, then you click Connect in the dashboard to authorize Coda. OpenClaw calls the tools from the next message — no config files or API keys. ### How long does it take to connect Coda to OpenClaw? About two minutes. Sign in, click Connect next to Coda in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Coda 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 Coda working from chat. ### OpenClaw installed the Coda skill but can't call the tools The ClawHub skill teaches OpenClaw about Coda, but the calls run through the ClawLink plugin and your connected account. Make sure Coda 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 - [Connect ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints - [Notion tools](https://claw-link.dev/openclaw/notion) — Manage pages, databases, and blocks - [OpenClaw Typeform integration](https://claw-link.dev/openclaw/typeform) — Create interactive forms and surveys