# How to connect Basin to OpenClaw (paste one key, 19 tools) > Connect Basin to OpenClaw with ClawLink: paste your Basin key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/basin The usual route to Basin 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 Basin setup: install one ClawHub skill, connect Basin in the browser, and OpenClaw can call real Basin 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 Basin. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Basin** — 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 basin # connect Basin (browser OAuth) npx -y @useclawlink/cli actions basin # list available actions npx -y @useclawlink/cli run basin --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 Basin in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Basin API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Basin, 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 Basin is connected in the dashboard, that agent calls the same 19 Basin 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). ## Basin MCP for OpenClaw Looking for a Basin MCP server for OpenClaw? ClawLink connects Basin to OpenClaw and exposes 19 Basin 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 Basin integration](https://claw-link.dev/hermes/basin) works the same way. ## What the OpenClaw Basin integration can do 19 Basin tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 19. ### 15 of 19 Basin tools for OpenClaw | Tool | What it does | |---|---| | **Get domains** `basin_get_domains` | Retrieve a list of all custom domains associated with the Basin account | | **Get form details** `basin_get_form_details` | Retrieves comprehensive details about a specific Basin form including configuration | | **Get form webhook** `basin_get_form_webhook` | Retrieve details of a specific form webhook by its ID | | **Get forms** `basin_get_forms` | Retrieves a list of all Basin forms with their configuration and metadata | | **Get project details** `basin_get_project_details` | Retrieve detailed information about a specific project | | **Get projects** `basin_get_projects` | Retrieves a list of Basin projects from your account | | **Get submissions** `basin_get_submissions` | Retrieve form submissions from Basin with optional filtering, sorting, and search capabilities | | **Get webhooks** `basin_get_webhooks` | Retrieve all webhooks associated with a specific form | | **List form views** `basin_list_form_views` | Retrieves a list of all Basin form views with their configuration and metadata | | **Create form** `basin_create_form` | Create a new form in Basin | | **Create form webhook** `basin_create_form_webhook` | Create a new webhook for a specific form | | **Create project** `basin_create_project` | Create a new Basin project | | **Update form** `basin_update_form` | Update an existing Basin form by ID | | **Update project** `basin_update_project` | Update details of an existing project | | **Update webhook** `basin_update_webhook` | Update settings of an existing webhook for a form | ## Example prompts **Get Domains** > Pull the relevant data from Basin, summarize it in plain English, and point out anything that needs attention. **Get Form Details** > Pull the relevant data from Basin, summarize it in plain English, and point out anything that needs attention. **Get Form Webhook** > Pull the relevant data from Basin, summarize it in plain English, and point out anything that needs attention. **Get Forms** > Pull the relevant data from Basin, 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 Basin working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Basin API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Basin 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 Basin. | 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 Basin actions to the runtime in a format your agent can reliably use. | 19 tools for Basin are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Basin 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 Basin in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Basin 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 Basin skill but can't call the tools The ClawHub skill teaches OpenClaw about Basin, but the calls run through the ClawLink plugin and your connected account. Make sure Basin 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 Basin 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 Basin tools Basin 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 Basin 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. ### Basin 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 Basin has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Basin integration? Yes. ClawLink is the fastest way to connect OpenClaw to Basin: link your Basin account once in the browser and OpenClaw can call the Basin API through 19 ready-made tools — no custom code or token handling. ### How do I add Basin to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Basin skill from ClawHub, then you click Connect in the dashboard to authorize Basin. OpenClaw calls the tools from the next message — no config files, and the Basin key you paste is stored server-side instead of in your environment. ### How long does it take to connect Basin to OpenClaw? About two minutes. Sign in, click Connect next to Basin in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Basin 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 Basin working from chat. ### OpenClaw installed the Basin skill but can't call the tools The ClawHub skill teaches OpenClaw about Basin, but the calls run through the ClawLink plugin and your connected account. Make sure Basin 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 GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.