Teamtailor + Memtro

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.

In Memtro

What you can do with Teamtailor in Memtro

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.

What it does

  1. 01Jobs with title and status, and when each was created and changed
  2. 02Candidates with name, email, and when added and last changed, to browse page by page
  3. 03Job applications: which candidate applied to which job, the stage, and when changed or rejected, and the company's users with title and role
  4. 04When asked and granted, adds, edits or deletes comments and to-dos on a candidate, adds a sourced candidate without emailing them, or changes a candidate's details
  5. 05When asked and granted, puts a candidate on a job, emailing them only if asked, or moves an application to another stage, whose triggers may email the candidate
  6. 06When asked and granted, creates a job ad or publishes it on the career site, raises a requisition for approval, and adds a user, who is emailed an invitation, or permanently removes one

Acts when asked

When you ask it to

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.

  1. 01Add a comment to a candidate, as a named Teamtailor user, optionally on one of their job applications
  2. 02Add a to-do about a candidate, assigned to a Teamtailor user, with an optional due date
  3. 03Add a new candidate as sourced by a recruiter, without emailing them
  4. 04Change a candidate's name, email, pitch, LinkedIn URL or tags
  5. 05Put a candidate on a job (a new application), emailing them only if asked
  6. 06Move a job application to another stage, which can fire that stage's triggers
  7. 07Create a job ad, as a draft unless a status is given
  8. 08Change a job: title, ad text, status (open, draft, unlisted, archived), tags or dates
  9. 09Edit a to-do's text or due date, or delete it
  10. 10Edit a comment's text, or delete it
  11. 11Raise a hiring requisition for approval
  12. 12Add a user, who is emailed an invitation, or remove one

Events

When it happens

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 webhooks
  • 01A candidate was created
  • 02A candidate was updated
  • 03A candidate was deleted
  • 04A job was created
  • 05A job was updated
  • 06A job was deleted
  • 07A job application was created
  • 08A job application changed (stage, rejection, job)
  • 09A job application was deleted
In practice

Ask it like you would a colleague

Once 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.

Teamtailor + Memtro
  • 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

01

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.

02

After the interview

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.

Teams

Where it fits

The teams that lean on Teamtailor most, a question each of them asks, and what they connect beside it.

Better together

Works with

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.

Also in People and HR

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    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

  2. 2

    Copy the key. Its scope cannot be edited afterwards, so make a new key to change it

  3. 3

    In Memtro open Connections → Teamtailor, paste the API key, set Region to EU, NA or APAC (blank means EU), and connect

  4. 4

    Ask who is in the pipeline for a role and at which stage

Also works from

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.

FAQ

Questions

Can Memtro change anything in Teamtailor?+

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.

Who can use a Teamtailor connection?+

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.

Does Memtro store my Teamtailor data?+

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.

How do I connect Teamtailor?+

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.

Can Teamtailor start a job?+

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.

Connect Teamtailor in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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