# How to connect Gleap to OpenClaw (paste one key, 179 tools) > Connect Gleap to OpenClaw with ClawLink: paste your Gleap key once and 179 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/gleap The usual route to Gleap 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 Gleap setup: install one ClawHub skill, connect Gleap in the browser, and OpenClaw can call real Gleap 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/gleap ## Setup It takes three steps to connect OpenClaw to Gleap. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Gleap** — 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 gleap # connect Gleap (browser OAuth) npx -y @useclawlink/cli actions gleap # list available actions npx -y @useclawlink/cli run gleap --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 Gleap in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Gleap API key once. Verify the connection by asking OpenClaw: > Before using Gleap to archive a ticket, show me what will change and ask for confirmation. ### 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 Gleap is connected in the dashboard, that agent calls the same 179 Gleap 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). ## Gleap MCP for OpenClaw Looking for a Gleap MCP server for OpenClaw? ClawLink connects Gleap to OpenClaw and exposes 179 Gleap 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 Gleap integration](https://claw-link.dev/hermes/gleap) works the same way. ## What the OpenClaw Gleap integration can do 179 Gleap 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 179. ### 30 of 179 Gleap tools for OpenClaw | Tool | What it does | |---|---| | **Archive a ticket** `gleap_archive_a_ticket` | Archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history. | | **Archive all tickets** `gleap_archive_all_tickets` | Archive all tickets matching specific type and status criteria | | **Clone engagement** `gleap_clone_engagement` | Clone an existing engagement | | **Create a collection** `gleap_create_a_collection` | Create a help center collection | | **Export sessions** `gleap_export_sessions` | Export sessions for the authenticated project in CSV format | | **Export statistics lists** `gleap_export_statistics_lists` | Export statistics list data as CSV from Gleap | | **Generate ticket draft reply** `gleap_generate_ticket_draft_reply` | Generate an AI-powered draft reply for a ticket | | **Generate tracker ticket data** `gleap_generate_tracker_ticket_data` | Generate AI-powered tracker ticket data from an existing ticket | | **Get a checklist action** `gleap_get_a_checklist_action` | Retrieve a specific engagement checklist by its ID | | **Get a collection** `gleap_get_a_collection` | Retrieve a help center collection by ID | | **Get a ticket** `gleap_get_a_ticket` | Retrieves complete details for a specific ticket by its ID | | **Get AI content** `gleap_get_ai_content` | Retrieve AI content by its content ID | | **Get all articles** `gleap_get_all_articles` | Retrieve articles in a help center collection | | **Get all chat messages** `gleap_get_all_chat_messages` | Retrieves all engagement chat messages from the current Gleap project | | **Get all collections** `gleap_get_all_collections` | Retrieves all help center collections for the authenticated project | | **Get all invitations for a project** `gleap_get_all_invitations_for_a_project` | Retrieves all pending invitations for a project | | **Get all sessions** `gleap_get_all_sessions` | Retrieves all user sessions for the authenticated project | | **Get all teams** `gleap_get_all_teams` | Retrieve all teams | | **Get all tickets** `gleap_get_all_tickets` | Retrieve tickets from a Gleap project with optional filtering, sorting, and pagination | | **Get all users for a project** `gleap_get_all_users_for_a_project` | Retrieve all users for a project | | **Get current user** `gleap_get_current_user` | Retrieves the authenticated user's profile including email, name, user type, availability | | **Get engagement activities count** `gleap_get_engagement_activities_count` | Retrieve the count of activities for a specific engagement | | **Get engagement banner** `gleap_get_engagement_banner` | Retrieve an engagement banner by its ID | | **Get engagement banners** `gleap_get_engagement_banners` | Retrieve all engagement banners from a Gleap project | | **Get engagement chat message** `gleap_get_engagement_chat_message` | Retrieves a specific engagement chat message by its ID | | **Get engagement checklists** `gleap_get_engagement_checklists` | Retrieve all engagement checklists for a project | | **Get engagement cobrowse** `gleap_get_engagement_cobrowse` | Retrieves all cobrowse product tours for the authenticated project | | **Get engagement cobrowse by ID** `gleap_get_engagement_cobrowse_by_id` | Retrieve a specific cobrowse product tour by its ID | | **Get engagement email** `gleap_get_engagement_email` | Retrieves a specific engagement email by its ID | | **Get engagement emails** `gleap_get_engagement_emails` | Retrieve all engagement emails from a Gleap project | ## Example prompts **Archive A Ticket** > Before using Gleap to archive a ticket, show me what will change and ask for confirmation. **Archive All Tickets** > Before using Gleap to archive all tickets, show me what will change and ask for confirmation. **Clone Engagement** > Use Gleap to clone engagement and walk me through the result in plain English. **Create A Collection** > Create it in Gleap for me, then confirm the important fields before you finish. ## 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 Gleap working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Gleap API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Gleap 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 Gleap. | 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 Gleap actions to the runtime in a format your agent can reliably use. | 179 tools for Gleap are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Gleap 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 Gleap in the browser, and the 179 tools above work from chat. There is no SDK and no config file, and the Gleap 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 Gleap skill but can't call the tools The ClawHub skill teaches OpenClaw about Gleap, but the calls run through the ClawLink plugin and your connected account. Make sure Gleap 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 Gleap 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 Gleap tools Gleap 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 Gleap 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. ### Gleap 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 Gleap has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Gleap integration? Yes. ClawLink is the fastest way to connect OpenClaw to Gleap: link your Gleap account once in the browser and OpenClaw can call the Gleap API through 179 ready-made tools — no custom code or token handling. ### How do I add Gleap to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Gleap skill from ClawHub, then you click Connect in the dashboard to authorize Gleap. OpenClaw calls the tools from the next message — no config files, and the Gleap key you paste is stored server-side instead of in your environment. ### How long does it take to connect Gleap to OpenClaw? About two minutes. Sign in, click Connect next to Gleap in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Gleap 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 Gleap working from chat. ### OpenClaw installed the Gleap skill but can't call the tools The ClawHub skill teaches OpenClaw about Gleap, but the calls run through the ClawLink plugin and your connected account. Make sure Gleap 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 tools](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [Connect Freshdesk](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations - [Intercom](https://claw-link.dev/openclaw/intercom) — Manage conversations, contacts, companies, and support articles