Ask Sage HR who is off next week, and how hiring for a role is going.
Connect Sage HR with your subdomain and an API key and Memtro reads employees with position, team, manager and start date, leavers, teams, time-off policies and requests, who is out of office on a day, and recruitment positions with applicants. Birth dates, addresses, pay and bank details are never read. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can book time off, create, update, terminate or rehire employees, add applicants, record timesheets, and permanently delete an employee document.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sage HR tool, reads what it needs, and answers with the source cited.
These tools change something in Sage 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.
Once Sage 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.
Who is off next week?
Who is out of office today?
How many applicants does the senior designer role have, and at what stage?
What is the default holiday allowance, and does it carry over?
Book 22 and 23 December off for Dan Fletcher under annual leave
Before planning on Monday, the engineering lead asks who on the team is off next week. Memtro reads the time-off requests for the window and lists Dan Fletcher off Tuesday to Thursday and Priya Nair off on Friday afternoon, both approved.
Laura Bennett, office manager at Globex, asks Memtro to book Dan Fletcher's holiday on 22 and 23 December. Memtro creates the request under the annual leave policy in Sage HR, where it enters that policy's approval flow for his manager to decide.
The teams that lean on Sage HR most, a question each of them asks, and what they connect beside it.
A record in Sage 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
Factorial HR
Pinpoint
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMIn Sage HR open Settings → Integrations → API, enable API access and copy the key shown. The key has the permissions of the admin who enabled it, for reading and for any action an administrator grants
Re-enabling the API regenerates the key, and it stops working if that admin loses admin rights
Paste the API key into Connections → Sage HR in Memtro with your Subdomain, the part before .sage.hr (acme for acme.sage.hr), 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 Sage HR tools are the same everywhere.
Only when you ask, and only what it has been granted: book time off for an employee under a policy (enters the policy's approval flow); create an employee (welcome email only when asked); update an employee's name, start date, team, manager, location, position, number or approvers; terminate an employee on a last working day; rehire a terminated employee; add an applicant to an open recruitment position (thank-you email only when asked); record a worked day for an employee; clock an employee in and out on a day; add a task to the onboarding or offboarding checklist template; log a keeping-in-touch day, or approve, decline or cancel one; create a timesheet project, or close one; delete an employee document (permanent). 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.
Subdomain and API key. In Sage HR open Settings → Integrations → API, enable API access and copy the key shown. The key has the permissions of the admin who enabled it, for reading and for any action an administrator grants.
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
