Does Canny Autopilot Replace a Custom Slack/Discord/Zendesk-to-Linear Pipeline?
No, not fully. Canny's Autopilot automates capture, dedupe, and triage for sales calls, support tickets, and review sites. Canny's integrations page feeds it from Gong, Intercom, Zendesk, Help Scout, Freshdesk, Zoom, Fathom, Fireflies, Grain, and tl;dv, plus review sites like G2 and Capterra. Slack is on that list too, but only when someone mentions the Canny bot inside a thread; it isn't reading every message. Discord isn't on the list at all. In Canny's own integration catalog, Discord sits under "Communication," and its one job there is pushing notifications about Canny activity out to a channel. Nothing in Autopilot reads Discord messages in.
And even for the sources Autopilot does read, the destination is a Canny post, not a Linear or GitHub issue. Getting that post into your tracker is a separate integration. Per Canny's Linear integration docs, it isn't automatic either. A person opens the post's Linked issues panel and searches for a matching Linear issue or creates a new one, one post at a time. The shape of "Autopilot replaces the pipeline" is that it replaces the support-and-sales-call half of capture, on the sources it supports, and stops at your Canny board. Discord and the trip to Linear or GitHub are still yours to wire up.
The Discord half of a request never reaches the count
Watch what happens when the same request arrives in three places in one week. A customer files a Zendesk ticket asking for it. A different customer raises it on a recorded sales call. A third mentions it in your public Discord.
Autopilot handles the first two without you touching anything. It reads the ticket and the call transcript, recognizes them as the same ask, and dedupes them into a single Canny post with both requesters attached and the product area already sorted. That is the feature working exactly as documented.
The Discord message never enters. Discord sits under "Communication" in Canny's integration catalog, and its one job there is pushing notifications about Canny activity out to a channel. You find that message only if you happen to scroll the channel that afternoon, and if you don't, the post driving your roadmap conversation is short a requester, with your most active community tier invisible in the count behind it.
Then comes the promotion step. Open the Canny post, open its Linked issues panel, search there for a matching Linear issue, and create one when nothing matches. The Discord thread has no attachment path at all, so referencing it means pasting a link into a manual note. None of that is a broken workflow. It is the documented one, and it repeats for every promoted post, indefinitely.
Autopilot's coverage, source by source
Autopilot is included on every Canny plan, from Free through Business, with no separate add-on to buy for the feature itself. Where it earns that inclusion is call and ticket triage:
- Support tickets: Zendesk, Help Scout, and Freshdesk, read directly from the conversation.
- Sales and success calls: Gong, Zoom, Google Meet, Fathom, Fireflies, Grain, and tl;dv transcripts.
- Chat, conditionally: Intercom messenger conversations pull in automatically; Slack requires an
@Cannymention in the thread you want captured. - Public sentiment: reviews from G2, Capterra, Trustpilot, the Apple App Store, and Google Play.
Everything on that list gets deduped against existing Canny posts and sorted into the right product area without a human tagging it first, which is genuinely the job Autopilot was built for. It's also a real gap list. No Discord, no email inbox, no GitHub issues, no raw analytics events. The Autopilot page says Canny "connects to hundreds more tools through Zapier," but a Zapier zap is exactly the kind of per-channel glue a custom pipeline requires, not something Autopilot does for you.
issue filed·
report writtenWhere the DIY version of this starts costing more than it saves
The natural fix is to patch the gap yourself. Set up a Zapier automation that posts new Discord messages into a Slack channel someone monitors, or a bot that copies flagged Discord threads into Canny as manual posts, plus a habit of clicking through to Linear on every promoted post as it appears. That works while the volume is low enough that one person can hold the whole system in their head. They track which channel needs manual coverage, which posts still need the Linear click, and whether the Zapier zap silently stopped running last Tuesday.
It stops working at a predictable point. Discord volume gets high enough that scrolling to catch requests isn't reliable, enough promoted Canny posts pile up that someone forgets to click through on a few each week, and enough channels exist that no one person owns "did we actually route everything" as their job. Once nobody owns routing, the fix isn't a better zap. It's not running separate pipelines per channel at all.
We'd bring up Modem here, the product we build, so read the next part with that in mind. Modem reads Slack, Discord, Zendesk, and Gong as one connected set rather than four separate integrations with different capture rules, classifies and dedupes every message against existing topics regardless of which channel it arrived in, and files the result straight into Linear or GitHub as a tracked issue with the requesters attached. No @-mention is needed on Slack, no per-post button, and Discord gets treated the same as every other source instead of being notification-only. A request split across Slack, Discord, and a ticket picks up its third mention the moment the Discord message landed, with the ticket requester, the sales account, and the Discord user all attached to one topic instead of split across a board and a scrollback.
This doesn't make Autopilot pointless. If your feedback genuinely lives in Zendesk, Gong, and Intercom, and you're fine clicking through Canny posts by hand, it does that job well, and it's already included in your plan. It matters once Discord, or any source outside Autopilot's list, carries real signal and the per-post routing step starts falling behind volume. For the fuller comparison of what a Canny setup covers versus a unified read across channels, see our guide to Canny alternatives; if Discord specifically is the gap you're patching, routing Discord bug reports into Linear with customer attribution walks through that piece on its own.
One number to pull before you decide
Pull your last month of promoted Canny posts and count how many came from Zendesk, Gong, or an @-mentioned Slack thread versus how many started as someone manually copying in a Discord message or an email. If Discord is empty, Autopilot is covering what you need and the per-post Linear click is a minor tax. If it's not empty, that's your actual gap, and it's worth sizing before deciding whether a Zapier patch or a unified read across channels is the right next step.
