Ask what last month's payroll cost by nominal code, without anyone's pay being shown.
Connect Staffology Payroll with an API key and Memtro reads employers, employees with job title and department, pay runs, and payroll cost totals by nominal code and pay code. Salaries, NI numbers, bank details and contact details are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can manage employer notes and departments, record leave, start, finalise or reopen pay runs, where finalising may submit to HMRC, email payslips to employees, and mark leavers, which cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Staffology Payroll tool, reads what it needs, and answers with the source cited.
These tools change something in Staffology Payroll. 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 Staffology Payroll 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.
What did payroll cost for Acme last month by nominal code?
Who joined the Brightwave Ltd engineering department this tax year?
Which pay runs have we had for Northwind so far in Year2026?
How much employer NI did we pay over the last three months?
Record two weeks' holiday for Dan Fletcher from 1 December
The finance lead asks what payroll cost Acme over the first quarter of the tax year. Memtro reads the totals by nominal code for Months 1 to 3: gross pay, employer NI and pensions, summed across employees, with nobody's pay shown.
At a payroll bureau, Priya Nair asks Memtro to finalise Northwind's Month 8 pay run and email the payslips. Memtro finalises it, Staffology submits the FPS to HMRC as the employer's settings say, and each employee receives their payslip by email.
The teams that lean on Staffology Payroll most, a question each of them asks, and what they connect beside it.
A record in Staffology Payroll 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 app.staffology.co.uk click your initials (top right) → API Keys, enter a name such as Memtro, create the key and copy it
Staffology has no read-only keys: this key gives full access to the whole payroll account, every employer included, and Memtro acts only when asked and through the actions an administrator grants
Paste the API key into Connections → Staffology Payroll in Memtro, optionally set a Default employer ID, and connect
Ask what last month's payroll cost by nominal code
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Staffology Payroll tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to an employer; edit an employer note's title and text; delete an employer note (permanent); create a department; change a department's title, colour or accounting code; record leave (holiday, sickness, parental and so on) for an employee; start the next pay run for a pay frequency; finalise or reopen a pay run, emailing payslips only if asked; re-send payslip emails for one pay run entry or a whole pay run; mark employees as leavers, emailing P45s only if asked. 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. In app.staffology.co.uk click your initials (top right) → API Keys, enter a name such as Memtro, create the key and copy it.
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
