Feedback source
Your Intercom conversations, triaged into a roadmap
Every new Intercom conversation flows into FeedbackFlow as a feedback item, so the themes hiding in support chats become a ranked list of what to build.
Why connect Intercom
- Support insight, not just tickets. Turn day-to-day conversations into product direction.
- Themes surface on their own. The same request across ten chats collapses into one ranked topic.
- Close the loop. Requester identity comes along, so you know who to tell when it ships.
"Export keeps timing out on large projects, this is blocking our team."
Deduped and ranked alongside every other source.
How it works
- 1
Connect your app
Add your Intercom client secret in FeedbackFlow.
- 2
Subscribe to conversations
Set the webhook to the conversation.user.created topic.
- 3
Let AI do the sorting
New conversations arrive triaged and grouped.
Prefer the full walkthrough? Read the Intercom setup guide.
Before you start
- Access to the Intercom Developer Hub for your workspace, which normally means an admin or a developer seat.
- A FeedbackFlow project, so the setup card can show you the Request URL that belongs to it.
- Ten minutes. This is the shortest of the three inbound setups: one secret, one webhook, one topic.
How to connect Intercom to FeedbackFlow
- 1
Copy your client secret
Open the Intercom Developer Hub and select your app, creating one for your workspace if you have not already. Under Basic Information, copy the Client Secret and paste it into the Intercom card in FeedbackFlow. That secret is what lets FeedbackFlow verify each webhook signature and reject anything that did not come from Intercom.
- 2
Add the webhook Request URL
In the same app, open Webhooks and add the Request URL shown on the Intercom card in FeedbackFlow. The URL is specific to your project. Intercom sends a ping to confirm the endpoint before it will save, and FeedbackFlow answers that ping automatically.
- 3
Subscribe to conversation.user.created
Select the conversation.user.created topic and save. This is the only topic FeedbackFlow needs: it fires when a customer starts a new conversation, which is the message that carries the actual request. Replies and internal notes on an existing conversation are deliberately not subscribed.
The exact Request URL and any values you need to paste are shown on the Intercom card inside your project settings, because they are specific to your project. Full Intercom setup guide.
What FeedbackFlow reads from Intercom
The opening customer message of each newly created conversation, plus who sent it when Intercom provides that. Teammate replies and internal notes are not ingested.
| Field | What FeedbackFlow does with it |
|---|---|
| Opening message body | Becomes the feedback item and the text the AI triages |
| Conversation ID | Stored as the external ID, so webhook retries do not create duplicates |
| Contact name and email | Attached as the requester, so you can close the loop when the work ships |
What this looks like in practice
A customer opens a chat asking for CSV export
The opening message becomes a feedback item with their name and email attached, and the AI files it under an export topic rather than leaving it in the conversation.
Twelve customers ask for the same thing over a month
They land on one topic with a count of twelve and the twelve requesters recorded against it, which is the number that should drive the roadmap decision.
You ship the feature
The topic carries the list of people who asked, so support knows exactly who to tell instead of guessing or searching Intercom by hand.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- Only the first message of a conversation is captured. If the real request surfaces three replies deep, that detail does not reach FeedbackFlow.
- Conversations started by a teammate rather than a customer are not ingested, because the subscribed topic is conversation.user.created.
- Identity is attached only when Intercom includes it on the payload. An anonymous visitor produces a feedback item with no requester.
- This is a one-way source. FeedbackFlow does not write notes, tags, or replies back into Intercom conversations.
Frequently asked questions
- Does this capture every reply in a conversation, or just the first message?
- Just the opening customer message. FeedbackFlow subscribes to conversation.user.created, which fires once when a customer starts a conversation. That message is usually where the request is stated, and ingesting every subsequent reply would flood the feedback list with back-and-forth that carries no new signal. The trade-off is real: if a request only emerges deep in a thread, it will not be captured.
- Will my support team notice any change in Intercom?
- No. The integration is read-only and event-driven, so nothing is written back into Intercom: no tags, no notes, no replies, no changes to conversation state. Your agents keep working exactly as they do now, and the product signal is extracted in the background.
- Does the requester come across, or just the message?
- Both, when Intercom supplies them. The contact name and email are attached to the feedback item as the requester and stay attached when items are grouped into a topic. That is what makes closing the loop practical: when a topic ships you have the list of people who asked for it, rather than a count with no names behind it.
- How does this compare to Intercom feature requests?
- Intercom can tag conversations so you can find them again, but the sorting stays manual: someone reads the tagged conversations, judges which are the same request, and decides what matters. FeedbackFlow does that step automatically across Intercom and every other source you connect, then drafts the Jira or Linear issue. If tagging is already working well for you, the gain is the cross-source dedupe rather than the capture.
- What happens if Intercom retries a webhook?
- Nothing duplicated. Each conversation is stored against its Intercom conversation ID, so a retry of the same event is recognised and discarded. Intercom retries whenever it does not receive a prompt acknowledgement, so this comes up more often than you might expect, and it is handled.
Connect Intercom today
Free plan. No credit card. Live in 2 minutes.