Your
Ashby always
one message away
Create candidates, update application stages, and look up jobs and interviews in Ashby from your messaging apps by voice or text.
Mailchimp
Ashby
Six ways to run it from a message.
Drive it by message when you need it, or put it on autopilot.
Capture candidates
Turn a voice memo or forwarded email into an Ashby candidate record with contact details and social profiles.
Update applications
Move an application between interview stages with a message like “Move Jordan Lee to the onsite interview stage.”
Ask about recruiting
Ask “Which interviews are scheduled for this application?” and get details from Ashby interview schedules.
Recruiting summaries
Get scheduled summaries of Ashby applications, candidates, job postings, and interview schedules delivered to your messages.
React to applications
When an application is submitted in Ashby, get a message with the recruiting event so you can follow up.
Ashby in your messages
Reach Ashby from WhatsApp, Telegram, or Slack to check candidates, applications, jobs, and interview schedules.
Ashby, from anywhere you
message.
Pick the channel you already live in. Notis turns it into a fully native Ashby remote.
Telegram
Voice-first Ashby bot. Record, tag, file.
WhatsApp business or personal, both work.
Slack
Slash-command your way through any workspace.
iMessage
Native bubbles. iPhone, iPad and Mac.
Gmail
Forward emails. Get them filed in Ashby.
Notis Desktop
Run from Notis desktop with hotkeys & history.
What people automate with
Ashby + Notis.
Record candidate interview confirmations
When a candidate accepts a Google Calendar interview invitation, add a confirmation note to their Ashby profile.
Capture declined interview invitations
When a candidate declines a Google Calendar interview invitation, put the decline on their Ashby candidate record for coordinator follow-up.
Flag tentative candidate responses
If a candidate marks an interview invite tentative, document the tentative status in Ashby without treating the meeting as confirmed.
Log canceled candidate interviews
When a candidate interview is canceled in Google Calendar, record the cancellation in Ashby only if the sparse event ID can be resolved to a known candidate.
Document interview time changes
When the start or end time of a candidate interview changes, add an Ashby note with the old and new times after matching the event to the candidate.
Record interview location changes
When an interview location or join link changes, note the revised logistics in Ashby for the matched candidate.
Supported triggers and
actions
Notis builds workflows that link this app to anything else. A trigger fires from one place; an action lands in another.
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Application Signature Request Updated
Triggers when an application’s e-signature request is sent, cancelled, completed or deleted.
Application Submitted
Triggers when a candidate submits an application or a recruiter adds one; excludes imports, syncs, and later changes.
Application Updated
Fires when an existing application changes; enabling hire or stage triggers too sends two events per action.
Candidate Deleted
Fires when a candidate record is deleted, not when it is merged into another record.
Candidate Emails Changed
Fires when a candidate’s recent emails may have changed; messages are absent and the beta may not be enabled.
Candidate Hired
Fires when a candidate is marked hired, including for confidential jobs.
Candidate Merged
Fires when two candidate records merge; their history remains on the record named in the event.
Candidate Moved To Interview Stage
Fires when an application changes interview stage in either direction, or when a candidate is hired.
Candidate Pushed To HRIS
Fires when a hired candidate is transferred to an HRIS, which may happen minutes or days after hiring.
Interview Schedule Created
Fires when an interview loop is first booked; the schedule-updated event fires at the same time.
Interview Schedule Updated
Fires when a booked interview loop or interview changes, and once at booking alongside the schedule-created trigger.
Job Created
Fires when an internal job requisition is created; confidential jobs are excluded.
Job Interview Plan Switched
Fires when a job switches interview plans, remapping stages for every application in progress.
Job Posting Deleted
Fires when a job posting is deleted, not when it is merely removed from its job board.
Job Posting Published
Fires when a job posting is published; the job-posting-updated event also fires.
Job Posting Unpublished
Triggers when a job posting is removed from its board but kept in Ashby.
Job Posting Updated
Fires when a job posting changes, including on publication or withdrawal; those events also fire.
Job Updated
Fires when an internal job opens, closes, or changes interview plan; confidential jobs are excluded.
Offer Created
Fires when an offer process starts; later offer changes trigger the offer-updated event.
Offer Deleted
Fires when an offer process is deleted; deleted offers no longer appear in list results.
Offer Signature Request Updated
Fires when an offer letter’s e-signature request is sent, cancelled, completed or deleted.
Offer Updated
Fires when an offer is drafted, approved, or accepted or declined; offer creation has a separate trigger.
Opening Created
Fires when a headcount opening is created; no opening update or deletion events are available.
Survey Submitted
Survey submissions trigger this, except anonymous Candidate Experience surveys; Diversity and EEOC answers are omitted.
Take-Home Assignment Assigned
Fires when a take-home assignment is issued and awaits submission; the candidate has not submitted it yet.
Take-Home Assignment Cancelled
Fires when a take-home assignment is cancelled, whether or not the candidate submitted it.
Take-Home Assignment Completed
Fires when reviewers finish evaluating a take-home assignment, not when the candidate submits it.
Take-Home Assignment Submitted
Fires when a candidate submits a take-home assignment; review has not happened yet.
Connect any two apps
with AI in the middle.
Choose the app that starts the workflow and the app that should react. Notis sits in between, reading each event, deciding what matters, and writing the result exactly where it belongs.
When this happens · Trigger
Do this · Action
Popular pairs
Connect Ashby to
1,500+ integrations in one click.
Start with a managed app, then go beyond the catalog with any MCP server, any CLI tool, or one of 3,900+ tools and APIs you never sign up for at all. Notis uses all of them from the same conversation.
1,500+ managed integrations
Choose a supported app and connect it in one click. Notis handles access and makes its actions available to every agent.
Browse integrationsCustom MCP servers
Bring any remote or local Model Context Protocol server. Its tools become available to Notis like any managed integration.
Set up a custom MCPCLI tools
Use any Linux command line on your Cloud Computer. Notis can install it, run it, and bring the result back to your conversation.
Install a CLI tool3,900+ pay-per-use tools
Semrush, Apollo, Apify and more are already wired in. No account, no API key, no subscription: each call comes out of your plan.
Browse pay-per-use toolsStart saving time today.
Connect in 60 seconds. No DIY, no maintenance, no setup tax.