Canny
Project ManagementManage user feedback in Canny from your flows. Agents create feature requests on any board, browse and search posts, add comments when linked tickets resolve, tally votes, and resolve users by email before acting on their behalf.
What This Integration Enables
Canny only works if it is the single place demand accumulates, and that breaks the moment feedback arrives anywhere else, which it always does. This connector makes FlowRunner agents the intake clerks: they resolve the requesting customer by email, search the board for prior art, create posts and cast votes on behalf of real users, and post comments back when linked work ships. The roadmap conversation then starts from a tally that includes everyone, not just board natives. And because every write carries a real user's identity, the board stays what it claims to be: a record of customer demand, not a place where a bot's opinions accumulate under borrowed names. - Resolve a person by email before any post, comment, or vote is made in their name - Search and browse posts by board, status, and query before creating duplicates - Convert support and sales asks into attributed posts and votes - Comment on posts when the linked ticket or PR resolves - Pull top-voted and recently changed posts for roadmap digests
Without FlowRunner
With FlowRunner
Use Case Scenarios
The helpdesk-to-board pipeline
A feature request arrives by email through [Gmail](/integrations/gmail). The agent calls Get User with the sender's address; if the customer exists in Canny, their id becomes the author, and if not, the request routes to a person to decide whether to invite them. List Posts searches the board for the same ask. A clean miss becomes Create Post under the customer's name; a match becomes Create Vote so the existing post's score grows. Either way the customer's demand is on the record, attributed, and countable.
Roadmap digest with real numbers
Every Friday, the agent runs List Posts filtered by status across the boards from List Boards, pulls scores and comment counts, and calls List Votes on the movers to see who is asking. The digest posts to [Slack](/integrations/slack): top requests by votes, new entrants, and which enterprise accounts appear in the voter lists. Product walks into Monday planning with demand data instead of anecdotes.
Feedback that reaches the sprint board
Once triage marks posts as planned, the agent pipes each one into [Linear](/integrations/linear) as an issue carrying the Canny post URL, score, and top comments from List Comments. When the Linear issue closes, the return leg fires: the agent drafts a comment announcing the fix, a person approves the wording, and Create Comment posts it so every voter gets notified. The customers who asked are the first to know it shipped.
Human-in-Loop Highlight
Create Comment and Create Post write to a public board under a real customer's or teammate's name, and Canny notifies every voter on a post when activity lands. An agent that auto-comments "this has shipped" onto a post with 340 voters has just emailed 340 customers, and if the fix does not actually cover their case, the thread fills with public corrections no one can retract. So FlowRunner flows draft the comment, name the audience, and wait: "Posting to 'Bulk export to CSV', 340 voters will be notified, author shown as Priya from Product. Approve the text?" The same discipline covers Create Vote, because a vote cast on someone's behalf is a data point in the prioritization record, and the human question, did this customer actually ask for this, is exactly the kind an agent should raise and a person should answer before the score moves.
Agent Capabilities
11 actionsPosts
3- List Posts Fetches posts filtered by board, status, or search query, with limit and skip paging and a hasMore flag. The search step that prevents duplicate posts.
- Get Post Retrieves one post by id with full details: status, score, comment count, author, board, tags, and public URL.
- Create Post Creates a feature request on a board on behalf of a specific user, with title and details. The write that turns a support conversation into countable demand.
Boards and Categories
2- List Boards Fetches all boards with id, name, post count, and URL. The map of where feedback lives.
- List Categories Fetches the categories on a board for organizing and filtering posts.
Comments
2- List Comments Fetches a post's comments in chronological order with author, text, and time.
- Create Comment Adds a comment to a post on behalf of a user. Public and voter-notifying, which is why FlowRunner routes it through approval.
Votes
2- List Votes Fetches the votes on a post with voter, board, and timestamp. The evidence layer under prioritization.
- Create Vote Casts a vote on behalf of a user, raising the post's score. Used when a duplicate ask should strengthen the original post.
Users
2- List Users Fetches the company's users, the people who have authored posts, comments, or votes, with paging.
- Get User Retrieves one user by Canny id or email. The resolution step that keeps every write attributed to a real person.
Frequently Asked Questions
What can FlowRunner do with Canny?
FlowRunner agents can run List Posts, Get Post, and Create Post in Canny, plus 8 more actions.
Does connecting Canny to FlowRunner require OAuth?
No. Canny connects to FlowRunner with an API key, no OAuth flow required.
Can Canny trigger a FlowRunner workflow automatically?
Canny doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Canny
$100 in credits. No card required. Connect in minutes.