Enrich a person when a research issue is created
When a Linear issue requests research on a named person, enrich the available person details in Crustdata and summarize useful context for the issue.
Connect Linear to Crustdata
When something happens in Linear, Notis takes the next step in Crustdata. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new comment is received.
Do this · Action
Enriches a person’s data from their LinkedIn profile, with selectable fields and real-time enrichment.
Examples
Ways Notis can move work from Linear to Crustdata
Scan companies named in new competitor issues
When a new Linear issue asks for competitor research and names a company, use Crustdata company screening to gather a useful company snapshot.
Check job listings when a company issue changes
When a Linear issue is updated with a company hiring research request, retrieve relevant job listing data through Crustdata for a compact hiring signal check.
Check funding milestones when a project date shifts
When a Linear project target date changes for a funding or market initiative, retrieve relevant company funding milestone timeseries data for the project context.
Review company posts after a project update
When a Linear project status update is posted, retrieve recent LinkedIn posts for companies discussed in the update and summarize relevant activity.
Check web traffic signals on company issue updates
When a company research issue changes, retrieve relevant Crustdata web traffic data and summarize the signal for the issue context.
Refresh workforce trends when a company issue changes
When an active Linear company issue is updated, retrieve relevant headcount timeseries data from Crustdata to help the team review workforce direction.
Search company records for a new research issue
When a Linear issue starts research about a company, use Crustdata company search to find matching records and summarize relevant results.
Find LinkedIn posts mentioned in a Linear comment
When a comment asks for LinkedIn coverage of a market phrase or company topic, search Crustdata posts by that keyword and summarize relevant results.
Supported Triggers and Actions
Notis builds workflows that link Linear to Crustdata. A trigger fires from one place; an action lands in another.
Linear triggers
Crustdata actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Enrich person screener
Enriches a person’s data from their LinkedIn profile, with selectable fields and real-time enrichment.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Fetch headcount by facet timeseries
Retrieves headcount timeseries data by facet using filters and pagination.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Fetch investor portfolio data
Finds companies whose investor list includes a specified investor and returns funding summaries.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
Filter decision makers data
Filters and retrieves decision maker data using conditions, title filters, and pagination.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Post funding milestone timeseries data
Retrieves company funding milestone timeseries data using filters and pagination.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Post headcount timeseries data
Retrieves headcount timeseries data from CrustData Data Lab using filters and pagination.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Post job listings table data
Searches indexed job listings.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
Post web traffic data
Retrieves web traffic data from CrustData using filters and pagination.
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 Linear and Crustdata
Connect any two apps with Notis in the middle.
Linear and Crustdata, 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 Crustdata.