Customer conversations are a record; an agent should read them, not edit them. Help Centre articles are content; an agent drafting and updating those is exactly the useful case. Intercom's required scopes encode that distinction rather than leaving it to policy. Contact lookup accepting a custom attribute is the practical detail — most support questions start from an identifier that is not an email.
Intercom's own endpoint, with a separate EU address for EU-region accounts. Thirteen tools: a generic search-and-fetch pair plus specific ones for conversations, contacts, companies and Help Centre content.
- A DSL search and fetch pair for general retrieval
- Advanced conversation search, and reading one conversation in full
- Contact lookup by id, name, email, phone or custom attribute
- Company listing and detail
- Help Centre articles: list, search, read, create and update
OAuth in the browser, or a bearer access token. The permissions needed are read on users and companies, read on conversations, and read-write on articles. Their SSE endpoint is deprecated.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen