Skip to main content
The Intercom tool covers 48 endpoints for inbox conversations, contacts, companies, tags, notes, admins, teams and help center articles. Its key is intercom.

Connect

TypeScript
This is what ancha connect intercom --lang ts prints.

Endpoints

Unsupported features on listed routes return HTTP 400 in Intercom’s error shape. Unknown routes return HTTP 404. Both carry x-ancha-gap: 1. The client retries 5xx responses, so these errors use 4xx responses.

Starter data

The starter data is the Acme workspace. Your agent acts as Ancha assistant, ancha@acme.example. Run ancha twins seed intercom --full to print the complete starter data and the scene seed fields.

Checks

Intercom has no state checks. Use trace checks, for example { called: "POST /conversations/*/reply" } or { not_called: "DELETE /contacts/*" }.

Limits

  • Tickets, outbound messages, data events, segments, subscriptions and AI agent fields are gaps.
  • Replies support admin comments, internal notes and contact replies. Quick replies and attachments are gaps.
  • Contact custom attributes must already exist in the workspace.
  • Article collections and translations, bulk tagging of companies and users, and conversation ratings and statistics are gaps.