# How to connect Productlane to OpenClaw (paste one key, 39 tools) > Connect Productlane to OpenClaw with ClawLink: paste your Productlane key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/productlane The usual route to Productlane 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 Productlane setup: install one ClawHub skill, connect Productlane in the browser, and OpenClaw can call real Productlane 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 Productlane. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Productlane** — 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 productlane # connect Productlane (browser OAuth) npx -y @useclawlink/cli actions productlane # list available actions npx -y @useclawlink/cli run productlane --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 Productlane in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Productlane API key once. Verify the connection by asking OpenClaw: > Use Productlane to enable widget 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 Productlane is connected in the dashboard, that agent calls the same 39 Productlane 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). ## Productlane MCP for OpenClaw Looking for a Productlane MCP server for OpenClaw? ClawLink connects Productlane to OpenClaw and exposes 39 Productlane 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 Productlane integration](https://claw-link.dev/hermes/productlane) works the same way. ## What the OpenClaw Productlane integration can do 39 Productlane 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 39. ### 30 of 39 Productlane tools for OpenClaw | Tool | What it does | |---|---| | **Enable widget** `productlane_enable_widget` | Enable the Productlane widget | | **Get changelog** `productlane_get_changelog` | Retrieve a published changelog by ID from Productlane | | **Get company** `productlane_get_company` | Retrieve a company by its unique ID | | **Get contact** `productlane_get_contact` | Retrieve a contact by ID or email from Productlane | | **Get help center article** `productlane_get_help_center_article` | Retrieve a help center article by its ID | | **Get insight** `productlane_get_insight` | Retrieve an insight/thread by its ID | | **Get issue** `productlane_get_issue` | Retrieve a specific issue by its ID from a workspace | | **Get linear options** `productlane_get_linear_options` | Retrieve available Linear customer statuses and tiers for your workspace | | **Get project** `productlane_get_project` | Retrieve a project by its ID from a workspace | | **Get workspace** `productlane_get_workspace` | Fetch workspace details by ID | | **List changelogs** `productlane_list_changelogs` | List all published changelogs for a workspace by ID | | **List companies** `productlane_list_companies` | List all companies in Productlane | | **List contacts** `productlane_list_contacts` | Retrieve all contacts for your workspace | | **List help center articles** `productlane_list_help_center_articles` | List all help center articles for a specific workspace | | **List insights** `productlane_list_insights` | List all threads/insights for your workspace with optional filtering | | **List issues** `productlane_list_issues` | Retrieve all issues from a Productlane workspace | | **List members** `productlane_list_members` | Retrieve all members of your workspace with their roles and user information | | **List projects** `productlane_list_projects` | Retrieve all projects within a workspace | | **Widget close** `productlane_widget_close` | Close the Productlane widget | | **Widget disable** `productlane_widget_disable` | Disable the Productlane widget across the entire page | | **Widget off event** `productlane_widget_off_event` | Remove a previously registered widget event listener | | **Widget on event** `productlane_widget_on_event` | Register a listener for Productlane widget events | | **Widget open** `productlane_widget_open` | Generate a JavaScript snippet that opens the Productlane widget | | **Widget open docs** `productlane_widget_open_docs` | Open a specific docs article in the Productlane widget | | **Widget toggle** `productlane_widget_toggle` | Toggle the Productlane widget between open and closed states | | **Create changelog** `productlane_create_changelog` | Create a new changelog entry in Productlane | | **Create company** `productlane_create_company` | Create a new company in Productlane | | **Create contact** `productlane_create_contact` | Create a new contact in your Productlane workspace with optional company linking | | **Create feedback** `productlane_create_feedback` | Create new feedback in Productlane | | **Create insight** `productlane_create_insight` | Create a new insight/thread in Productlane workspace | ## Example prompts **Enable Widget** > Use Productlane to enable widget and walk me through the result in plain English. **Get Changelog** > Pull the relevant data from Productlane, summarize it in plain English, and point out anything that needs attention. **Get Company** > Pull the relevant data from Productlane, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Productlane, 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 Productlane working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Productlane API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Productlane 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 Productlane. | 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 Productlane actions to the runtime in a format your agent can reliably use. | 39 tools for Productlane are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Productlane 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 Productlane in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Productlane 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 Productlane skill but can't call the tools The ClawHub skill teaches OpenClaw about Productlane, but the calls run through the ClawLink plugin and your connected account. Make sure Productlane 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 Productlane 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 Productlane tools Productlane 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 Productlane 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. ### Productlane 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 Productlane has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Productlane integration? Yes. ClawLink is the fastest way to connect OpenClaw to Productlane: link your Productlane account once in the browser and OpenClaw can call the Productlane API through 39 ready-made tools — no custom code or token handling. ### How do I add Productlane to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Productlane skill from ClawHub, then you click Connect in the dashboard to authorize Productlane. OpenClaw calls the tools from the next message — no config files, and the Productlane key you paste is stored server-side instead of in your environment. ### How long does it take to connect Productlane to OpenClaw? About two minutes. Sign in, click Connect next to Productlane in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Productlane 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 Productlane working from chat. ### OpenClaw installed the Productlane skill but can't call the tools The ClawHub skill teaches OpenClaw about Productlane, but the calls run through the ClawLink plugin and your connected account. Make sure Productlane 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 - [Zendesk](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [Gleap](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. - [OpenClaw Freshdesk integration](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations