Resources · Claude connector

Claude Intercom connectorWhat Claude can do in your Intercom account.

The Claude Intercom connector exposes 6 tools, and all 6 read. 0 of them change anything in your workspace and none is undocumented. Below: what Claude pulls from conversations and contacts, how to plug it in, who can switch it off, and why Intercom's docs list more tools.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can read your Intercom inbox

Your support history stops being something only the support team can dig through. A product manager, a salesperson before a renewal call or a founder preparing a board review can ask Claude a plain question and get an answer built from real customer conversations, with links back to the records in Intercom.

Spot the bug everyone keeps reporting. Claude runs search across conversations, narrows with search_conversations by state, channel or assignee, then opens the relevant threads with get_conversation to summarize what customers actually wrote.

Walk into a customer call prepared. With search_contacts and get_contact, Claude finds the person by email or company domain and reads their custom attributes, location and activity dates before you dial.

Prepare a quarterly review from what customers actually said. fetch returns the full detail of a conversation or contact found earlier, including a direct link to open it in Intercom.

Now what the connector does not do. Its directory sheet lists no tool that replies to a customer, closes a conversation or edits a contact: by default, what it exposes is reading. Nothing fires on its own either; Claude only calls these tools while it is answering you. If you need a reply to go out when a ticket lands, that is an automation job, and our Intercom n8n integration and Intercom Make integration pages cover that side. They do a different job from Claude, not a better or worse one.

Vocabulary

Five words to know before you connect

The vocabulary around this connector, in one minute.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
Tool
One named action a connector gives Claude. Claude chooses the tools it needs by itself, and the directory lists each by name.
Authorization
Intercom's own sign-in and consent screens, where you hand Claude its access. Granted once per person, and it can be withdrawn.
Approval
The confirmation Claude waits for in the conversation before it does something that would change an account for you.
MCP
The open standard connectors are built on: the piece that lets an assistant like Claude talk to an outside service such as Intercom.
Connect

Connect Intercom to Claude in three steps

  1. 01

    Find Intercom in your connectors

    Open Claude's settings, go to Customize then Connectors, and look for Intercom in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before anyone can sign in.

  2. 02

    Start the connection

    Click Connect on the Intercom row, then log in to your Intercom workspace in the window Intercom opens itself. If the link breaks later, click Disconnect and connect again from the same row.

  3. 03

    Read the consent screen, then accept

    Intercom shows its own screen listing what the application will be able to do in your workspace. That screen, not Claude, sets the scope of the access. You can also withdraw the access later from the Intercom side.

Tools

The 6 tools, all on the reading side

Intercom gives Claude 6 tools: 6 that read your account, 0 that change something in it.

Every tool on the directory sheet reads data and leaves your workspace as it was. Tool names stay exactly as Claude displays them.

  • 6 read

What Claude reads (6)

6 tools

Six tools that look up conversations and contacts without changing them.

fetch

Takes an item found earlier and returns complete detailed information about it, plus a direct link to open it in Intercom.

When it helps
a search surfaced a promising thread and you want the full exchange, with the link to share, before quoting it to engineering.

Sourcedevelopers.intercom.com · September 30, 2026 ↗

search_conversations

Filters conversations more finely: by source type, author details, state, the team or teammate it is assigned to, and timing statistics.

When it helps
a support lead wants the open conversations assigned to one team, with their timing figures, to see where customers waited longest.

Sourcedevelopers.intercom.com · September 30, 2026 ↗

get_conversation

Opens a single conversation by its identifier and brings back the whole thread with its metadata, so Claude can read the customer's words rather than a summary.

When it helps
a customer escalates and you need the history of that one ticket before you reply yourself.

Sourcedevelopers.intercom.com · September 30, 2026 ↗

search_contacts

Looks up people in your workspace by name, email, phone, email domain or custom attribute, with flexible matching when you only half remember the details.

When it helps
an account manager wants every contact at a client domain ahead of a renewal meeting.

Sourcedevelopers.intercom.com · September 30, 2026 ↗

get_contact

Returns the full profile of one person: custom attributes, location and the timestamps of their activity.

When it helps
you want to know when a trial user was last active before you follow up.
Watch out
Claude only sees the profiles your own Intercom permissions already let you open.

Sourcedevelopers.intercom.com · September 30, 2026 ↗

Approvals

What Claude asks before it acts

With a sheet made only of reading tools, the approval question is mostly about who can open or close the door.

