Connect Linear to 21risk
When something happens in Linear, Notis takes the next step in 21risk. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Linear to 21risk
Check compliance context for new issues
When a Linear issue arrives, retrieve relevant 21risk compliance data and send a concise snapshot to your chosen channel, so the team can see related checks before work begins.
Review 21risk items when issue details change
When a Linear issue changes, retrieve a focused list of relevant 21risk items and send the summary to your run-report channel to help you reassess risk without restarting your search.
Bring audit report context into issue discussions
When a Linear comment raises an audit question, retrieve matching 21risk reports and share a concise result in the run-report channel, helping the team move the discussion forward with existing evidence.
Recheck reports when project plans shift
When Linear project properties change, retrieve relevant 21risk reports and send a brief summary to your selected channel, making it easier to spot audit context after a change in priority, lead, or target date.
Add compliance context to project updates
When a Linear project update is posted, retrieve related 21risk compliance data and send a short digest to your chosen channel, so status reviews include relevant checks without a separate search.
Surface risk models for new projects
When a Linear project is created, retrieve available 21risk risk models and report suitable options to your chosen channel, helping the team consider the right assessment approach early.
Find risk categories for new compliance issues
When a Linear issue is created, retrieve relevant 21risk risk-model categories and send a short grouping suggestion to the run-report channel, giving issue triage a useful starting point.
Check monthly compliance patterns after issue changes
When an issue changes, retrieve relevant 21risk items-per-month facts and summarize the trend in your chosen channel, helping the team see whether a recurring concern needs attention.
Check property insurance context from issue comments
When a public-team Linear comment asks about a property's insurance details, retrieve matching 21risk property data and send the result to your run-report channel for an easier response.
Supported Triggers and Actions
Notis builds workflows that link Linear to 21risk. A trigger fires from one place; an action lands in another.
Linear triggers
21risk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Items (BETA)
Tool to retrieve items (beta) from the 21risk odata api. use when you need a filtered and paged list of items for analytics and reporting. example: get items($filter="item cost gt 100", $top=50).
Comment Received Trigger
Triggered when a comment is received.
Get Items Per Month
Tool to retrieve fact table data for itemspermonth, one row per question per site per month. use when querying monthly item data with odata parameters ($filter, $top, $skip, $select, maxpagesizeinmb).
Issue Created Trigger
Triggered when a new issue is created.
Get Organizations
Tool to retrieve organizations from the 21risk odata api. use when you need to list, filter, or paginate organizations via odata parameters after authentication is confirmed.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Properties
Tool to fetch a list of properties related to sites, including cope information and other relevant data. use when you need property insurance details via odata api after authentication.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get Reports
Tool to retrieve audit reports, including draft, published, and scheduled reports. use when you need a paginated list of reports with optional odata filtering.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get RiskModel Categories
Tool to retrieve risk model categories for grouping questions and compliance checks. use when you need to filter, select, or paginate risk model categories via odata parameters ($filter, $select, $orderby, $top, $skip, $count).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Risk Models
Tool to retrieve risk models used for audits and compliance. use when you need to list available risk models with optional odata queries.
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 recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
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.
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:
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
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.
More ways to connect Linear and 21risk
Connect any two apps with Notis in the middle.
Linear and 21risk, or any other combination from 1,000+ 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 21risk.