Have we met before
A name comes up in a referral. Memtro finds Amara Osei in Ashby by email, shows her earlier application, the stage it reached and the archive reason, so the hiring manager knows the history before replying.
Ashby + Memtro
Ask who applied, where they stand and who is interviewing this week in Ashby.
Connect Ashby with an API key and Memtro reads your jobs with department, location and hiring team, careers page postings, applications with each candidate's current stage, one candidate in full, and upcoming interviews. It never reads compensation. Every hour the sync writes each new application into memory. When you ask, and once an administrator has granted the action by name, it can add and edit candidates, leave notes and tags, put candidates forward, move or archive applications, open or close jobs, publish postings and cancel interviews. Archiving can send the candidate a rejection email, which cannot be recalled.
In Memtro
What you can do with Ashby in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Ashby tool, reads what it needs, and answers with the source cited.
What it does
- 01Jobs by status (Open, Closed, Archived, Draft) with department, location, hiring team and interview stages
- 02Postings live on the careers page, with published date, deadline and public link
- 03Applications by job, status or date, and candidates by name or email with tags and their applications
- 04Upcoming interviews with start and end, meeting link, interviewers and whether feedback is in
- 05When asked and granted, creates and edits candidates, adds notes and tags, puts a candidate forward for a job, and moves an application between stages, running that stage's automations
- 06When asked and granted, archives an application with a rejection email to the candidate if a template is named, opens or closes jobs, publishes or takes down public postings, and cancels interview schedules
Acts when asked
When you ask it to
These tools change something in Ashby. 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.
- 01Add a candidate
- 02Edit a candidate's name, email, links, source, credited user or location
- 03Leave a note on a candidate
- 04Add a tag to a candidate, or take one off
- 05Put a candidate forward for a job, as a new application
- 06Change an application's source or credited user
- 07Move an application to another interview stage, or archive it with a reason, optionally emailing the candidate a rejection
- 08Open, close, archive or return a job to draft
- 09Publish a job posting on the careers page, or take it down
- 10Cancel an interview schedule
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Ashby for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Ashby signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01An application was submitted, or a candidate added by hand
- 02An application changed (fields, moved to another job)
- 03A candidate moved to another stage
- 04A candidate was hired
- 05A candidate was deleted
- 06Two candidates were merged
- 07An interview schedule was created
- 08An interview schedule changed (scheduled, moved or cancelled)
- 09A job switched interview plan
- 10A job was created
- 11A job changed
- 12A job posting was published
- 13A job posting was unpublished
- 14A job posting changed
- 15A job posting was deleted
- 16An offer process was started
- 17An offer changed
- 18An offer process was deleted
- 19An opening was created
- 20An opening changed
- 21An opening was deleted
- 22A candidate was pushed to the HRIS
- 23A take-home assignment was completed
- 24An e-signature request changed
In practice
Ask it like you would a colleague
Once Ashby 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.
Ashby + MemtroWhich applications for Staff Engineer are in the Technical Interview stage?
Who is interviewing this week, and has feedback been submitted?
Has Amara Osei applied before, and where did it end?
Which jobs are open in the Data department, and who is on each hiring team?
Move Amara Osei's Staff Engineer application to the onsite stage
Putting a referral forward
Jake Turner, an engineering manager at Northwind, asks Memtro to add his former colleague Lena Park for the Staff Engineer role with a note on why. Memtro creates the candidate, puts her forward for the job at its first stage and leaves the note, which the hiring team see in Ashby.
Teams
Where it fits
The teams that lean on Ashby most, a question each of them asks, and what they connect beside it.
- People and onboardingThe answers a new hire would otherwise ask around forNew starter, Manager, People lead, Hiring manager“How do I request a laptop, and who approves it?”Used alongside Confluence, Notion, Google Drive, Slack, Google Calendar and 5 more.
- LeadershipOne question across the whole companyFounder, Chief executive, Department head, Board member“What happened with our top ten accounts this week, and is anything at risk?”Used alongside HubSpot, Help Scout, Xero, Stripe, Linear and 6 more.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
Better together
Works with
A record in Ashby 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.
- Finance and commerceAshby with XeroInvoices, bills, contacts and reports, answered in plain English with figures cited to Xero.
- Finance and commerceAshby with StripeCustomers, charges, invoices and subscriptions through a restricted key.
- Finance and commerceAshby with FellohBookings, payments, refunds, chargebacks, supplier payments and payouts from the travel payments platform.
- Work managementAshby with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementAshby with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementAshby with LinearIssues, projects and teams, synced hourly into memory.
- Email, calendar and chatAshby with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatAshby with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatAshby with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
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.
BambooHR- Personio
- Microsoft Entra ID
- Google Workspace
- HiBob
- Greenhouse
Breathe HR
Lever
Workable
Deel
Factorial HR
Pinpoint
Recruitee- Teamtailor
CharlieHR
Deputy
Humaans- Connecteam
JazzHR- Rippling
- Sage HR
SmartRecruiters- Staffology Payroll
- Bonusly
Lattice- Canvas LMS
- Moodle
15Five
Homerun- Hubstaff
Jibble
Leapsome
LearnUpon
Planday- Remote
7shifts
Timetastic
Recruit CRM
Setup
How to connect
Connect withAPI key
- 1
In Ashby open Admin → Integrations → API Keys → Create and tick the read permissions: Jobs, Candidates, Organization, API keys, Hiring process metadata and Communication templates
- 2
Add Candidates: write, Jobs: write and Interviews: write only for the actions you want. A key with the read permissions alone reads everything and refuses the rest
- 3
In Memtro open Connections → Ashby, paste the API key and connect. Memtro checks it against Ashby and names the connection after the key
- 4
Ask who is interviewing this week
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Ashby tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Ashby?+
Only when you ask, and only what it has been granted: add a candidate; edit a candidate's name, email, links, source, credited user or location; leave a note on a candidate; add a tag to a candidate, or take one off; put a candidate forward for a job, as a new application; change an application's source or credited user; move an application to another interview stage, or archive it with a reason, optionally emailing the candidate a rejection; open, close, archive or return a job to draft; publish a job posting on the careers page, or take it down; cancel an interview schedule. 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 Ashby 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 Ashby 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. An hourly sync anchors recently changed Ashby records into memory as entities.
How do I connect Ashby?+
API key. In Ashby open Admin → Integrations → API Keys → Create and tick the read permissions: Jobs, Candidates, Organization, API keys, Hiring process metadata and Communication templates.
Can Ashby start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Ashby for you. 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 Ashby in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.