By default, Claude stops and asks for your confirmation before any action that would change an account on your behalf. No source describes a confirmation specific to Intercom, and the six listed tools only read. Claude also works with your rights and nothing more: a conversation or contact you cannot open in Intercom stays out of its reach. On a Team or Enterprise workspace, owners can limit what the connector may do for the whole organization, for example reading only, and members cannot override that from their own account.

Plans

Which plans include the Intercom connector

None of the 819 directory sheets states its availability by plan, so there is no connector-by-connector answer anywhere, for Intercom or any other.

What Anthropic does publish is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization first. For the live state of Intercom on your account, its sheet in the official directory is the only reference worth checking.

Limits

What the Intercom connector will not do

This connector is documented by its publisher only: no Claude help article or Anthropic developer page covers it, so the limits below come from Intercom.

A sheet that only shows reading tools is a floor you can observe, not a promise: an administrator can open more than what any public page lists. The directory's verification badge is not a security audit either, and Anthropic says on every sheet that it does not choose the tools a publisher exposes. Here the publisher is Intercom itself. And nothing is automatic: no tool fires when a new conversation arrives.

Two official sources disagree

How many tools does Claude really get on Intercom, and can it write?

  • Directory sheet ↗September 2026Six tools are listed, all for reading conversations and contacts.
  • Intercom developer docs ↗September 2026Intercom's server offers more tools than the sheet, including creating and updating help center articles and adding internal notes to conversations.

What this page followsBoth are accurate on their own terms: Intercom describes its whole server, the directory shows what it exposes for Claude. This page follows the directory, six reading tools, as an observed floor, and does not claim the writes are gone. Check the tool list in the connector settings on your own account.

Need help

Need help connecting Intercom to Claude?

A person reads every message.

FAQ

Questions about the Claude Intercom connector

01What can Claude do with the Intercom connector?
Claude can search and read your Intercom conversations and contacts while it answers you. The directory lists six tools: a general search, a detailed fetch, a finer conversation search, opening one conversation, a contact search and opening one contact profile. That covers questions like which bugs customers mention most, what a given account said last month, or when a trial user was last active. You ask in plain words, Claude picks the tools, and the answer links back to the records in Intercom.
02Can Claude reply to customers or change data in Intercom?
Not through the tools the directory lists today: all six read, and none of them replies to a customer, closes a conversation or edits a contact. Treat that as a floor rather than a guarantee. Intercom's own developer documentation describes a larger server, with tools that create and update help center articles and add internal notes to conversations. If your account shows more tools in the connector settings, those are the ones that actually apply to you, and the approval rules cover them.
03Does Claude ask before it does something in Intercom?
By default, Claude asks for confirmation before any action that would change an account on your behalf, and the request appears right in the conversation. With Intercom, the listed tools only read, so searches and lookups simply run as part of the answer. On Team and Enterprise workspaces, owners decide whether members may let certain actions skip the prompt. They can also restrict the connector to reading for the whole organization, and nobody can lift that restriction from their own account.
04Which plans is the Intercom connector available on?
No official source publishes plan availability connector by connector, and none of the directory sheets shows it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can each sign in. The Intercom sheet in the official directory is the only place that shows the current state for your own account.
05Can Claude see every conversation in our workspace?
No. Claude works with the rights of the person who connected it and nothing more, so it only reaches the conversations and contacts that person can already open in Intercom. Two teammates asking the same question may get different answers if their Intercom permissions differ. On Team and Enterprise workspaces, owners can also narrow what the connector may do for everyone, and that setting applies across the organization whatever each member would prefer.
06Why does the connection fail for our Intercom workspace?
Check the hosting region first. Intercom supports workspaces hosted in the US and in the EU, and workspaces hosted in Australia are not supported yet. Intercom's developer page lists two other snags: the consent page expires after 15 minutes, and only one connection can be pending per browser. If clicking Allow shows an authorization error, start the connection again from the connector row in Claude, in a single tab, and complete the consent before it times out.
07Should I use Claude or an automation tool with Intercom?
They do different jobs, so the right choice depends on the task. Claude reads your conversations and contacts when you ask a question, which suits research, preparing a customer call or a quarterly review. An automation tool runs on its own when something happens, such as a new conversation arriving, and can act without anyone sitting in a chat. Nothing stops you from using both: Claude to understand what customers say, an automated workflow to react to it.