Connect Abstract to Control d
When something happens in Abstract, 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
Do this · Action
Ways Notis can move work from Abstract to Control d
Screen Submitted Domains Before Adding DNS Rules
Validate submitted domains with Abstract, then add approved host rules to a specified Control D profile.
File Reviewed Domain Rules in a Control D Folder
Process a submitted domain request with Abstract, then create the approved custom rules in a specified profile folder.
Update a Control D Rule from a Reviewed Request
Use Abstract to process a change request, then update a specific existing custom rule by ID.
Apply Reviewed Changes Across Control D Rules
Process a request with Abstract and modify the specified existing custom rules in a Control D profile.
Review Control D Filter States on a Schedule
On a recurring schedule, inspect a specified profile's filters and change a named filter's enabled state when the instruction provides a clear reason.
Apply a Scheduled Batch of Filter Changes
At a chosen cadence, review a specified profile and bulk update its named filters when a supplied policy condition calls for it.
Review and Update External Filters on a Schedule
Revisit a specified Control D profile's external filters on a recurring schedule and update the specified third-party filter states under your policy.
Review a Control D Service Rule on a Schedule
At a recurring interval, review a specified service rule in a profile and change its blocking, bypass, spoof, or proxy redirect settings when your policy requires it.
Update a Control D Schedule from a Request
Process a schedule change request with Abstract and update the identified schedule in a specified Control D profile.
Supported Triggers and Actions
Notis builds workflows that link Abstract to Control d. A trigger fires from one place; an action lands in another.
Abstract triggers
Control d actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Device by ID
Permanently deletes a device, breaking DNS resolution on gadgets using its resolvers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Profile
Delete Profile Rule by Rule ID
Delete a custom DNS filtering rule from a profile.
Delete Rule from Folder
Delete Profile Schedule
Delete a schedule from a profile.
List Known Access IPs
List recent IP addresses used to query a device.
Get Analytics Endpoints
Lists available analytics regions and their endpoints.
Get Analytics Levels
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 Abstract and Control d
Connect any two apps with Notis in the middle.
Abstract and Control d, 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 Control d.