- Integrations
- /
- Canny
Canny
Canny customer feedback and roadmap
Canny is the feedback-and-roadmap platform — customers submit feature requests, vote on them, and watch the roadmap as features ship; product teams use it as the single source of truth for "what should we build next". Tiny Command exposes three actions, no triggers (Canny webhooks for post-created, post-status-changed, vote-added are configured in admin; point at a Tiny Command webhook trigger URL): List Boards (the top-level categorisation — usually one board per product or feature area), List Posts (paginated with filters by board, status, author), Create Post (programmatically file a feature request — useful for "when a support ticket mentions a feature gap, auto-file a Canny post" workflows). The connection uses a Canny API key from the company settings. Create Post lets you pass authorEmail to attribute the post to a customer (creates a Canny user account if not already present). The board concept matters: different product surfaces typically have different boards so the visible roadmap stays scoped per audience.
Do anything Canny can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Feedback Post | Files a feature request or feedback post programmatically. Optionally attribute to a customer (creates the Canny user if not present). The standard hook for "support ticket mentions a feature gap → auto-file in Canny on the customer's behalf" workflows. |
| List Boards | Returns every board in the connected workspace with name, slug, post count. Useful for resolving board IDs at workflow-build time when creating new posts. |
| List Posts | Paginated posts filterable by board, status (Open, Under Review, Planned, In Progress, Complete, Closed), and recently active. Useful for "weekly digest of new feedback" workflows that the product team consumes. |
Pre-built Canny workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Canny once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Canny field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Canny integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Canny to Tiny Command?
What Canny triggers does Tiny Command support?
What Canny actions can I run from a workflow?
Is the Canny integration real-time?
Do I need to write code to use Canny with Tiny Command?
How much does the Canny integration cost?
More other apps people connect.
Same category as Canny, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Canny.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.