# How to connect Retable to OpenClaw (paste one key, 11 tools) > Connect Retable to OpenClaw with ClawLink: paste your Retable key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/retable The usual route to Retable 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 Retable setup: install one ClawHub skill, connect Retable in the browser, and OpenClaw can call real Retable 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 Retable. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Retable** — 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 retable # connect Retable (browser OAuth) npx -y @useclawlink/cli actions retable # list available actions npx -y @useclawlink/cli run retable --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 Retable in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Retable API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Retable, 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 Retable is connected in the dashboard, that agent calls the same 11 Retable 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). ## Retable MCP for OpenClaw Looking for a Retable MCP server for OpenClaw? ClawLink connects Retable to OpenClaw and exposes 11 Retable 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 Retable integration](https://claw-link.dev/hermes/retable) works the same way. ## What the OpenClaw Retable integration can do 11 Retable tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 11. ### 9 of 11 Retable tools for OpenClaw | Tool | What it does | |---|---| | **Get rows** `retable_get_rows` | Return all rows or up to 50 selected rows using stable column IDs or title-keyed fields | | **Get table** `retable_get_table` | Get one table's metadata, column IDs and types, and views before reading or changing its data | | **List project tables** `retable_list_project_tables` | List tables in one Retable project with their IDs, columns, and parent workspace and project IDs | | **List workspace projects** `retable_list_workspace_projects` | List projects accessible in one workspace, including project IDs needed to discover tables | | **List workspaces** `retable_list_workspaces` | List workspaces visible to the connected Retable account, including each workspace ID needed to | | **Search rows** `retable_search_rows` | Search a table for a value in a primary column and return matching rows from an optional | | **Add columns** `retable_add_columns` | Append one or more typed columns to a table and return the complete resulting column list | | **Insert rows** `retable_insert_rows` | Insert one or more rows into a table in one request and return the created rows with their IDs | | **Update rows** `retable_update_rows` | Update cells in one or more existing rows in one request and return the updated row IDs | ## Example prompts **Get Rows** > Pull the relevant data from Retable, summarize it in plain English, and point out anything that needs attention. **Get Table** > Pull the relevant data from Retable, summarize it in plain English, and point out anything that needs attention. **List Project Tables** > List the relevant items in Retable, group them by priority, and recommend what OpenClaw should do next. **List Workspace Projects** > List the relevant items in Retable, group them by priority, and recommend what OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Retable working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Retable API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Retable 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 Retable. | 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 Retable actions to the runtime in a format your agent can reliably use. | 11 tools for Retable are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Retable 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 Retable in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Retable 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 Retable skill but can't call the tools The ClawHub skill teaches OpenClaw about Retable, but the calls run through the ClawLink plugin and your connected account. Make sure Retable 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 Retable 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 Retable tools Retable 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 Retable 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. ### Retable 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 Retable has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Retable integration? Yes. ClawLink is the fastest way to connect OpenClaw to Retable: link your Retable account once in the browser and OpenClaw can call the Retable API through 11 ready-made tools — no custom code or token handling. ### How do I add Retable to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Retable skill from ClawHub, then you click Connect in the dashboard to authorize Retable. OpenClaw calls the tools from the next message — no config files, and the Retable key you paste is stored server-side instead of in your environment. ### How long does it take to connect Retable to OpenClaw? About two minutes. Sign in, click Connect next to Retable in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Retable 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 Retable working from chat. ### OpenClaw installed the Retable skill but can't call the tools The ClawHub skill teaches OpenClaw about Retable, but the calls run through the ClawLink plugin and your connected account. Make sure Retable 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 Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints