# How to connect Turbot Pipes to OpenClaw (paste one key, 169 tools) > Connect Turbot Pipes to OpenClaw with ClawLink: paste your Turbot Pipes key once and 169 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/turbot-pipes The usual route to Turbot Pipes 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 Turbot Pipes setup: install one ClawHub skill, connect Turbot Pipes in the browser, and OpenClaw can call real Turbot Pipes actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **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/turbot-pipes ## Setup It takes three steps to connect OpenClaw to Turbot Pipes. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Turbot Pipes** — 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 turbot-pipes # connect Turbot Pipes (browser OAuth) npx -y @useclawlink/cli actions turbot-pipes # list available actions npx -y @useclawlink/cli run turbot-pipes --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 Turbot Pipes in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Turbot Pipes API key once. Verify the connection by asking OpenClaw: > Use Turbot Pipes to actor get 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Turbot Pipes is connected in the dashboard, that agent calls the same 169 Turbot Pipes 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). ## Turbot Pipes MCP for OpenClaw Looking for a Turbot Pipes MCP server for OpenClaw? ClawLink connects Turbot Pipes to OpenClaw and exposes 169 Turbot Pipes 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 Turbot Pipes integration](https://claw-link.dev/hermes/turbot-pipes) works the same way. ## What the OpenClaw Turbot Pipes integration can do 169 Turbot Pipes tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 169. ### 30 of 169 Turbot Pipes tools for OpenClaw | Tool | What it does | |---|---| | **Actor get** `turbot_pipes_actor_get` | Retrieve the authenticated actor | | **Actor list activity** `turbot_pipes_actor_list_activity` | List activities for the authenticated actor | | **Actor list connections** `turbot_pipes_actor_list_connections` | List connections associated with the authenticated actor | | **Actor list orgs** `turbot_pipes_actor_list_orgs` | List organizations associated with the authenticated actor | | **Actor list workspaces** `turbot_pipes_actor_list_workspaces` | List workspaces for the authenticated actor | | **Auth login token email create** `turbot_pipes_auth_login_token_email_create` | Start login process by sending a confirmation code to a user's email | | **Create auth signup** `turbot_pipes_create_auth_signup` | Create a new user account via signup | | **Create org connection** `turbot_pipes_create_org_connection` | Create a new connection for an organization | | **Create org connection folder** `turbot_pipes_create_org_connection_folder` | Create a new connection folder for an organization | | **Create org workspace query** `turbot_pipes_create_org_workspace_query` | Execute a SQL query in an org workspace using POST method | | **Get auth provider** `turbot_pipes_get_auth_provider` | Initiate OAuth authentication flow with a provider | | **Get conversation user** `turbot_pipes_get_conversation_user` | Retrieve details for a specific user workspace conversation | | **Get datatank table** `turbot_pipes_get_datatank_table` | Get the details for a workspace Datatank table | | **Get org** `turbot_pipes_get_org` | Retrieve organization information by handle | | **Get org billing invoice** `turbot_pipes_get_org_billing_invoice` | Get an invoice for an organization | | **Get org connection permission** `turbot_pipes_get_org_connection_permission` | Retrieve permission details for an org connection | | **Get org integration** `turbot_pipes_get_org_integration` | Get details of an integration configured on an organization | | **Get org member** `turbot_pipes_get_org_member` | Retrieve a specific organization member by org handle and user handle | | **Get org workspace connection** `turbot_pipes_get_org_workspace_connection` | Get the details for a workspace and connection association on an organization | | **Get org workspace connection folder** `turbot_pipes_get_org_workspace_connection_folder` | Retrieve a connection folder for an organization workspace | | **Get org workspace flowpipe trigger** `turbot_pipes_get_org_workspace_flowpipe_trigger` | Get the details of a trigger for a workspace in an organization | | **Get org workspace integration** `turbot_pipes_get_org_workspace_integration` | Get details of an integration available for a workspace belonging to an organization | | **Get org workspace mod variable setting** `turbot_pipes_get_org_workspace_mod_variable_setting` | Get setting for a mod variable in an organization workspace | | **Get org workspace notifier** `turbot_pipes_get_org_workspace_notifier` | Retrieve a notifier from an org workspace | | **Get org workspace query data** `turbot_pipes_get_org_workspace_query_data` | Execute a SQL query in an org workspace and retrieve results | | **Get tenant** `turbot_pipes_get_tenant` | Retrieve tenant information by handle | | **Get tenant avatar** `turbot_pipes_get_tenant_avatar` | Retrieve public avatar image for a tenant | | **Get user** `turbot_pipes_get_user` | Retrieve user information by handle | | **Get user AI key** `turbot_pipes_get_user_ai_key` | Retrieve AI provider API key metadata at the user level | | **Get user billing plan** `turbot_pipes_get_user_billing_plan` | Get the current user billing plan | ## Example prompts **Actor Get** > Use Turbot Pipes to actor get and walk me through the result in plain English. **Actor List Activity** > Use Turbot Pipes to actor list activity and walk me through the result in plain English. **Actor List Connections** > Use Turbot Pipes to actor list connections and walk me through the result in plain English. **Actor List Orgs** > Use Turbot Pipes to actor list orgs and walk me through the result in plain English. ## 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 Turbot Pipes working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Turbot Pipes API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Turbot Pipes 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 Turbot Pipes. | 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 Turbot Pipes actions to the runtime in a format your agent can reliably use. | 169 tools for Turbot Pipes are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Turbot Pipes 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 Turbot Pipes in the browser, and the 169 tools above work from chat. There is no SDK and no config file, and the Turbot Pipes 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 Turbot Pipes skill but can't call the tools The ClawHub skill teaches OpenClaw about Turbot Pipes, but the calls run through the ClawLink plugin and your connected account. Make sure Turbot Pipes 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 Turbot Pipes 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 Turbot Pipes tools Turbot Pipes 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 Turbot Pipes 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. ### Turbot Pipes 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 Turbot Pipes has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Turbot Pipes integration? Yes. ClawLink is the fastest way to connect OpenClaw to Turbot Pipes: link your Turbot Pipes account once in the browser and OpenClaw can call the Turbot Pipes API through 169 ready-made tools — no custom code or token handling. ### How do I add Turbot Pipes to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Turbot Pipes skill from ClawHub, then you click Connect in the dashboard to authorize Turbot Pipes. OpenClaw calls the tools from the next message — no config files, and the Turbot Pipes key you paste is stored server-side instead of in your environment. ### How long does it take to connect Turbot Pipes to OpenClaw? About two minutes. Sign in, click Connect next to Turbot Pipes in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Turbot Pipes 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 Turbot Pipes working from chat. ### OpenClaw installed the Turbot Pipes skill but can't call the tools The ClawHub skill teaches OpenClaw about Turbot Pipes, but the calls run through the ClawLink plugin and your connected account. Make sure Turbot Pipes 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.