Intercom integration
Turn your Intercom conversations into a ranked problem list
Connect your Intercom workspace once and the conversations your customers open flow in on their own — grouped by meaning into the problems worth fixing, with a clear before/after every time you run.
What you get
What GliddeSignal pulls from Intercom
Customer-started conversations pulled via the Intercom API
Synced daily, or pulled on demand with Sync now
Outbound messages your team sends are skipped — only your customers' words count
Your Access Token is encrypted at rest and never returned to the browser
You choose how many conversations a batch collects, from 10 to 5,000
Before you start
What connecting Intercom takes
Set up once on your project's Integrations tab: paste an Access Token.
What you'll need: An Access Token from a private app in your workspace's Developer Hub, and your data region.
Where the steps are: the guide inside the app, field by field.
The detail
What it touches, and how to turn it off
Everything Intercom can and can't see, stated plainly — what it reads, what it writes, and how to disconnect it.
What it reads
The conversations your customers open, newest first, via the Intercom REST API — each one's opening message (subject and body) only. It does not read the reply thread, your team's notes, or attachments, and it never reads a conversation your team started.
What it writes
Nothing. This connection is read-only.
How much, how often
You set the batch size — anywhere from 10 to 5,000 conversations, defaulting to 200. It syncs once a day at 07:00 UTC, plus whenever you press Sync now. A conversation you've already run is never pulled in twice.
Whose messages
Only conversations a customer started. Ones opened by a teammate or a bot — outbound campaigns, proactive messages, automated replies — are skipped on purpose: they are your words, not your customers', and analyzing them would put your own support copy in the problem list.
How it authenticates
An Access Token from a private app you create in your workspace's Developer Hub — a one-off copy, no OAuth round trip, no expiry to manage. It needs permission to read conversations and nothing else.
Your data region
Intercom hosts each workspace in one of three regions — US, EU or Australia — and a token only works against its own region's API. You pick the region when you connect; a correctly copied token with the wrong region is refused exactly like a bad one, so that is the first thing to check if a connect fails. Your address bar tells you: app.intercom.com is US, app.eu.intercom.com is EU, app.au.intercom.com is Australia.
Credential handling
Your Access Token is encrypted before storage and never returned to the browser. We validate it on save against Intercom's own /me endpoint, so a wrong token or region fails immediately instead of silently.
How to revoke
Disconnect it on the Integrations tab, then delete the private app (or regenerate its token) in Intercom's Developer Hub. Do both — revoking it at Intercom is the step that actually guarantees it.
→Begin
Put Intercom to work.
Connect it once, and your next readout builds itself.
14 days · no credit card required