Ask who is off next week, who someone reports to, and when a person started.
Connect CharlieHR with a Client ID and Client Secret and Memtro reads the team directory, with names, work emails, job titles, managers, teams, offices, start dates and leaving dates, along with leave requests and types and company holidays. NI numbers, dates of birth, personal contact details, home addresses, salaries, bank details and leave reasons are never returned. It reads on demand and there is no hourly sync. When you ask, it can add a note to a team member's profile, seen by whoever its note type allows.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right CharlieHR tool, reads what it needs, and answers with the source cited.
These tools change something in CharlieHR. 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 CharlieHR 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.
CharlieHR + MemtroWho is off next week?
Who does Priya Sharma report to?
How many days of holiday has Dan Fletcher booked this year?
Which bank holidays and office closures are coming up before Christmas?
Add a note to Dan Fletcher's profile that he finished his first-aid course
The engineering lead asks who on the platform team is away over the next fortnight. Memtro reads approved and pending leave requests for that window and lists each person with the type and dates, noting that Monday is a company holiday.
The office manager at Brightwave Ltd asks who joins this month. Memtro reads the directory and lists two new starters with their job title, team, office, manager and start date, without any personal details or pay.
The teams that lean on CharlieHR most, a question each of them asks, and what they connect beside it.
A record in CharlieHR 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
Factorial HR
Pinpoint
Recruitee
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMIn CharlieHR open Company → Integrations → any integration tile → API Keys; only a Super Admin can generate keys
Tick the confirmation, generate a key and copy the Client ID and Client Secret: CharlieHR shows them once
Paste both into Connections → CharlieHR in Memtro and connect; if the test is refused, ask CharlieHR support which key a company's own integration should use
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 CharlieHR tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a team member's CharlieHR profile. 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.
Client ID and Client Secret. In CharlieHR open Company → Integrations → any integration tile → API Keys; only a Super Admin can generate keys.
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
