Skip to content
Notis

Move confirmed audit domains into Control D rules

When an audit identifies domains that need blocking, send the confirmed findings to Notis and add them to the right Control D profile.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Create Custom Rules for Profile

Tool to create custom rules for a profile. Use after confirming the profile ID and preparing rule definitions. Provide a list of rule objects matching the API schema.

Why this helps

Copying domain findings from an audit into DNS rules creates busywork and risks missing a confirmed item.

  • Reduce manual re-entry of confirmed domain findings.
  • Keep profile changes tied to an explicit audit request.
  • Review the created rules in Control D after each run.

Setup

Build it in a few focused steps.

  • 1Connect 21risk and Control D once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Tell Notis to create Control D custom rules for confirmed domain findings in a 21risk audit, and state the profile and desired rule behavior.
  • 4Choose the notis_webhook trigger and where run reports should go.
  • 5Test with one real audit finding and verify the rule in Control D.

Questions about this workflow

Does 21risk start this workflow automatically?

No. 21risk has no listed trigger events. A webhook request starts this workflow, and you provide the audit finding in that request.

What information should I include?

Include the confirmed domain, the Control D profile ID, and the intended rule behavior. Notis cannot infer missing profile or policy choices.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

21risk 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

Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Profile by ID

Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.

ActionInstant

Delete Profile Rule by Hostname

Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.

ActionInstant

Delete Profile Rule by Rule ID

Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.

ActionInstant

Delete Profile Rule in Folder

Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.

ActionInstant

Delete Profile Schedule

Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

ActionInstant

List Known Access IPs

Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.

ActionInstant

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.

ActionInstant

Connect any two apps with Notis in the middle.

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