Check operational data when Notion columns change
A column change can ripple into downstream work. Query Appdrag for the records you need to review while the change is fresh.
Trigger
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.
Action
Visual SQL SELECT
Tool to execute a Visual SELECT Cloud Backend function. Use when you need to read rows from a database table using a visual SQL function configured in AppDrag.
Why this helps
Structural edits can create hidden follow-up work across systems, making it harder to know what may need attention.
- Pairs structural changes with a deliberate dependency check.
- Helps surface relevant operational records for review.
- Reduces the chance that database maintenance becomes a forgotten task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Appdrag to Notis once through the portal.
- 2Create an automation or ask Notis to query Appdrag after a Notion data source schema changes.
- 3Describe which dependency information should be retrieved in one plain-language instruction.
- 4Choose the Notion Data Source Schema Updated trigger and pick a channel for run reports.
- 5Make a safe test column change and confirm the Appdrag lookup returns the intended records.
Questions about this workflow
Does the query modify Appdrag data?
No. Visual SQL SELECT is used to read records for the follow-up.
What types of changes trigger it?
The Notion schema event applies to column additions, removals, and renames.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Appdrag. A trigger fires from one place; an action lands in another.
Notion triggers
Appdrag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute Cloud Backend function via DELETE
Tool to execute a Cloud Backend API function via DELETE on the default environment. Use when you need to call a function with DELETE parameters and optional APIKey.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Preprod Function (DELETE)
Tool to execute the pre-production version of a Cloud Backend API function via DELETE. Use when you need to test or validate delete operations in the preprod environment before production deployment.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Execute PROD API Function (GET)
Tool to execute a production Cloud Backend API function via GET. Includes robust URL handling and fallbacks to accommodate management base URLs.
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.
Execute Dev Function (PATCH)
Tool to execute the development version of a Cloud Backend API function via PATCH. Use after deploying or updating your function to the dev environment.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Execute Cloud Backend function via POST
Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.
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.
Execute Function POST (Preprod Env)
Tool to execute a Cloud Backend API function via POST on the preprod environment. Use when you need to test a function in the preprod environment before releasing to production. Include apiKey if your function requires APIKey security.
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.
Execute Cloud Backend function via PUT (default)
Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.
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.
Execute Cloud Backend function via PUT (preprod)
Tool to execute a Cloud Backend API function via PUT on the preprod environment. Use when you need to call a function with PUT parameters and optional APIKey in preprod.
Connect any two apps with Notis in the middle.
Notion and Appdrag, 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 Appdrag.