Probation reviews due
The head of people at Acme asks whose probation ends before the end of the month. Memtro reads the directory and lists three people with their probation end dates, job titles and managers, so the reviews can be booked.
Ask who reports to whom, who is away this week, and when probation ends.
Connect Humaans with an API access token and Memtro reads the people directory, with work email, status, location, teams, and start, probation and leaving dates, along with job roles with department and manager, time away and locations. Dates of birth, addresses, pay and leave reasons are never read. The hourly sync writes people into memory. When you ask, and once an administrator has granted the action by name, it can book time away, approve, decline or change it, record a new job role, and adjust a person's allowance. Deleting a time away entry is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Humaans tool, reads what it needs, and answers with the source cited.
These tools change something in Humaans. 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 Humaans for you. Each event can start a job, with the event as its input. Humaans signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Humaans 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 is away this week, and is it holiday or sickness?
Who reports to Priya Nair?
Whose probation ends in the next month?
Book Dan Fletcher's holiday from 22 to 24 December
Approve Priya Nair's pending time away request for next Friday
The head of people at Acme asks whose probation ends before the end of the month. Memtro reads the directory and lists three people with their probation end dates, job titles and managers, so the reviews can be booked.
Dan Fletcher, a team lead at Northwind, asks Memtro to book three days of holiday for Priya Nair after she agreed them with him. Memtro books the time away, which lands as pending for its approvers, draws on her allowance, and is visible to her and her manager.
The teams that lean on Humaans most, a question each of them asks, and what they connect beside it.
A record in Humaans 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 Humaans open API tokens. A token never sees more than the person who made it, so an owner or admin should make it
Create a token with the public:read scope and an expiry. Add private:write only for the actions an administrator will grant: booking, changing or deleting time away, new job roles and allowance adjustments. private:read is not needed
In Memtro open Connections → Humaans, paste the API access token and connect. A token with an expiry stops working on that date
Ask who is away this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Humaans tools are the same everywhere.
Only when you ask, and only what it has been granted: book time away for a person in Humaans; change the dates, type or approval status of time away in Humaans; delete a time away entry in Humaans (permanent); record a new job role for a person in Humaans; add or remove days from a person's time away allowance in Humaans. 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 Humaans records into memory as entities.
API access token. In Humaans open API tokens. A token never sees more than the person who made it, so an owner or admin should make it.
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 Humaans 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