Policy question
A new hire asks how to claim travel expenses. Memtro searches Outline, finds the Expenses policy in the People collection, reads the relevant section and answers with a link to the document.
Search your Outline wiki and know what changed, without opening it.
Connect Outline, cloud or self-hosted, with an API key and Memtro lists collections and their documents, searches the wiki with a snippet around each match, reads a document's markdown in full, and sees what changed recently and who edited it. Every hour the sync remembers each document created or updated. When asked, and once an administrator has granted each action by name, it creates, edits, moves, copies, archives and restores documents, comments and resolves threads, and creates or changes collections. Edits notify subscribers, and a permanent delete, or deleting a collection with every document in it, cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Outline tool, reads what it needs, and answers with the source cited.
These tools change something in Outline. 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 Outline for you. Each event can start a job, with the event as its input. Outline signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Outline 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 does the wiki say about expense claims?
What did Priya change in the Engineering collection this week?
Which documents in Policies were updated in the last month, and by whom?
Create a page in Meeting notes titled '5 November weekly' with these notes
Move the old travel policy to the Archive collection
A new hire asks how to claim travel expenses. Memtro searches Outline, finds the Expenses policy in the People collection, reads the relevant section and answers with a link to the document.
Hannah Lee asks Memtro to change the mileage rate in the Expenses policy and leave a comment for the finance team. Memtro swaps that one passage, which everyone with access sees at once and subscribers are told about, keeps the old text in the revision history, and adds a comment that notifies collaborators.
The teams that lean on Outline most, a question each of them asks, and what they connect beside it.
A record in Outline 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 Outline go to Settings → API & Apps → New API key. A key with no scopes does everything its owner can. A scoped key needs documents.*, collections.* and auth.info for reading, plus documents.*, comments.*, collections.* and stars.create write scopes for the actions
Copy the key: it is shown once, when it is created
In Memtro open Connections → Outline, paste the API key and connect. For a self-hosted Outline add the root URL of your instance
Ask what was written this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Outline tools are the same everywhere.
Only when you ask, and only what it has been granted: create a document in a collection; edit a document's title or text, or publish a draft; unpublish a document back to a draft; move a document to another collection or parent; copy a document; archive a document; delete a document (to the trash, or permanently when asked); restore an archived or deleted document, or an earlier revision; comment on a document or reply to a comment; resolve a comment thread; star a document for the key's owner; create a collection; rename a collection or change its description, icon or colour; delete a collection and every document in it. 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 Outline records into memory as entities.
API key. In Outline go to Settings → API & Apps → New API key. A key with no scopes does everything its owner can. A scoped key needs documents.*, collections.* and auth.info for reading, plus documents.*, comments.*, collections.* and stars.create write scopes for the actions.
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 Outline 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