Pipeline check
Maya Okafor, head of people at Acme Ltd, asked where the designer vacancy stood. Memtro listed the candidates by stage with when each applied, and linked each one in Homerun for the details.
How many candidates are in interview for the designer role in Homerun?
Homerun connects Memtro to your applicant tracking. It reads vacancies with status, department, location, stages, salary range and candidate counts, and each vacancy's application-form questions. It lists candidates by vacancy, stage, hire date or disqualification, with their non-sensitive notes and tags. When asked and granted, it can add, move or delete candidates, add, edit and delete notes, create, rename and delete tags, tag and untag candidates, submit form answers, and send the confirmation email. Candidates come back as ids, stages and dates only: never names, contact details, ratings, answers or files.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Homerun tool, reads what it needs, and answers with the source cited.
These tools change something in Homerun. 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 Homerun 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.
How many candidates are in interview for the designer role?
Which vacancies are public, and how many candidates does each have?
Who was hired for engineering roles since September?
What notes are on this candidate so far?
Move candidate 58213 to the Offer stage.
Maya Okafor, head of people at Acme Ltd, asked where the designer vacancy stood. Memtro listed the candidates by stage with when each applied, and linked each one in Homerun for the details.
Tom Reilly, hiring manager at Northwind, asked Memtro to note that a candidate interviewed well and move them to Final round. As granted, Memtro added the note under Tom's name and moved the candidate, and the hiring team saw both.
The teams that lean on Homerun most, a question each of them asks, and what they connect beside it.
A record in Homerun 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.
In Homerun, an admin opens Settings, Integrations and creates an API key. Tick the read scopes, and the matching write scopes for changes, since scopes cannot be changed later.
In Memtro, open Connections → Homerun and paste the API key.
An administrator grants the actions by name, such as moving candidates, to the teams that may use them.
Ask how many candidates are in interview for the designer role.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Homerun tools are the same everywhere.
Only when you ask, and only what it has been granted: add a candidate to a vacancy or the talent pool; move a candidate to another stage or vacancy; delete a candidate (permanent); add a note to a candidate; edit a candidate's note; delete a candidate's note (permanent); send a candidate the application confirmation email (once only); create a tag; rename a tag; delete a tag (removed from every candidate); tag a candidate; remove a tag from a candidate; submit answers to a vacancy's application-form questions for a candidate. 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 Homerun, an admin opens Settings, Integrations and creates an API key. Tick the read scopes, and the matching write scopes for changes, since scopes cannot be changed later.
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