# How to connect Intercom to OpenClaw (no API keys) > Connect Intercom to OpenClaw with ClawLink in one click — 133 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/intercom The usual route to Intercom 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 Intercom setup: install one ClawHub skill, connect Intercom in the browser, and OpenClaw can call real Intercom 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/intercom ## Setup It takes three steps to connect OpenClaw to Intercom. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Intercom** — 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 intercom # connect Intercom (browser OAuth) npx -y @useclawlink/cli actions intercom # list available actions npx -y @useclawlink/cli run intercom --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 Intercom in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Intercom to add tag to contact 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 Intercom is connected in the dashboard, that agent calls the same 133 Intercom 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). ## Intercom MCP for OpenClaw Looking for a Intercom MCP server for OpenClaw? ClawLink connects Intercom to OpenClaw and exposes 133 Intercom 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 Intercom integration](https://claw-link.dev/hermes/intercom) works the same way. ## What the OpenClaw Intercom integration can do 133 Intercom 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 133. ### 30 of 133 Intercom tools for OpenClaw | Tool | What it does | |---|---| | **Add tag to contact** `intercom_add_tag_to_contact` | Add a tag to a contact in Intercom | | **Assign conversation** `intercom_assign_conversation` | Assign a conversation to an admin or team | | **Attach contact to company** `intercom_attach_contact_to_company` | Attach a contact to a company in Intercom | | **Close conversation** `intercom_close_conversation` | Close a conversation in Intercom | | **Create an article** `intercom_create_an_article` | Create a new article in Intercom | | **Create contact** `intercom_create_contact` | Create a new contact in Intercom | | **Create conversation** `intercom_create_conversation` | Create a new conversation in Intercom | | **Create data event** `intercom_create_data_event` | Submit a data event to Intercom | | **Download data export** `intercom_download_data_export` | Download content data export from Intercom | | **Find tag** `intercom_find_tag` | Retrieve details for a specific tag by its ID | | **Get a contact** `intercom_get_a_contact` | You can fetch the details of a single contact | | **Get content import source** `intercom_get_content_import_source` | Retrieve a content import source by its ID | | **Get conversation** `intercom_get_conversation` | Retrieves a specific conversation by ID with all messages and details | | **Get counts** `intercom_get_counts` | Retrieve summary counts for Intercom app entities including companies, users, leads, tags | | **Get custom object instance by external ID** `intercom_get_custom_object_instance_by_external_id` | Retrieve a custom object instance by its external_id | | **Get external page** `intercom_get_external_page` | Retrieve an external page from Fin Content Library by ID | | **Get ticket** `intercom_get_ticket` | Retrieve a ticket from Intercom | | **Get ticket type** `intercom_get_ticket_type` | Retrieve details for a specific ticket type by its ID | | **Identify an admin** `intercom_identify_an_admin` | You can view the currently authorised admin along with the embedded app object (a "workspace" | | **Jobs status** `intercom_jobs_status` | Retrieve the status of job execution | | **List all activity logs** `intercom_list_all_activity_logs` | You can get a log of activities by all admins in an app | | **List all admins** `intercom_list_all_admins` | You can fetch a list of admins for a given workspace | | **List all articles** `intercom_list_all_articles` | You can fetch a list of all articles by making a GET request to | | **List all collections** `intercom_list_all_collections` | You can fetch a list of all collections by making a GET request to | | **List all companies** `intercom_list_all_companies` | You can list companies | | **List all help centers** `intercom_list_all_help_centers` | You can list all Help Centers by making a GET request to | | **List all macros** `intercom_list_all_macros` | Fetch a list of all macros (saved replies) in your workspace for use in automating responses | | **List all notes** `intercom_list_all_notes` | You can fetch a list of notes that are associated to a contact | | **List attached companies for contact** `intercom_list_attached_companies_for_contact` | You can fetch a list of companies that are associated to a contact | | **List attached contacts** `intercom_list_attached_contacts` | You can fetch a list of all contacts that belong to a company | ## Example prompts **Add Tag To Contact** > Use Intercom to add tag to contact and walk me through the result in plain English. **Assign Conversation** > Use Intercom to assign conversation and walk me through the result in plain English. **Attach Contact To Company** > Use Intercom to attach contact to company and walk me through the result in plain English. **Close Conversation** > Use Intercom to close conversation 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 Intercom working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Intercom app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Intercom 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 Intercom. | 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 Intercom actions to the runtime in a format your agent can reliably use. | 133 tools for Intercom are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Intercom 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 Intercom in the browser, and the 133 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 Intercom skill but can't call the tools The ClawHub skill teaches OpenClaw about Intercom, but the calls run through the ClawLink plugin and your connected account. Make sure Intercom 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 Intercom 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 Intercom tools Intercom 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 Intercom 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. ### Intercom 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 Intercom 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 Intercom integration? Yes. ClawLink is the fastest way to connect OpenClaw to Intercom: link your Intercom account once in the browser and OpenClaw can call the Intercom API through 133 ready-made tools — no custom code or token handling. ### How do I add Intercom to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Intercom skill from ClawHub, then you click Connect in the dashboard to authorize Intercom. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Intercom to OpenClaw? About two minutes. Sign in, click Connect next to Intercom in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Intercom 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 Intercom working from chat. ### OpenClaw installed the Intercom skill but can't call the tools The ClawHub skill teaches OpenClaw about Intercom, but the calls run through the ClawLink plugin and your connected account. Make sure Intercom 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. - [Freshdesk tools](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations