Before the panel
An interviewer asks what has happened with Priya Nair so far. Memtro reads her Workable timeline: the phone screen, who rated her and the comments left, and sums it up before the panel sits down.
Jobs, candidates and every stage of the pipeline from Workable, remembered as hires happen.
Connect Workable with your account subdomain and an access token and Memtro reads your jobs by state, each job's description and pipeline stages, candidates by job or stage, and a candidate's profile and activity timeline. Salary is never read. Every hour the sync writes each new candidate into memory. When asked, and once an administrator has granted each action by name, it comments, moves, rates, tags, disqualifies or reinstates candidates, and adds, copies or relocates them between jobs, all as the acting member. Moves and disqualifications can trigger Workable's emails to the candidate, and relocating deletes the original record permanently.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Workable tool, reads what it needs, and answers with the source cited.
These tools change something in Workable. 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 Workable 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.
Which candidates for the Senior Backend Engineer role are in the interview stage?
Who applied for the Account Executive job in the last two weeks, and where are they now?
Summarise Priya Nair's timeline: who has spoken to her and what did they say?
Which jobs are published right now, by department?
Move Tom Okafor to Technical interview and note that the phone screen went well
An interviewer asks what has happened with Priya Nair so far. Memtro reads her Workable timeline: the phone screen, who rated her and the comments left, and sums it up before the panel sits down.
Zoe Clarke asks Memtro to move Tom Okafor to the technical interview and add her notes. Memtro reads his timeline, posts the comment for the hiring team as the acting member, and moves him to the stage, where the account's interview invitation automation emails him.
The teams that lean on Workable most, a question each of them asks, and what they connect beside it.
A record in Workable 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 Workable open the account menu (top right) → Integrations → Generate new token, ticking r_jobs and r_candidates, plus w_candidates for the candidate actions or w_comments for comments alone. Leave r_employees unticked. The token is shown once
In Memtro open Connections → Workable, paste the Access token and your Account subdomain (the acme in acme.workable.com), and connect
For the actions, add the login email of the Workable member they should be recorded against as the acting member
Ask who is in the interview stage for your open roles
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Workable tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a candidate's timeline; move a candidate to another stage of their job; disqualify a candidate (rejected or withdrew); reinstate a disqualified candidate; rate a candidate; add or remove a candidate's tags; add a candidate to a job; copy a candidate to another job; relocate a candidate to another job (the original is removed). 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 Workable records into memory as entities.
Account subdomain and access token. In Workable open the account menu (top right) → Integrations → Generate new token, ticking r_jobs and r_candidates, plus w_candidates for the candidate actions or w_comments for comments alone. Leave r_employees unticked. The token is shown once.
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