On the roadmap
Support is asked when scheduled exports will ship. Memtro finds the feature in Productboard, its status, owner and timeframe, the release it sits in, and how many notes from customers are linked to it.
Features, releases and customer feedback from Productboard, with the customer behind each note.
Connect Productboard with an access token and Memtro reads your products, components and features with status, owner and timeframe, releases and objectives, the companies and users behind feedback, and the notes themselves. Every hour the sync writes each new feedback note into memory with its customer. When asked, and once an administrator has granted each action by name, it adds and updates feedback notes, creates and updates features, initiatives, objectives and releases, and links them as parent, child or blocker. Deleting a note, or an entity with its children, is permanent and Productboard cannot restore it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Productboard tool, reads what it needs, and answers with the source cited.
These tools change something in Productboard. 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, choose the kinds you want, and Memtro registers its address with Productboard for you. Each event can start a job, with the event as its input. Productboard sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Productboard 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.
What feedback have we had about CSV export since September?
Which features are In progress, and who owns each?
What has Northwind Traders asked for, and which features is it linked to?
Add a feedback note from sara@northwindtraders.com: wants scheduled exports to SFTP, from today's call
Move the scheduled exports feature to Planned and put it in the Q1 release
Support is asked when scheduled exports will ship. Memtro finds the feature in Productboard, its status, owner and timeframe, the release it sits in, and how many notes from customers are linked to it.
After a call, Owen Barnes asks Memtro to log Acme's request and mark the scheduled exports feature as Planned. Memtro adds a feedback note under the customer's email with the call as its source, then changes the feature's status. The whole workspace sees both at once, attributed to the token's owner.
The teams that lean on Productboard most, a question each of them asks, and what they connect beside it.
A record in Productboard 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.
In Productboard open Settings → Integrations → Public APIs → Access Token and click + to generate a token. Public API access needs a Pro plan or above, and the token is shown once
Writing and deleting entities and notes are separate token permissions: leave delete off unless deleting is wanted
In Memtro open Connections → Productboard, paste the Access token and connect. The token reads the whole workspace, and anything Memtro adds or changes is attributed to its owner
Ask what feedback mentions exports this quarter
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Productboard tools are the same everywhere.
Only when you ask, and only what it has been granted: add a feedback note, linked to a customer by email; update a feedback note: title, content, owner, tags, processed or archived; delete a feedback note (permanent); create a feature, initiative, objective, release or other entity; update an entity: name, description, status, owner, timeframe, tags or archived; link two entities as parent, child, link or blocker; delete an entity and its children (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. An hourly sync anchors recently changed Productboard records into memory as entities.
Access token. In Productboard open Settings → Integrations → Public APIs → Access Token and click + to generate a token. Public API access needs a Pro plan or above, and the token is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Productboard for you. 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