Which feature requests have the most votes, who asked for them and what shipped.
Connect Canny with your secret API key and Memtro reads boards, feature-request posts with votes and comments, who voted and for which company, users, companies, tags and changelog entries. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can create and edit posts, change a post's status, tag posts, record votes, add internal comments, and create or publish changelog entries. Changing a status or publishing an entry can email your users, and deleting a post, comment or entry is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Canny tool, reads what it needs, and answers with the source cited.
These tools change something in Canny. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Canny, choosing the same kinds; the tab shows Canny's own steps. Each event can start a job, with the event as its input. Canny signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Canny is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Canny + MemtroWhich feature requests have the most votes right now?
What has Acme voted for on the Feature Requests board?
Who asked for single sign-on, and which companies are they from?
What did we ship in the changelog last month?
Mark the SSO post as planned without emailing voters
The product lead asks which open requests matter most. Memtro reads posts sorted by score, then the votes on the top ten with each voter's company and monthly spend, and answers with the requests ranked by votes and the spend behind them.
Audit logs ship, and Dan Fletcher asks Memtro to mark the request complete and tell its voters. Memtro changes the post's status to complete with the comment he approved, and Canny emails every non-admin voter about the change.
The teams that lean on Canny most, a question each of them asks, and what they connect beside it.
A record in Canny is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Clio Manage
YouTrack
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn Canny open Settings → API and copy the Secret API key, which has full access to the company's Canny data
In Memtro open Connections → Canny, paste the Secret API key and connect
Memtro writes only when asked and only the actions an administrator granted, and on Canny's Free plan the key is limited to 100 requests a minute and 1,000 an hour
Ask which requests have the most votes
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Canny tools are the same everywhere.
Only when you ask, and only what it has been granted: create a post on a feedback board, on behalf of a Canny user; add an internal (team-only) comment to a post, with no voter notification; create a tag on a board; add a tag to a post; change a post's status, optionally emailing its voters and adding a public comment; edit a post's title, details, ETA, owner, images or custom fields; remove a tag from a post; create a changelog entry, as a draft unless asked to publish or schedule it; publish, schedule or unpublish a changelog entry (publishing can email users); record a user's vote on a post; delete a comment (permanent); delete a post (permanent); delete a changelog entry (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Secret API key. In Canny open Settings → API and copy the Secret API key, which has full access to the company's Canny data.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Canny, choosing the same kinds; the tab shows Canny's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time