# How to connect Request Tracker (RT) to OpenClaw (paste one key, 11 tools) > Connect Request Tracker (RT) to OpenClaw with ClawLink: paste your Request Tracker (RT) 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/request-tracker The usual route to Request Tracker (RT) 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 Request Tracker (RT) setup: install one ClawHub skill, connect Request Tracker (RT) in the browser, and OpenClaw can call real Request Tracker (RT) 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 Request Tracker (RT). 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Request Tracker (RT)** — 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 request-tracker # connect Request Tracker (RT) (browser OAuth) npx -y @useclawlink/cli actions request-tracker # list available actions npx -y @useclawlink/cli run request-tracker --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 Request Tracker (RT) in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Request Tracker (RT) API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Request Tracker (RT), 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 Request Tracker (RT) is connected in the dashboard, that agent calls the same 11 Request Tracker (RT) 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). ## Request Tracker (RT) MCP for OpenClaw Looking for a Request Tracker (RT) MCP server for OpenClaw? ClawLink connects Request Tracker (RT) to OpenClaw and exposes 11 Request Tracker (RT) 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 Request Tracker (RT) integration](https://claw-link.dev/hermes/request-tracker) works the same way. ## What the OpenClaw Request Tracker (RT) integration can do 11 Request Tracker (RT) tools are ready for OpenClaw once the account is connected. ### All 11 Request Tracker (RT) tools for OpenClaw | Tool | What it does | |---|---| | **Get queue** `request_tracker_get_queue` | Retrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive | | **Get ticket** `request_tracker_get_ticket` | Retrieve one visible RT ticket, including its current fields and capability-sensitive links for | | **Get ticket history** `request_tracker_get_ticket_history` | Return one page of detailed ticket history, including transaction types, field changes | | **List queues** `request_tracker_list_queues` | List queues visible to the connected RT user so an agent can select a queue for ticket search | | **List ticket attachments** `request_tracker_list_ticket_attachments` | List attachment metadata references associated with a visible RT ticket without downloading | | **Search tickets** `request_tracker_search_tickets` | Search visible RT tickets with an explicit TicketSQL expression and return one bounded page | | **Search users** `request_tracker_search_users` | Search RT users with structured field conditions and return one bounded page of user references | | **Create ticket** `request_tracker_create_ticket` | Create a durable RT ticket in a queue | | **Update ticket** `request_tracker_update_ticket` | Update selected metadata on an existing RT ticket and verify every requested field by reading | | **Add ticket comment** `request_tracker_add_ticket_comment` | Add a private internal comment to an RT ticket | | **Reply to ticket** `request_tracker_reply_to_ticket` | Send public correspondence on an RT ticket | ## Example prompts **Get Queue** > Pull the relevant data from Request Tracker (RT), summarize it in plain English, and point out anything that needs attention. **Get Ticket** > Pull the relevant data from Request Tracker (RT), summarize it in plain English, and point out anything that needs attention. **Get Ticket History** > Pull the relevant data from Request Tracker (RT), summarize it in plain English, and point out anything that needs attention. **List Queues** > List the relevant items in Request Tracker (RT), 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 Request Tracker (RT) working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Request Tracker (RT) API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Request Tracker (RT) 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 Request Tracker (RT). | 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 Request Tracker (RT) actions to the runtime in a format your agent can reliably use. | 11 tools for Request Tracker (RT) are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Request Tracker (RT) 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 Request Tracker (RT) in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Request Tracker (RT) 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 Request Tracker (RT) skill but can't call the tools The ClawHub skill teaches OpenClaw about Request Tracker (RT), but the calls run through the ClawLink plugin and your connected account. Make sure Request Tracker (RT) 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 Request Tracker (RT) 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 Request Tracker (RT) tools Request Tracker (RT) 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 Request Tracker (RT) 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. ### Request Tracker (RT) 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 Request Tracker (RT) has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Request Tracker (RT) integration? Yes. ClawLink is the fastest way to connect OpenClaw to Request Tracker (RT): link your Request Tracker (RT) account once in the browser and OpenClaw can call the Request Tracker (RT) API through 11 ready-made tools — no custom code or token handling. ### How do I add Request Tracker (RT) to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Request Tracker (RT) skill from ClawHub, then you click Connect in the dashboard to authorize Request Tracker (RT). OpenClaw calls the tools from the next message — no config files, and the Request Tracker (RT) key you paste is stored server-side instead of in your environment. ### How long does it take to connect Request Tracker (RT) to OpenClaw? About two minutes. Sign in, click Connect next to Request Tracker (RT) in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Request Tracker (RT) 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 Request Tracker (RT) working from chat. ### OpenClaw installed the Request Tracker (RT) skill but can't call the tools The ClawHub skill teaches OpenClaw about Request Tracker (RT), but the calls run through the ClawLink plugin and your connected account. Make sure Request Tracker (RT) 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 Zendesk integration](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