Ask JazzHR how many people applied for a job this week, and where they are.
Connect JazzHR with an API key and Memtro reads jobs with status, department, location and hiring lead, applicants by job, status, rating or apply date and their workflow step, hires and the activity log. Applicants' contact details, salary and EEO answers 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 add notes, create applicants, move them between steps, categorise them, and create jobs, which can go on the careers page and job boards. None of these can be deleted through the API.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right JazzHR tool, reads what it needs, and answers with the source cited.
These tools change something in JazzHR. 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, then add the address it shows as a webhook in JazzHR, choosing the same kinds; the tab shows JazzHR's own steps. Each event can start a job, with the event as its input. JazzHR signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce JazzHR 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.
JazzHR + MemtroHow many people applied for the warehouse supervisor job this week?
Which applicants for the account executive role are rated 4 or higher?
Who did we hire last month, and for which jobs?
Add a note to Dan Fletcher's application: strong references, follow up Monday
Move Priya Sharma to the phone screen step on the account executive job
On Monday the operations director asks how many people applied for the Acme warehouse supervisor job last week. Memtro lists 23 new applicants by apply date, with source and rating, and notes that five are already at the phone screen step.
Laura Bennett asks Memtro to post a drafting version of a part-time warehouse role in the UK with Dan Fletcher as hiring lead. Memtro creates the job in JazzHR as a draft, not on the careers page or any job board, and says JazzHR's API cannot edit or delete it afterwards.
The teams that lean on JazzHR most, a question each of them asks, and what they connect beside it.
A record in JazzHR 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
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMIn JazzHR open Settings → Integrations and copy the API key. It sees and can change the whole account
API access may need JazzHR's top plan, possibly for an extra fee, but JazzHR's own docs do not say which plan includes it
In Memtro open Connections → JazzHR, paste the API key and connect
Ask how many people applied for a job this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The JazzHR tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to an applicant; create an applicant, optionally applied to one job (JazzHR may send the job's automated emails); put an applicant on a job, or set their workflow step and rating on it; create a job (open or draft, syndicated to job boards only when asked); create an applicant category; put an applicant in a category. 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 JazzHR open Settings → Integrations and copy the API key. It sees and can change the whole account.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in JazzHR, choosing the same kinds; the tab shows JazzHR's own steps. 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
