Feedback source
Turn Slack messages into ranked product insight
Point FeedbackFlow at the channels where feedback already happens. Every message becomes a triaged feedback item, grouped and prioritized with the rest.
Why connect Slack
- Capture the channels you already use. Feedback in #feedback, #support, or any channel flows in on its own.
- No copy and paste. Messages arrive as structured feedback items, not screenshots pasted into a doc.
- Triaged with everything else. Slack feedback is deduped, scored, and ranked next to your widget and support tools.
"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 workspace
Add the FeedbackFlow app and drop in your Slack signing secret.
- 2
Invite the bot to a channel
Point it at the channels where feedback lands.
- 3
Watch it triage
New messages become feedback items, grouped and ranked by AI.
Prefer the full walkthrough? Read the Slack setup guide.
Before you start
- A Slack workspace where you can install or edit an app, which usually means workspace admin or a rights request to one.
- A FeedbackFlow project. The free plan covers one, and no credit card is needed to finish this setup.
- A channel worth capturing. Most teams start with a single #feedback or #support channel rather than the whole workspace.
How to connect Slack to FeedbackFlow
- 1
Create or open your Slack app
Go to api.slack.com/apps and either open the app you already use or create a new one for your workspace. Under Basic Information, copy the Signing Secret and paste it into the Slack card in your FeedbackFlow project settings. FeedbackFlow uses that secret to verify that every incoming event genuinely came from Slack.
- 2
Point Event Subscriptions at your ingest URL
Open Event Subscriptions, switch it on, and paste the Request URL that FeedbackFlow shows you on the Slack card. The URL is unique to your project. Slack immediately sends a one-off challenge request to confirm the endpoint is live, and FeedbackFlow answers it automatically, so the field should verify without you doing anything else.
- 3
Subscribe to the message.channels event
Still in Event Subscriptions, open "Subscribe to bot events" and add message.channels, then save. This is the only event FeedbackFlow needs. Slack will prompt you to reinstall the app to the workspace so the new scope takes effect.
- 4
Invite the bot to the channel
In the channel you want captured, run /invite @yourbot. Slack only forwards events for channels the app is a member of, so this last step is what actually turns the flow on. Repeat it for any other channel you want to capture, and leave it out of the ones you do not.
The exact Request URL and any values you need to paste are shown on the Slack card inside your project settings, because they are specific to your project. Full Slack setup guide.
What FeedbackFlow reads from Slack
Only plain messages posted by people in channels the bot has joined. Bot posts, joins and leaves, edits, and other message subtypes are ignored, so automated channel noise does not become feedback.
| Field | What FeedbackFlow does with it |
|---|---|
| Message text | Becomes the body of the feedback item and the input the AI triages |
| Slack event ID | Stored as the external ID, so a redelivered event does not create a duplicate |
| Channel membership | Decides what is captured at all; the bot only sees channels it has been invited to |
What this looks like in practice
A customer success manager pastes a complaint into #feedback
It arrives as a feedback item within seconds, gets assigned a topic by AI, and joins the ranked list alongside anything similar that came in through your widget or Zendesk.
Five people report the same bug across a week
They collapse into one topic with a count of five rather than five separate items, so the ranking reflects how many people hit it, not who shouted loudest.
The topic reaches the top of the list
One click drafts a Jira or Linear issue with a title, summary, and acceptance criteria written from those five messages, and files it into the project your engineers already use.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- FeedbackFlow does not capture the sender identity from Slack, so items from this source are not attributed to a named requester the way Zendesk and Intercom items are. If closing the loop with a specific person matters, capture that feedback through a source that carries identity.
- Threaded replies and message edits are not ingested. Only the original top-level message in a joined channel becomes a feedback item.
- Direct messages are never captured. The connector is scoped to channels the bot has been explicitly invited to.
- This is a one-way source. FeedbackFlow reads from Slack; it does not post triage results back into a channel.
Frequently asked questions
- Does FeedbackFlow read every channel in my Slack workspace?
- No. Slack only delivers events for channels the app has been invited to, so nothing is captured until you run /invite @yourbot in a specific channel. Most teams start with one #feedback or #support channel and add more later. Direct messages are never captured, and removing the bot from a channel stops the flow immediately.
- Do I need to be a Slack admin to set this up?
- You need permission to create or edit a Slack app and to install it to the workspace, which in most organizations means an admin. Inviting the bot to a channel afterwards is something any member of that channel can do. If your workspace restricts app installation, the signing-secret step is the one that needs an admin; the rest you can finish yourself.
- What stops the same message being captured twice?
- Every ingested message is stored against its Slack event ID. Slack retries delivery when it does not get a fast acknowledgement, and those retries carry the same event ID, so a redelivery is recognised and discarded rather than becoming a second feedback item. Separately, AI dedupe groups genuinely different messages that describe the same problem into one ranked topic.
- Will this turn every message in the channel into a ticket?
- No. Messages become feedback items, which are raw material. AI groups them into topics and ranks those topics, and a Jira or Linear issue is only created when you choose to file one. Chatter in the channel adds to the pile of items but does not generate tickets on its own.
- Is Slack enough on its own, or should I connect other sources?
- Slack works fine on its own if that is genuinely where your feedback lands. The dedupe gets more useful with more sources, though: the same request arriving through Slack, your in-app widget, and Zendesk collapses into a single ranked topic with the full count behind it, which is a better prioritization signal than any one channel alone.
Connect Slack today
Free plan. No credit card. Live in 2 minutes.