Skip to main content

How it works

Connecting Intercom brings your support conversations into the Context Graph. Each Intercom conversation is stored as a support ticket with its message thread, linked to the same people and accounts as your CRM, calls, email, and Slack. Once connected, Claude, ChatGPT, Cursor, Grok Bot, and your workflows can answer questions like “what’s open in support for this account?” with the conversations behind the answer. The connection is read-only. Clearskies never writes back to Intercom.

What you’ll need

  • Clearskies admin access. Only admins can connect or disconnect Intercom.
  • An Intercom access token from a private app in the Intercom Developer Hub, in the Intercom workspace you want to connect.
Any Intercom data region works (US, EU, or AU). Clearskies detects the region automatically.

Setup steps

1. Create an access token in Intercom

In Intercom, open the Developer Hub and create a private app in the workspace you want to connect, or use an existing one. Copy the app’s access token.

2. Open Context Graph in Clearskies

Log in to Clearskies and navigate to Context Graph from the main navigation.

3. Connect Intercom

Find Intercom and click Connect.

4. Paste your access token

Paste the access token and save. Clearskies checks the token with Intercom and shows the Intercom workspace it’s connected to. If you see an error:
  • “Invalid Intercom access token”: Intercom rejected the token. Copy it again from the Developer Hub, or create a new one.
  • “Intercom could not be reached to verify the token. Please try again shortly.”: Intercom was unavailable. Wait a moment and try again.

5. Let the first import run

Clearskies starts importing your full Intercom conversation history right away, oldest first. Large workspaces can take a while. After the first import, Clearskies picks up new and updated conversations about every 15 minutes.

What syncs

These are not imported:
  • Internal notes
  • Assignments, closes, and snoozes with no message text (these update the ticket’s state instead)
  • Intercom companies
  • Full contact profiles and custom contact attributes
  • Attachments
Tickets link to people by email address, and to accounts by the email domain of those people. Intercom companies are not used for matching.

Example prompts

  • “What’s open in support for Acme Robotics right now?”
  • “Summarize Northwind’s last 30 days of Intercom conversations before my QBR.”
  • “List unassigned support tickets that haven’t been updated in 7 days.”
  • “Which of my renewal accounts have an open high-priority support conversation?”
  • “Did the customer mention pricing in any support chat this quarter?”

Good to know

  • Everything the token can see is imported. You can’t limit the connection to specific inboxes or teams.
  • One Intercom workspace per Clearskies workspace. Connecting again with a new token replaces the old one.
  • Freshness: changes usually appear within 15 to 20 minutes, longer during the first import or when Intercom limits request rates.
  • Very long conversations are cut off. Intercom returns at most 500 parts per conversation, so later messages in longer threads are not imported.
  • To disconnect, go to Context Graph, select Intercom, and click Disconnect.

You’re all set

Your Intercom conversations are now part of your Context Graph, alongside your other connected sources. Questions? Reach out at support@clearskies.cc