Turn a Notion role brief into an Ashby draft job
When a new hiring request is added to Notion, ask Notis to create a corresponding draft job in Ashby so the role has a clear home without retyping the brief.
When something happens in Notion, 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
Fires when a new comment is created in the accessible workspace.
Do this · Action
Add a candidate to a recruiting project.
When a new hiring request is added to Notion, ask Notis to create a corresponding draft job in Ashby so the role has a clear home without retyping the brief.
When a Notion hiring request changes, have Notis recognize an approved headcount plan and create an Ashby opening, helping the next recruiting step happen without a reminder chain.
When a referral intake page is created in Notion, ask Notis to create the candidate in Ashby so a promising introduction does not remain buried in notes.
When a new Notion referral page contains an explicit job referral, ask Notis to submit it through Ashby's referral action so the candidate enters the right recruiting flow.
When a Notion candidate note changes, ask Notis to add the relevant update as an Ashby candidate note, preserving context where the recruiting team works.
When a new Notion sourcing review identifies a candidate and a useful existing Ashby tag, ask Notis to apply that tag to make later filtering simpler.
When a Notion sourcing plan is updated with a candidate, ask Notis to add that candidate to the corresponding Ashby recruiting project and keep the initiative organized.
When a Notion hiring tracker records a clear stage decision, ask Notis to move the matching Ashby application to that interview stage so the pipeline does not lag behind the team's decision.
When a new Notion candidate page explicitly says the person should enter a specific role's process, ask Notis to create the matching Ashby application.
Notis builds workflows that link Notion to Ashby. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a candidate to a recruiting project.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add an existing tag to a candidate’s profile.
Fires when a new comment is created in the accessible workspace.
Assign a team member to a hiring team.
Fires when a new database container is created.
Adds a completed partner assessment to an Ashby candidate; requires candidatesWrite permission.
Fires when a new data source is created in the workspace.
Add a user to a pool of interviewers.
Fires when a data source’s columns are added, removed, or renamed.
Attaches an existing partner email to an Ashby candidate without sending it; requires candidatesWrite permission.
Fires when the body content of an accessible page is updated.
Link an existing job to a job requisition.
Fires when a new page is created in the accessible workspace.
Associate a location with an existing job requisition.
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.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
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.
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.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Ashby, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Ashby.