Turn reported risky domains into a Control D blocklist
When a Linear issue reports a confirmed risky domain, have Notis assess the request and add an appropriate custom rule to the relevant Control D profile.
Connect Linear to Control d
When something happens in Linear, Notis takes the next step in Control d. 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
Permanently deletes a device, breaking DNS resolution on gadgets using its resolvers.
Examples
Ways Notis can move work from Linear to Control d
Apply approved corrections to Control D rules
When a Linear issue update records an approved correction to a custom DNS rule, ask Notis to update the identified Control D rule.
Carry approved filter changes into Control D
When a Linear issue update approves a profile filter change, have Notis enable or disable the specified filter on the matching Control D profile.
Create focus-hour DNS schedules from Linear
When a Linear issue requests an agreed focus-hour policy, have Notis create the corresponding schedule in the identified Control D profile.
Prepare a Control D profile for a new project
When a Linear project is created for work that needs a distinct DNS policy, have Notis create a named Control D profile if the project clearly requests one.
Align Control D profile settings with project decisions
When a Linear project update records an approved policy-settings change, have Notis update the identified Control D profile fields.
Apply an approved bundle of Control D filters
When a Linear issue update approves a set of filter states, have Notis apply the specified changes together to the identified Control D profile.
Apply requested external filter changes
When a Linear issue contains an approved request to change a specific external filter on a Control D profile, have Notis update the filter state.
Update a Control D service rule from Linear
When a Linear issue update approves a service policy adjustment, have Notis modify the identified service rule on the appropriate Control D profile.
Supported Triggers and Actions
Notis builds workflows that link Linear to Control d. A trigger fires from one place; an action lands in another.
Linear triggers
Control d actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Delete Device by ID
Permanently deletes a device, breaking DNS resolution on gadgets using its resolvers.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Delete Profile
Permanently deletes a profile only if no devices enforce it; assigned profiles cannot be deleted.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Delete Profile Rule by Rule ID
Delete a custom DNS filtering rule from a profile.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
Delete Rule from Folder
Permanently deletes a custom DNS rule from a profile folder.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Delete Profile Schedule
Delete a schedule from a profile.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
List Known Access IPs
List recent IP addresses used to query a device.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Get Analytics Endpoints
Lists available analytics regions and their endpoints.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
Get Analytics Levels
Lists the available analytics levels for devices.
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 Control d
Connect any two apps with Notis in the middle.
Linear and Control d, 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 Control d.