Where a candidate stands in Pinpoint, which roles are open and what the team said.
Connect Pinpoint with your subdomain and an API key and Memtro reads jobs with status, deadline and pay range, applications with candidate, job, stage and hired or rejected dates, and their comments, never those for confidential jobs. The hourly sync writes each application into memory as it changes. When you ask, and once an administrator has granted the action by name, it can comment on an application, move it to another stage, update its details, and open, close or archive a job. Moving a stage can run automations that email the candidate. Deleting a comment or an application is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Pinpoint tool, reads what it needs, and answers with the source cited.
These tools change something in Pinpoint. 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 Pinpoint 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.
Pinpoint + MemtroWhich roles are open in Pinpoint, and when do they close?
Where does Priya Sharma's application for the Product Designer role stand?
How many people applied to the Senior Engineer job this month?
Move Dan Fletcher's application to the final interview stage
Close the Customer Success Lead job to new applications
On Monday the hiring manager asks how the Customer Success Lead role is going. Memtro reads the job and its applications, with each candidate's current stage and applied date, and the comments left on the shortlisted ones, and says who is waiting on a decision.
After a strong first call, recruiter Hannah Moss asks Memtro to move Priya Nair to the assessment stage and note that references are cleared. Memtro adds the comment as the system user and moves the application. The stage's automation sends Priya the assessment by email, and the hiring team sees the move.
The teams that lean on Pinpoint most, a question each of them asks, and what they connect beside it.
A record in Pinpoint 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
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMIn Pinpoint → Settings → API & Webhooks, switch the Pinpoint API toggle on (top right). The API does not answer without it
Open the API Keys tab, create a key and copy it. The key covers the whole account
In Memtro open Connections → Pinpoint, enter the Pinpoint subdomain, the first part of your address (for acme.pinpointhq.com enter acme), paste the API key and connect
Ask which roles are open and how many people have applied to each
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Pinpoint tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to an application; move an application to another stage, which may run that stage's automations and email the candidate; update an application's name, email, LinkedIn, hire or start date, or tags; open, close or archive a job; delete a comment; delete an application. 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. An hourly sync anchors recently changed Pinpoint records into memory as entities.
Pinpoint subdomain and API key. In Pinpoint → Settings → API & Webhooks, switch the Pinpoint API toggle on (top right). The API does not answer without 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
