Sprint stand-up
Tom Reilly, engineering lead at Northwind, asked what was in the Doing column. Memtro listed the cards with assignees, due dates and checklist progress.
What is in the Doing column on the Favro sprint board?
Favro connects Memtro to your boards and backlogs. It reads collections, boards with their columns and lanes, and cards with assignees, tags, dates and checklist progress. For one card it reads the description, comments, checklists and activity, and it lists the organisation's members. When asked and granted, it can create, edit, move, archive or delete cards, comment, add checklists and tick their items, and create tags, columns and boards. With events on, Favro tells Memtro when a card is created or moved, and a job can start on it. Events come from one board, which you name.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Favro tool, reads what it needs, and answers with the source cited.
These tools change something in Favro. 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 Favro for you. Each event can start a job, with the event as its input. Favro signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Favro 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 is in the Doing column on the sprint board?
Who moved card 412, and when?
What is left on the checklist for card 388?
Which cards on the sprint board are due this week?
Comment on card 412 that the design is approved.
Tom Reilly, engineering lead at Northwind, asked what was in the Doing column. Memtro listed the cards with assignees, due dates and checklist progress.
At Acme Ltd, a job starts when a card moves between columns on the sprint board. It reads the card's checklists and, as granted, comments on the card listing the unticked items. Everyone who can see the card sees it, including Maya Okafor, the product owner.
The teams that lean on Favro most, a question each of them asks, and what they connect beside it.
A record in Favro 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 Favro, open your profile, API tokens, and create a token. Leave it read-write for actions. The token acts as you.
In Memtro, open Connections → Favro and enter your Favro login email and the API token. Add the Organization ID only if you belong to more than one.
An administrator grants the actions by name to the teams that may use them. For events, set the Board for events, then turn events on from the connection's Events tab.
Ask what is in the Doing column on the sprint board.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Favro tools are the same everywhere.
Only when you ask, and only what it has been granted: create a card on a board or in your to-do list; edit a card: name, description, assignees, tags, dates, or archive it; move a card to another column or board, or add it to another board; delete a card; comment on a card; edit a comment; delete a comment; add a checklist to a card; add an item to a checklist; tick, untick or rename a checklist item; delete a checklist item; create a tag; add a column to a board; create a board or backlog in a collection. 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.
Favro login email and API token. In Favro, open your profile, API tokens, and create a token. Leave it read-write for actions. The token acts as you.
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 Favro 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