Ask Factorial HR who is off next week, who manages whom and what is overdue.
Connect Factorial HR with an API key and Memtro reads employees with work email, manager and leaving dates, teams with leads, time off by person and date range, and HR tasks with status, due date and assignees. Pay, bank and identity details are never read into an answer. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can manage HR tasks, book, approve, reject or cancel time off, clock people in and out, create projects and teams, invite employees by email, and terminate an employee.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Factorial HR tool, reads what it needs, and answers with the source cited.
These tools change something in Factorial HR. 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 Factorial HR for you. Each event can start a job, with the event as its input. Factorial HR sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Factorial HR 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.
Factorial HR + MemtroWho is off next week?
How much holiday has Dan Fletcher taken this year?
Who manages Priya Nair, and who else is in her team?
Which onboarding tasks are overdue?
Approve Dan Fletcher's holiday request for the week of 14 December
On Thursday the operations lead at Acme asks who is off next week. Memtro reads the approved time off overlapping those dates and lists each person with leave type and days, then flags two pending requests still waiting for approval.
Priya Nair, who manages the Brightwave Ltd support team, asks Memtro to approve Dan Fletcher's pending holiday. Memtro finds the request, confirms the dates with her, and approves it in Factorial, where Dan sees the decision.
The teams that lean on Factorial HR most, a question each of them asks, and what they connect beside it.
A record in Factorial HR 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.
BambooHR
Ashby
Breathe HR
Lever
Workable
Deel
Pinpoint
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMA Factorial admin creates the key, and it reads the whole company: Factorial → Settings → API Keys → New API Key, name it Memtro, then Get my API Key
Copy the key now, since Factorial shows it once
In Memtro open Connections → Factorial HR, paste the API key and connect
Ask who is off next week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Factorial HR tools are the same everywhere.
Only when you ask, and only what it has been granted: create an HR task; change an HR task; delete an HR task; book time off for an employee; approve a time-off request; reject a time-off request; cancel (delete) a leave; invite an employee to Factorial; terminate an employee; clock an employee in; clock an employee out; create a project; create a team; add an employee to a team. 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.
API key. A Factorial admin creates the key, and it reads the whole company: Factorial → Settings → API Keys → New API Key, name it Memtro, then Get my API Key.
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 Factorial HR 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
