Connect Adrapid to Dnsfilter

When something happens in Adrapid, Notis takes the next step in Dnsfilter. 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 Dnsfilter

View example

Turn an Adrapid location brief into a DNSFilter network

Send an Adrapid generated location or campaign operations brief and create the matching DNSFilter network.

View example

Create a DNSFilter policy from an Adrapid security brief

Convert an Adrapid campaign security brief into a DNSFilter policy with explicitly supplied rules.

View example

Add Adrapid approved domains to DNSFilter policies

Apply a supplied Adrapid approved-domain export across selected DNSFilter policies.

View example

Block Adrapid flagged domains across DNSFilter policies

Use an Adrapid threat or campaign review export to bulk block explicitly listed domains.

View example

Allow an Adrapid approved application in DNSFilter

Add one explicitly approved application from an Adrapid campaign or production brief to a DNSFilter policy.

View example

Block an Adrapid flagged application in DNSFilter

Block an explicitly identified application from an Adrapid risk or compliance export.

View example

Submit an Adrapid suspicious domain for DNSFilter threat review

Ask DNSFilter to evaluate a suspicious FQDN identified in an Adrapid export.

View example

Create a DNSFilter report schedule from an Adrapid brief

Create a scheduled DNSFilter report when an Adrapid operations brief supplies the required organization and frequency.

View example

Refresh a DNSFilter report preview from an Adrapid reporting export

On a chosen schedule, submit a supplied Adrapid reporting export to generate a DNSFilter scheduled report preview.

Supported Triggers and Actions

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

Adrapid triggers

Dnsfilter actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create IP Address

Adds an IP address to a network for filtering policies.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Allowed Application

Allows an application through a policy, regardless of other blocking rules.

ActionInstant

Get Application Category

Retrieves details about an application category.

ActionInstant

Add Allowlist Domains to Policies

Adds domains to the allow lists of multiple policies, bypassing their filtering rules.

ActionInstant

Get Billing Information

Retrieves billing records for an organization, including amounts and billing periods.

ActionInstant

Add Blacklist Category To Policy

Adds a content category to a policy’s block list without changing other settings.

ActionInstant

Get Category

Retrieves basic information about a category.

ActionInstant

Add Blacklist Domain To Policy

Blocks a domain for users covered by a policy.

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.