Recheck vulnerability context when software details change
A version change can alter the security picture; bring the record back into review automatically.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
/v1/cve
Why this helps
Security notes can become outdated when the recorded software version changes without a renewed check.
- Revisit CVE context after inventory changes.
- Keep security review connected to updated software records.
- Reduce manual reminders to rerun a lookup.
Setup
Build it in a few focused steps.
- 1Connect Notion and api.kadec0.xyz to Notis once in the portal.
- 2Ask Notis to rerun a CVE lookup for updated software details and report possible matches for verification.
- 3Select Page Properties Updated on the software inventory data source.
- 4Choose where runs are reported and test by updating one software record.
Questions about this workflow
Will this run on every property change?
The selected trigger runs on page property updates. Describe the intended security review and inspect initial runs.
Should teams act on a match immediately?
Use results to prioritize verification; confirm the exact product and version before deciding on remediation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to api.kadec0.xyz. A trigger fires from one place; an action lands in another.
Notion triggers
api.kadec0.xyz actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
/v1/youtube
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
/v1/serp-batch
All Page Events
Triggers when any Notion page is created or updated across the workspace.
/v1/scrape
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.
/v1/enrich
New Comment
Triggers when a new comment is added to a specified Notion block or page.
/v1/serp-read
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.
/v1/cve
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.
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.
Connect any two apps with Notis in the middle.
Notion and api.kadec0.xyz, 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 api.kadec0.xyz.