Explore product visuals as details change
When product details evolve, make it easier to see a fresh visual interpretation without rebuilding the request by hand.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Generate Image from Image
Tool to generate a new image from an initial image and text prompts. use after you have a reference image and want to transform it via text guidance.
Why this helps
Small product changes can make old imagery feel stale, yet updating visuals often falls behind other priorities.
- Connect evolving product notes to visual exploration.
- Make iteration easier when a feature or positioning changes.
- Keep the reference and new direction in the same working context.
Setup
Build it in a few focused steps.
- 1Connect Notion and DreamStudio to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to explore a product image when its Notion page content changes.
- 3Write one plain-language prompt explaining how to use the changed product notes and current reference image.
- 4Choose the Notion Page Updated trigger and a channel for run reports.
- 5Test by making one real product page content change.
Questions about this workflow
Does this work for a whole product database?
The page trigger applies to a specified page. Use the prompt and trigger scope to keep the workflow focused.
Will the original image be overwritten?
The action generates a new image from an initial image and guidance, giving you a variation to review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dreamstudio. A trigger fires from one place; an action lands in another.
Notion triggers
Dreamstudio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Image from Image
Tool to generate a new image from an initial image and text prompts. use after you have a reference image and want to transform it via text guidance.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Engines
Tool to retrieve a list of all engines available to your organization or user. use when you need to discover which dreamstudio engines you can invoke.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
User Account
Tool to retrieve user account details, including id, email, credits, and profile. use after authenticating with the stability api to check account status.
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.
DreamStudio User Balance
Tool to retrieve the user's balance information, including available credits and usage. use after authenticating to verify current credits.
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 Dreamstudio, 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 Dreamstudio.