Keep research screening aligned with schema changes
When your research database structure evolves, use the schema change as a cue to revisit and run a clearly defined Finviz screening routine.
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
Run screener
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
Why this helps
Changes to a research database can leave supporting routines out of step unless someone remembers to review them.
- Notice when a research structure change affects screening routines.
- Reduce the chance that process maintenance is forgotten.
- Use the new database context to guide an appropriate screen.
Setup
Build it in a few focused steps.
- 1Connect Notion and Finviz to Notis once in the portal.
- 2Create an automation with a plain-language instruction to review the research schema change and run a screen only when its purpose is clear.
- 3Select Notion Data Source Schema Updated for the research source and choose a channel for run reports.
- 4Test with a real schema change and review whether the resulting screen fits the updated process.
Questions about this workflow
Will every schema update cause a screen?
The prompt should ask Notis to interpret the change and screen only when the updated research workflow clearly calls for it.
What information is included in the schema event?
The event includes updated property details, allowing the automation to consider what changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Finviz. A trigger fires from one place; an action lands in another.
Notion triggers
Finviz actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Run screener
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get insider trading
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
get_ticker_sectors_with_performance
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
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.
Get news sentiment
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get market movers
Monitor insider trading activity, screen stocks based on custom criteria, and analyze market sentiment from financial news to make informed investment decisions. Access real-time data on market movers, tabular financial information, and comprehensive market intelligence all in one place.
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 Finviz, 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 Finviz.