Revisit your brand visuals with fresh context
A monthly visual review can help you notice when your creative direction no longer reflects the brand guidance you maintain in Notion.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Generate Image (Precise)
Text-to-image with gpt-image-2.5-sunburst.
Why this helps
Brand decisions can evolve quietly, leaving old visual assumptions in place across new work.
- Create a regular moment to review visual direction.
- Consider the current brand guidance in Notion.
- Explore a new image concept without needing a fresh manual brief.
Setup
Build it in a few focused steps.
- 1Connect Notion and OpenAI to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to generate a precise brand visual concept each month using current guidance.
- 3Describe the image direction and relevant Notion context in one plain-language instruction.
- 4Choose a monthly schedule and select where run reports should be sent.
- 5Test with current brand guidance and assess whether the concept fits.
Questions about this workflow
Will the monthly schedule automatically update the brand page?
No. The OpenAI action generates an image; Notis can report the result through your chosen channel.
What is a good use for the monthly image?
Use it as a review prompt for campaigns or as a concept to refine with your team.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to OpenAI. A trigger fires from one place; an action lands in another.
Notion triggers
OpenAI actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Image
Text-to-image with gpt-image-2.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Image (Precise)
Text-to-image with gpt-image-2.5-sunburst.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Edit Image
Reference-image editing with gpt-image-2.
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.
Edit Image (Precise)
Reference-image editing with gpt-image-2.5-sunburst.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Generate Image (Fast)
Text-to-image with gpt-image-2.5-flare.
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.
Edit Image (Fast)
Reference-image editing with gpt-image-2.5-flare.
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 OpenAI, 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 OpenAI.