Turn a Slack hiring request into an Ashby draft job
Capture a clearly stated new role request from Slack as a draft job in Ashby, so the hiring idea has a home before it gets lost in chat.
Connect Slack to Ashby
When something happens in Slack, Notis takes the next step in Ashby. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new channel is created.
Do this · Action
Add a candidate to a recruiting project.
Examples
Ways Notis can move work from Slack to Ashby
Capture candidate referrals from Slack in Ashby
Turn a clearly described employee referral in a Slack channel into an Ashby referral, preserving the recommendation in the recruiting pipeline.
Save Slack interview observations as Ashby candidate notes
Capture a specific interview observation shared in a recruiting channel as a candidate note in Ashby, keeping useful context with the candidate.
Tag candidates when the team shortlists them in Slack
Use a team's chosen Slack reaction on a candidate discussion as a signal to add an existing shortlist tag to that candidate in Ashby.
Start an Ashby application from a clear Slack hiring decision
When a recruiting channel explicitly agrees to consider a known candidate for a known job, ask Notis to create the Ashby application.
Save founder candidate context from Slack DMs
Capture a clear candidate-specific recruiting observation from a Slack DM as an Ashby note, so a useful detail does not stay in a private conversation.
Add sourced candidates to the right Ashby project
When a Slack message clearly identifies a candidate and sourcing initiative, ask Notis to associate that candidate with the existing Ashby project.
Correct an application source from a Slack clarification
When the team clarifies in Slack how a candidate entered the process, ask Notis to update the Ashby application's source attribution.
Record an explicit candidate stage decision from Slack
After the team clearly agrees on a candidate's next stage, ask Notis to move the identified Ashby application to that stage.
Supported Triggers and Actions
Notis builds workflows that link Slack to Ashby. A trigger fires from one place; an action lands in another.
Slack triggers
Ashby actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Add Candidate to Project
Add a candidate to a recruiting project.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Add Candidate Tag
Add an existing tag to a candidate’s profile.
ActionInstant
New Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Add Hiring Team Member
Assign a team member to a hiring team.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Add Completed Assessment to Candidate
Adds a completed partner assessment to an Ashby candidate; requires candidatesWrite permission.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Add User to Interviewer Pool
Add a user to a pool of interviewers.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Add Existing Email Message to Candidate
Attaches an existing partner email to an Ashby candidate without sending it; requires candidatesWrite permission.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
Add Opening Job
Link an existing job to a job requisition.
ActionInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
Add Opening Location
Associate a location with an existing job requisition.
ActionInstant
Trigger Types
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
New Notion pageStripe chargeCalendar event
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
Why AI automation
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Related pairs
More ways to connect Slack and Ashby
Connect any two apps with Notis in the middle.
Slack and Ashby, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Ashby.