Connect ActiveMerge to Control d

When something happens in ActiveMerge, 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 ActiveMerge to Control d

View example

Apply a signed DNS blocklist

After a network policy document is signed in ActiveMerge, send its approved domains to Control D as profile rules.

View example

File approved DNS rules in a folder

Route approved domains from an ActiveMerge policy document into a selected Control D profile folder.

View example

Schedule an approved access window

Use an approved ActiveMerge schedule document to create a Control D profile schedule.

View example

Create a profile for an approved policy

Create a Control D profile when an ActiveMerge policy package is approved and a new profile is needed.

View example

Update device settings from an approved change

Pass an approved ActiveMerge device change to Control D to modify the confirmed device.

View example

Review Control D profiles on a schedule

Get a recurring inventory of Control D profiles to support a regular review of ActiveMerge policy documents.

View example

Collect profile schedules for review

On a recurring schedule, gather Control D profile schedules so approved time windows can be checked against current settings.

View example

Prepare a monthly profile analytics summary

Retrieve a Control D profile analytics summary on a recurring cadence for review alongside your policy documents.

Supported Triggers and Actions

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

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