Give page discussions a current visual reference
A new comment on a key Notion page can prompt a rendered snapshot of the related webpage.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Take Webpage Snapshot
Tool to capture rendered HTML and screenshot of a webpage. Use when you need both DOM content and an image in one request with custom loading and capture settings.
Why this helps
A busy discussion can grow without a shared view of the current page state.
- Anchor a page discussion to a current rendered view.
- Make follow-up easier when several workstreams are active.
- Keep a visual reference close to the conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cloudflare browser rendering once in the Notis portal.
- 2Create the automation in the portal or ask Notis to snapshot a webpage after a comment on its Notion page.
- 3Write one plain-language instruction that tells Notis to use the page URL and capture rendered HTML with a screenshot.
- 4Choose the Notion New Comment trigger for the relevant page and a channel for run reports.
- 5Test with one real comment on the selected page.
Questions about this workflow
How is this different from a workspace-wide comment trigger?
New Comment can be scoped to a specified Notion block or page, keeping the automation focused on a particular discussion.
What will the snapshot help me review?
It captures rendered HTML and a screenshot of the webpage associated with the Notion page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudflare browser rendering. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudflare browser rendering actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Capture Screenshot
Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Accounts
Tool to list all Cloudflare accounts accessible. Use to retrieve a valid account_id for further browser rendering actions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Scrape HTML Elements
Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.
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.
Take Webpage Snapshot
Tool to capture rendered HTML and screenshot of a webpage. Use when you need both DOM content and an image in one request with custom loading and capture settings.
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 Cloudflare browser rendering, 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 Cloudflare browser rendering.