Connect Adrapid to Control d

When something happens in Adrapid, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Adrapid to Control d

View example

Block campaign destinations in Control D

Use an Adrapid campaign export containing destination hostnames to create reviewed block rules in a Control D profile.

View example

Place Adrapid campaign rules in a Control D folder

Use supplied Adrapid campaign hostname data and a folder_id to create custom rules inside a specific Control D profile folder.

View example

Schedule Control D changes for an Adrapid launch

Create a Control D profile schedule from an Adrapid launch export that includes an exact profile, schedule details, and approved timing.

View example

Create a Control D profile for an Adrapid campaign

Provision a blank or cloned Control D profile using an Adrapid campaign export that names the requested profile options.

View example

Provision a Control D device for an Adrapid campaign

Create a Control D device from an Adrapid campaign request containing the exact device settings and profile assignment.

View example

Apply approved Adrapid settings to a Control D device

Modify one Control D device using an Adrapid export that includes the exact device ID and approved changes.

View example

Review Control D folders for an Adrapid campaign

Inspect the folders of a Control D profile named in an Adrapid export before organizing campaign rules.

View example

List root Control D rules for a campaign profile

List root custom rules for the Control D profile identified in a supplied Adrapid export, without duplicating folder-specific audits.

View example

Review native filters for a Control D campaign profile

Retrieve native filter states for the Control D profile specified in an Adrapid campaign export.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Control d. A trigger fires from one place; an action lands in another.

Adrapid 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

Delete Profile Rule by Rule ID

Delete a custom DNS filtering rule from a profile.

ActionInstant

Delete Rule from Folder

Permanently deletes a custom DNS rule from a profile folder.

ActionInstant

Delete Profile Schedule

Delete a schedule from a profile.

ActionInstant

List Known Access IPs

List recent IP addresses used to query a device.

ActionInstant

Get Analytics Endpoints

Lists available analytics regions and their endpoints.

ActionInstant

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.