Staffing a new project
Tom Reilly, delivery director at Acme Ltd, asked who could join a new client project in January. Memtro read the assignments and leave over that month and named three people with free days, with their hours already planned.
Who is free next month, and who is booked on which project?
Runn connects Memtro to your resource planning. It reads people, projects and clients, who is assigned to which project in which role and for how many hours a day, the time actually worked, leave, and project notes and milestones. When asked, and once an administrator has granted the action by name, it can add a project note or time worked, create or delete an assignment, book or delete leave, create a project or client, rename, confirm or archive a project, and add a milestone. Leave reasons are never returned, and notes Memtro adds show as written by API.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Runn tool, reads what it needs, and answers with the source cited.
These tools change something in Runn. 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.
Once Runn 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.
Who has capacity next month?
Who is assigned to the Northwind rebuild, and for how many hours a day?
How many billable hours did the design team log last week?
Who is on leave in the week of 14 December?
Book Maya Okafor on leave from 22 to 24 December
Tom Reilly, delivery director at Acme Ltd, asked who could join a new client project in January. Memtro read the assignments and leave over that month and named three people with free days, with their hours already planned.
Priya Sharma, resource manager at Northwind, asked Memtro to put Dan Fletcher on the BigCo rebuild as a developer for four hours a day through February. Memtro created the assignment in Runn for every working day in that range.
The teams that lean on Runn most, a question each of them asks, and what they connect beside it.
A record in Runn 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 Runn, as an admin with Edit Account Settings and Data turned on, open Settings → API → Create API Token.
Choose Write if Memtro should make changes, otherwise Read, and copy the token, which is shown once.
In Memtro, open Connections → Runn and paste it into API token. Set Region to us if your API domain is api.us.runn.io.
Ask your first question: who has capacity next month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Runn tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a project; add time worked for a person on a project (adds to what is there); assign a person to a project for a date range and hours a day; delete an assignment (permanent); book leave for a person (merges with overlapping leave); delete a leave booking (permanent); create a project for a client; rename, confirm or tentative, archive or unarchive a project; create a client; add a milestone to a project. 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 Runn records into memory as entities.
API token and optional region. In Runn, as an admin with Edit Account Settings and Data turned on, open Settings → API → Create API Token.
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