Turn a clear profile request into an update
Create a request page with the intended Control D profile change, then let Notis review it and update the profile details.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Update Profile by ID
Tool to modify an existing profile by ID. Use when you need to update profile fields after confirming the current profile. Example: Update profile '123abc' with new name and settings.
Why this helps
Configuration requests can be documented without making it clear who will carry them into Control D.
- Makes the handoff from request to configuration explicit.
- Keeps the source request easy to revisit.
- Reports what Notis could apply or needs clarified.
Setup
Build it in a few focused steps.
- 1Connect Notion and Control D to Notis once through the portal.
- 2Create an automation prompt that applies only approved, clearly described updates to the identified profile.
- 3Select the Notion Page Created trigger for the request page location and choose where reports should go.
- 4Test with one real request and review the resulting profile.
Questions about this workflow
Can the prompt update any profile setting?
It can ask Notis to modify a profile by ID. State which changes are allowed and how to identify the profile.
Should the request be approved first?
Yes, describe a clear approval signal in your prompt so drafts or questions do not cause changes.
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.