Make customer record updates privacy-aware
Handle sensitive details as part of routine record changes, without relying on someone to remember a separate cleanup step.
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
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Why this helps
Updated records can introduce new personal details after an earlier review is already complete.
- Catch sensitive strings introduced during routine property changes.
- Reduce privacy review tasks competing with founder work.
- Apply the same anonymization instruction whenever records change.
Setup
Build it in a few focused steps.
- 1Connect Notion and Anonyflow to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis in one plain-language prompt to review changed record properties for sensitive string values and submit relevant strings to Anonyflow for anonymization.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test with a sample record change using dummy values.
Questions about this workflow
Will a schema change trigger this too?
Adding a column can trigger page property updates for existing rows. For a single structural-change signal, use the Data Source Schema Updated event instead.
Does this require manually selecting fields?
No field-mapping screen is involved. Describe the intended behavior in the automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Anonyflow. A trigger fires from one place; an action lands in another.
Notion triggers
Anonyflow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Deanonymize Packet
Tool to deanonymize a json data packet using your private key. use after receiving an anonymized packet to recover specific fields.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Deanonymize Value
Tool to deanonymize one or more anonymized string values. use when you need to recover the original plaintext values after encryption-based anonymization. example: `deanonymizevalue().execute(deanonymizevaluerequest(data=["<anonymized string>"]))`
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.
Test Connection
Tool to test the connection to the anonyflow api. use when verifying that the anonyflow service is reachable and operational before performing anonymization tasks. example: `testconnection().execute(testconnectionrequest())`
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 Anonyflow, 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 Anonyflow.