Keep event visuals aligned with updated details
If the event story changes, make a new visual exploration from the updated details and current reference image.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
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
Event details can shift quickly, leaving creative assets mismatched unless someone remembers to refresh them.
- Tie visual exploration to current event details.
- Reduce manual follow-up after schedule or message changes.
- Keep the event page as the home for creative 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 refresh event visuals when the selected event page content changes.
- 3Describe in one plain-language prompt how to use current event details and the page's reference image.
- 4Choose the Notion Page Content Updated trigger and a channel for run reports.
- 5Test with one meaningful update to a real event page.
Questions about this workflow
Will every content edit create a variation?
The trigger reports content edits. Use the prompt to specify which event updates merit a new visual exploration.
What event changes are useful?
Try a changed theme, audience, or key message that should affect the image direction.
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.