Refresh site visuals after inventory changes
A schema update can prompt a batch capture of the website pages in your Notion inventory.
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
Batch Capture Screenshots
Tool to capture screenshots for multiple urls in a single request. use when you have a list of pages to snapshot in batch.
Why this helps
A structural change to a page inventory can leave teams uncertain whether the visual reference set still covers the pages they track.
- Refresh several tracked pages in one capture request.
- Pair structural inventory changes with a visual check.
- Avoid opening every listed website individually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apiflash to Notis once in the portal.
- 2Create an automation in the portal or ask Notis for the outcome conversationally.
- 3Ask Notis to batch-capture the website URLs listed in the site inventory when its data source schema changes.
- 4Select the Notion Data Source Schema Updated trigger, scope it to the inventory if useful, and choose a report channel.
- 5Make a real schema update and verify the batch capture result.
Questions about this workflow
Why use a schema trigger here?
It signals a structural change to the inventory, which can be a useful time to refresh its visual reference set.
What URLs should be listed?
The data source should make the website URLs available in its page context for Notis to use in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apiflash. A trigger fires from one place; an action lands in another.
Notion triggers
Apiflash actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Capture Screenshots
Tool to capture screenshots for multiple urls in a single request. use when you have a list of pages to snapshot in batch.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Capture Website Screenshot (POST)
Tool to capture a screenshot of a website via http post. use when you need to post form data parameters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Quota Information
Tool to retrieve current api quota usage and limits. use after authentication to monitor usage and reset times.
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 Screenshot Metadata
Tool to retrieve metadata for a previously captured screenshot. use when you need details like file size and dimensions after capture.
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 Apiflash, 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 Apiflash.