A product channel that stays readable
Each post is one Slack message, with comments and moves threaded under it. Engineers see the customer's words in their own tool, and you see progress without asking.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 5 · Connect · Slack & issue trackers
Each new post becomes a Slack message, with every later change threaded under it, and a reply in that thread lands on the post. Move a post to the status you choose and it becomes an issue in Linear, Jira, GitHub or ClickUp. When the issue moves, so does the post.
Try it
Reply in the Slack thread and see it land on the post. Then finish the issue in Linear and watch the post move.
Step by step
Sign in to Slack or your tracker and approve HeedPost.
Choose the Slack channels, and the team or project each board's issues go to.
Pick the status that creates an issue, like Planned.
Match your statuses to the tracker's. HeedPost checks the match when you save it.
Reply in Slack and close issues in your tracker. HeedPost keeps up.
Who it's for
Each post is one Slack message, with comments and moves threaded under it. Engineers see the customer's words in their own tool, and you see progress without asking.
When engineering closes the issue, the post moves and everyone who asked is told.
Moving a post to Planned files a Linear issue with the customer's words, and finishing it ships the post. On GitHub, paste an existing issue onto a post to link the two.
The details
Pick a channel, or one per board, and what reaches it: new posts, comments, status changes and moves between boards. Each post is one message, and everything after it is threaded under that message, so the channel stays readable. Answer in the thread and your reply appears on the post as a comment from you, as long as your Slack email belongs to someone in the workspace.
Connect your tracker, choose which team or project each board's issues go to, and pick the status that files an issue, like Planned. Map your HeedPost statuses to the tracker's states. When the issue moves, the post moves with it, and its followers are told.
Paste an existing issue onto a post to link the two instead of filing a new one.
Moving a hundred posts won't file a hundred issues you didn't mean: filing waits for the undo window, then checks each post is still in that status.
The API, the events, and what you can rely on when you build on it.
Every message from Slack or a tracker is checked for its signature and recorded, so a retry is recognised and applied only once. Slack retries anything that takes longer than three seconds, so this matters.
A post links to one issue, and an issue to one post. Even if two filings start at the same moment, a post is filed only once.
HeedPost checks a status map when you save it. GitHub, for example, stores a plain closed as closed as completed. If a map would land on a different status, you see an explanation when you save it, instead of finding out later.
No response ever includes a Slack or tracker token, and tokens are read only at the moment they're used. Disconnecting is always free, and your plan counts only live connections.
Each of these is a REST endpoint and, with the same name, an MCP tool.
GET/v1/webhookslist_webhooks Every endpoint this workspace sends events to, and how its recent deliveries went.28 event types from this feature reach your webhooks. Each line shows what its data carries.
slack.connectedno extra detailsslack.disconnectedno extra detailsslack.reconnectedno extra detailsslack.updatedno extra detailslinear.connectedno extra detailslinear.disconnectedno extra detailslinear.issue_linkedissue, createdlinear.issue_unlinkedissuelinear.reconnectedno extra detailslinear.updatedno extra detailsjira.connectedno extra detailsjira.disconnectedno extra detailsjira.issue_linkedissue, createdjira.issue_unlinkedissuejira.reconnectedno extra detailsjira.updatedno extra detailsgithub.connectedno extra detailsgithub.disconnectedno extra detailsgithub.issue_linkedissue, createdgithub.issue_unlinkedissuegithub.reconnectedno extra detailsgithub.updatedno extra detailsclickup.connectedno extra detailsclickup.disconnectedno extra detailsclickup.issue_linkedissue, createdclickup.issue_unlinkedissueclickup.reconnectedno extra detailsclickup.updatedno extra detailsPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Integrations (Slack, a tracker or a webhook endpoint) | 0 | 1 | Unlimited |
| Two-way status with trackers | Not included | Included | Included |
| Slack replies back to the post | Not included | Included | Included |
Something else? Write to us, and a person answers.
A Slack connection, a connected tracker, or a webhook endpoint. Plus includes one, and Pro has no limit. API keys don't count.
Yes. Paste it onto the post.
Only after the eight-second undo, and only for posts still in the filing status.
Linear, Jira, GitHub and ClickUp.
The person in your workspace with the same email as the Slack account. Replies from anyone else aren't posted.
No. Your posts and their history stay.