Turn a new Ashby role into a Linear launch checklist
When an Ashby role is ready to open, create a Linear issue with the role details and recruiting launch checklist.
When something happens in Ashby, Notis takes the next step in Linear. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when an application’s e-signature request is sent, cancelled, completed or deleted.
Do this · Action
Archives a Linear issue while preserving its data for future reference.
When an Ashby role is ready to open, create a Linear issue with the role details and recruiting launch checklist.
Send a candidate milestone to a related Linear issue as a concise comment so the hiring team can see the latest context.
Use an Ashby interview update to refresh the related Linear issue with scheduling context and the next coordination step.
On a recurring schedule, review Ashby candidate pipeline context and create Linear follow-up issues for candidates who appear to need action.
Review upcoming Ashby interviews on a schedule and comment on the relevant Linear hiring issue with a compact readiness summary.
On a schedule, review Ashby hiring pipeline context and update existing Linear issues when a candidate's next step or priority has changed.
Create a scheduled, concise recruiting roundup from Ashby pipeline context as a comment on a specified existing Linear issue.
Notis builds workflows that link Ashby to Linear. 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.
Archives a Linear issue while preserving its data for future reference.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a comment to an issue; this shared workspace change cannot be undone.
Triggers when an application’s e-signature request is sent, cancelled, completed or deleted.
Confirm the project name before archiving, especially in bulk; it leaves active views but can be unarchived later.
Triggers when a candidate submits an application or a recruiter adds one; excludes imports, syncs, and later changes.
Creates an issue in a specified Linear team with the supplied details.
Fires when an existing application changes; enabling hire or stage triggers too sends two events per action.
Hides a project update from active views while keeping its data; it is irreversible only until it is unarchived.
The update is archived, not permanently deleted: it is hidden from the default and active views and its data is preserved. It can be unarchived later; the action is irreversible only in the sense that the update stays hidden until it is explicitly unarchived.
Fires when a candidate record is deleted, not when it is merged into another record.
Retrieve a team's default issue estimate and workflow state for new issue forms.
Fires when a candidate’s recent emails may have changed; messages are absent and the beta may not be enabled.
Creates an attachment and associates it with an existing issue.
Fires when a candidate is marked hired, including for confidential jobs.
Creates a label for a Linear team or returns an existing label with the exact same name.
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.
Ashby and Linear, 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 Linear.