Give new product features a consistent visual
Document a feature once in Notion and get an on-brand image concept to support the announcement or help content.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Generate on brand
Reuse a saved brand kit so output stays consistent.
Why this helps
Feature documentation gets written, but a supporting visual is often postponed until another team remembers it.
- Adds a visual step to feature documentation without a separate reminder.
- Uses the saved brand kit for a consistent look.
- Creates a reusable starting point for announcements and help materials.
Setup
Build it in a few focused steps.
- 1Connect Notion and Image generation to Notis once in the portal.
- 2Start an automation from the portal or ask Notis conversationally.
- 3Describe the desired feature illustration in one plain-language prompt using new page context and the saved brand kit.
- 4Choose the Notion New Page trigger and select where run reports should go.
- 5Test with a real feature page and review the image.
Questions about this workflow
What kind of pages can start this?
Choose the database where feature pages are added and use the New Page event.
Why use Generate on brand?
It reuses a saved brand kit to guide the generated feature visual.
Can the image be used in multiple places?
The generated image can be reviewed for use in announcements, documentation, or other materials.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Image generation. A trigger fires from one place; an action lands in another.
Notion triggers
Image generation actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate an image
Create an image from a text description.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Edit an existing image
Send a reference image and describe the change.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate on brand
Reuse a saved brand kit so output stays consistent.
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 Image generation, 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 Image generation.