Carry approved filter decisions into network protection
A clear review comment can trigger Notis to update the named Control D profile filters and summarize what changed.
Trigger
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Action
Bulk Update Profile Filters
Tool to bulk update filters on a specific profile. Use when you need to enable or disable multiple filters at once. Provide a list of filter IDs with desired states.
Why this helps
Approved security decisions can sit in comment threads until someone remembers to apply them.
- Connects a decision to the follow-through it needs.
- Keeps filter changes tied to review context.
- Returns a concise completion summary.
Setup
Build it in a few focused steps.
- 1Connect Notion and Control D to Notis once through the portal.
- 2Create an automation prompt that acts only on explicit filter decisions in review comments and asks Notis to confirm the intended profile and filters before changing them.
- 3Choose the Notion Comment Created trigger, scoped to the relevant review page if appropriate, and select a run-report channel.
- 4Test with a real comment that states one clear approved filter change.
Questions about this workflow
Can it interpret any comment as approval?
Write the prompt to act only when a comment explicitly states an approved change, and to seek clarification when details are ambiguous.
What does the action change?
It asks Control D to bulk update filter states on the identified profile.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Control d. A trigger fires from one place; an action lands in another.
Notion 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
Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Profile Rule by Hostname
Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Delete Profile Schedule
Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
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.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Get Analytics Endpoints
Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.
Connect any two apps with Notis in the middle.
Notion 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.