Pipeline for a role
The hiring manager at Acme asks who is in the running for the backend engineer job. Memtro reads the job's applications and lists each candidate by name with the stage they are at, and which were rejected and when.
Ask who is in the Teamtailor pipeline for a role, and at which stage.
Connect Teamtailor with an API key and Memtro reads jobs with title and status, candidates with name and email, job applications with stage and rejection date, and the company's users with title and role. Phone numbers and CVs are never read. It reads on demand and there is no hourly sync. When you ask, with a read/write key, and once an administrator has granted the action by name, it can add comments, to-dos and candidates, put a candidate on a job, move applications between stages, create and publish job ads, raise requisitions, and add or permanently remove users.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Teamtailor tool, reads what it needs, and answers with the source cited.
These tools change something in Teamtailor. 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 Teamtailor, choosing the same kinds; the tab shows Teamtailor's own steps. Each event can start a job, with the event as its input. Teamtailor signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Teamtailor 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 in the pipeline for the senior designer role, and at which stage?
Which jobs are open in Teamtailor right now?
Which applications were rejected this week?
Move Priya Nair to the final interview stage for the backend role
Publish the Customer Success Manager job on our career site
The hiring manager at Acme asks who is in the running for the backend engineer job. Memtro reads the job's applications and lists each candidate by name with the stage they are at, and which were rejected and when.
Dan Fletcher finishes an interview with Priya Nair and asks Memtro to move her on. Memtro adds his comment on her application, written as him, and moves the application to the final interview stage. That stage's trigger in Teamtailor emails Priya a booking link.
The teams that lean on Teamtailor most, a question each of them asks, and what they connect beside it.
A record in Teamtailor 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.
Only a Company Admin can create the key: Teamtailor → Settings → Integrations → API keys → New API key, Admin scope, with read access, or read/write to let Memtro make the changes an administrator grants
Copy the key. Its scope cannot be edited afterwards, so make a new key to change it
In Memtro open Connections → Teamtailor, paste the API key, set Region to EU, NA or APAC (blank means EU), and connect
Ask who is in the pipeline for a role and at which stage
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Teamtailor tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a candidate, as a named Teamtailor user, optionally on one of their job applications; add a to-do about a candidate, assigned to a Teamtailor user, with an optional due date; add a new candidate as sourced by a recruiter, without emailing them; change a candidate's name, email, pitch, LinkedIn URL or tags; put a candidate on a job (a new application), emailing them only if asked; move a job application to another stage, which can fire that stage's triggers; create a job ad, as a draft unless a status is given; change a job: title, ad text, status (open, draft, unlisted, archived), tags or dates; edit a to-do's text or due date, or delete it; edit a comment's text, or delete it; raise a hiring requisition for approval; add a user, who is emailed an invitation, or remove one. 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. Only a Company Admin can create the key: Teamtailor → Settings → Integrations → API keys → New API key, Admin scope, with read access, or read/write to let Memtro make the changes an administrator grants.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Teamtailor, choosing the same kinds; the tab shows Teamtailor'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