# How to connect Pylon to OpenClaw (no API keys) > Connect Pylon to OpenClaw with ClawLink in one click — 12 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/pylon The usual route to Pylon 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 Pylon setup: install one ClawHub skill, connect Pylon in the browser, and OpenClaw can call real Pylon 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 Pylon. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Pylon** — 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 pylon # connect Pylon (browser OAuth) npx -y @useclawlink/cli actions pylon # list available actions npx -y @useclawlink/cli run pylon --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 Pylon in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Pylon to mcp get account 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 Pylon is connected in the dashboard, that agent calls the same 12 Pylon 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). ## Pylon MCP for OpenClaw Looking for a Pylon MCP server for OpenClaw? ClawLink connects Pylon to OpenClaw and exposes 12 Pylon 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 Pylon integration](https://claw-link.dev/hermes/pylon) works the same way. ## What the OpenClaw Pylon integration can do 12 Pylon tools are ready for OpenClaw once the account is connected. ### All 12 Pylon tools for OpenClaw | Tool | What it does | |---|---| | **Mcp get account** `pylon_mcp_get_account` | Get full details for a Pylon customer account | | **Mcp get contact** `pylon_mcp_get_contact` | Get full details for a Pylon contact (customer) | | **Mcp get issue** `pylon_mcp_get_issue` | Get full details for a Pylon support issue/ticket | | **Mcp get issue messages** `pylon_mcp_get_issue_messages` | Get the full message history for a Pylon issue | | **Mcp get me** `pylon_mcp_get_me` | Get the currently authenticated user's details | | **Mcp get user** `pylon_mcp_get_user` | Get full details for a Pylon user (team member) | | **Mcp search accounts** `pylon_mcp_search_accounts` | Search for customer accounts in Pylon | | **Mcp search issues** `pylon_mcp_search_issues` | Search for issues/tickets in Pylon | | **Mcp create issue** `pylon_mcp_create_issue` | Create a new issue/ticket in Pylon | | **Mcp update account** `pylon_mcp_update_account` | Update an existing customer account in Pylon | | **Mcp update issue** `pylon_mcp_update_issue` | Update an existing issue/ticket in Pylon | | **Mcp upload account files** `pylon_mcp_upload_account_files` | Upload one or more files (e.g | ## Example prompts **Mcp Get Account** > Use Pylon to mcp get account and walk me through the result in plain English. **Mcp Get Contact** > Use Pylon to mcp get contact and walk me through the result in plain English. **Mcp Get Issue** > Use Pylon to mcp get issue and walk me through the result in plain English. **Mcp Get Issue Messages** > Use Pylon to mcp get issue messages 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 Pylon working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Pylon app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Pylon 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 Pylon. | 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 Pylon actions to the runtime in a format your agent can reliably use. | 12 tools for Pylon are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Pylon 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 Pylon in the browser, and the 12 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 Pylon skill but can't call the tools The ClawHub skill teaches OpenClaw about Pylon, but the calls run through the ClawLink plugin and your connected account. Make sure Pylon 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 Pylon 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 Pylon tools Pylon 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 Pylon 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. ### Pylon 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 Pylon 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 Pylon integration? Yes. ClawLink is the fastest way to connect OpenClaw to Pylon: link your Pylon account once in the browser and OpenClaw can call the Pylon API through 12 ready-made tools — no custom code or token handling. ### How do I add Pylon to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Pylon skill from ClawHub, then you click Connect in the dashboard to authorize Pylon. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Pylon to OpenClaw? About two minutes. Sign in, click Connect next to Pylon in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Pylon 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 Pylon working from chat. ### OpenClaw installed the Pylon skill but can't call the tools The ClawHub skill teaches OpenClaw about Pylon, but the calls run through the ClawLink plugin and your connected account. Make sure Pylon 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 Zendesk](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [OpenClaw Gleap integration](https://claw-link.dev/openclaw/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points. - [Connect Freshdesk](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations