Canny
Manage posts, boards, votes, comments, tags and users on Canny — the product feedback and feature request platform.
About
Canny ships in the w6w first-party pack. It declares 39 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.canny- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Project Management · Customer Support
Overview
Canny collects product feedback: users post feature requests on a board, vote and comment on the ones they care about, and your team triages, tags, categorizes and moves posts through a status pipeline — then tells everyone what shipped in a changelog. This app covers that whole loop from a workflow: read and search posts and boards, create posts and comments on a user’s behalf, move a post through status/category/board changes, tag it, merge duplicates, and cast or remove votes.
It also covers the two records every automation eventually needs: users (Canny’s own identity, keyed by your application’s userID or a Canny-issued id) and companies (the account a user belongs to, with custom fields and MRR) — both upserted and read the same way Canny’s own SSO/Identify integrations do. A changelog entry action lets a workflow publish a release note the moment a linked post’s status changes, and a status-change feed lets a workflow react to the whole team’s triage activity instead of one post at a time.
Canny’s API is authenticated with one secret, workspace-wide API key — there is no per-token scoping — sent as an apiKey field in the JSON body of every POST, never as a header or query string. Every path, argument and response field here was read off Canny’s own generated API reference (developers.canny.io) rather than a third-party directory.
Build with Canny
Three routes to the same 39 actions. The Workflow tab is generated from Canny's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Comment
comment-create Post a portal comment on behalf of a user. The author must already exist as a Canny user — see Upsert User.
List Comments
comment-list Search portal comments, optionally filtered by post, board, author or company.
Update Company
company-update Update a company. To create one, upsert a user with this company id in its companies list.
Create Changelog Entry
entry-create Create a changelog entry, optionally publishing or scheduling it immediately.
Change Post Status
post-change-status Move a post to a new status, with an attached status-change comment.
Create Post
post-create Create a new post. The author must already exist as a Canny user — see Upsert User.
List Status Changes
status-change-list List the feed of post status changes across a board or the workspace.
Create Tag
tag-create Create a tag on a board. Calling it again with the same name returns the same tag.
Delete User
user-delete Delete a user, including their comments and votes. A post left with no other activity is removed along with them.
Upsert User
user-upsert Create a user, or update one identified by email, userID or id. Returns the user's Canny id.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Canny's real ids.
{
"manifestVersion": "2",
"name": "canny-example",
"steps": [
{
"id": "board-get",
"uses": {
"app": "io.w6w.canny",
"action": "board-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Board
readboard-get -
List Boards
searchboard-list -
Create Category
performcategory-create -
Get Category
readcategory-get -
List Categories
searchcategory-list
+34 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Canny, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Canny. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "board-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action board-get --payload '{"id":"<value>"}'Give an AI agent Canny — without giving it Canny's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.canny#board-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Canny connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Canny's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Canny itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Canny declares its own checks, so its health is a property of the app rather than something the host guesses at.