Detect Sensitive Data Before It Leaks
Accidentally pasted an API key? Get flagged immediately so you can remove it.
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
Moderation Completion
Tool to classify input text or image for safety using a moderation model. use after receiving user-generated content to filter out unsafe material.
Why this helps
Accidental exposure of secrets or PII in new pages creates compliance and security risk. Discovery is late, damage is done.
- Catches accidental exposure immediately
- Prevents compliance violations before they escalate
- Reduces audit and legal risk
- Protects customer data and company credentials
Setup
Build it in a few focused steps.
- 1Connect Notion to Notis in the portal.
- 2Ask Notis 'Flag API keys, passwords, and credit card numbers in new pages' or create via Automations.
- 3Notis will scan every new page for sensitive data patterns (SSN, API keys, card numbers).
- 4Choose your alert method (urgent Slack ping, email to security lead).
- 5Test by creating a page with fake PII and verify immediate flagging.
Questions about this workflow
Will this flag false positives like fake examples in documentation?
It may. You can whitelist patterns or provide context (mark something as 'example for testing') to reduce false alarms.
What happens when PII is detected?
Notis alerts you immediately so you can delete it. The page stays accessible, but you're notified fast.
Does Notis scan the entire page or just certain fields?
It scans all content. You can limit scanning to specific sections or properties if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ai ml api. A trigger fires from one place; an action lands in another.
Notion triggers
Ai ml api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Moderation Completion
Tool to classify input text or image for safety using a moderation model. use after receiving user-generated content to filter out unsafe material.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Ai ml api, 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 Ai ml api.