Keep priority changes visible
When a task's properties change, make the new priority easier to see.
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
Convert HTML to Image
Tool to convert HTML content into an image. Returns either a downloadable file or a JSON payload containing id and url, depending on the upstream API behavior.
Why this helps
Priority updates are easy to miss when they happen among many database edits and notifications.
- Make changed task details easier to notice.
- Help collaborators spot priority shifts quickly.
- Keep important updates visible without checking every row.
Setup
Build it in a few focused steps.
- 1Connect Notion and Html to image to Notis once.
- 2Create an automation in the portal and write one instruction for turning a changed task into an image.
- 3Select Notion's Page Properties Updated trigger and choose the relevant data source.
- 4Choose a run-report channel and test with one real priority update.
Questions about this workflow
Does every property edit start it?
The trigger fires on page property updates. Describe in the prompt how Notis should handle the changed task details.
What can the image show?
Ask for the changed priority alongside helpful task context, such as its title, status, or next step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Html to image. A trigger fires from one place; an action lands in another.
Notion triggers
Html to image actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get HTML to Image
Tool to retrieve a generated image by its ID. Use when you need to fetch, resize, or download an existing HTML to image asset.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check HTML-to-Image Account Usage
Tool to retrieve account usage statistics including hourly, daily, and monthly image creation counts. Use after authenticating to review current usage limits and billing periods.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Convert HTML to Image
Tool to convert HTML content into an image. Returns either a downloadable file or a JSON payload containing id and url, depending on the upstream API behavior.
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.
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 Html to image, 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 Html to image.