Intercom's API provides access to conversations, contacts, and analytics data. Connecting it to OpenClaw lets your support and success team get conversation context and inbox status from Slack.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Intercom — it's considerably more involved.
Connecting OpenClaw with Intercom: Step by Step
Step 1: Create an Intercom Access Token
Go to app.intercom.com/developers, create a new app, and generate an access token with the scopes you need (Conversations read, Contacts read at minimum). Use this as a Bearer token for all API requests to https://api.intercom.io.
Step 2: Use the Search Conversations Endpoint
The /conversations/search endpoint accepts structured queries — filter by state (open, closed, snoozed), assignee, tag, and more. For contact history, the /contacts/{id}/conversations endpoint returns all conversations for a specific customer.
Step 3: Build the Proxy and Skill File
Build your proxy around conversation search and contact lookup. Write ~/.openclaw/skills/intercom.md with your team's tag names and assignment team names — Intercom uses human-readable labels that Claude can work with directly.
Challenges and Caveats
Rate Limits Are Strict on Lower Plans
Intercom's API rate limits are 500–1000 requests per minute depending on plan. Conversation search can involve multiple paginated requests for large inboxes. Cache results where possible.
Conversation History Has Pagination
Long conversation threads are paginated. If a customer has been in contact many times, your proxy may need to handle cursor-based pagination to retrieve the full history.
Skip All of This — Use Cody Instead
Cody has Intercom integration built in. Get conversation context and inbox health in Slack without access token setup.
Related Guides
- Connecting OpenClaw with Zendesk: A Practical Guide
- Connecting OpenClaw with Freshdesk: A Practical Guide
- Connecting OpenClaw with Hubspot: A Practical Guide
Need the model-flexible version? See: How to Connect Intercom to OpenClaw: Setup, Models, and Workflow Guide.