Respond quickly to a campaign image request
A campaign system can send a webhook when a visual needs attention, letting Notis use Notion context to request a fast edit.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Image (Fast)
Reference-image editing with gpt-image-2.5-flare.
Why this helps
Campaign assets can become a last-minute bottleneck when a small change requires a fresh manual handoff.
- Make a focused revision easier to start when a request arrives.
- Use existing campaign context to guide the edit.
- Keep visual iteration moving during a busy launch window.
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 make a fast campaign image edit when your campaign tool sends a webhook.
- 3Write one plain-language instruction describing the image, the campaign context, and the requested change.
- 4Select the incoming webhook trigger and connect the external request to Notis.
- 5Choose a report channel and test with one real campaign edit request.
Questions about this workflow
What can send the webhook?
An external tool or custom backend can send an HTTP request to start the workflow.
Can this action create a new image instead?
This workflow uses the fast image edit action, which is intended to revise a reference image.
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.