Turn image tasks across Notion pages into processing runs
Keep visual follow-up from disappearing across your workspace by letting Notis identify image tasks as pages change.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Process Image Async
Tool to schedule an image enhancement job and wait for the result. Performs selected enhancement options on an image and returns the result URL if processing completes within 25 seconds; otherwise returns a job hash for later retrieval. Use when you need to enhance images with options like denoising, deblurring, lighting improvements, or background removal.
Why this helps
Image requests can live across many pages, making it difficult to remember which ones still need action.
- Cover image tasks wherever they are recorded in accessible Notion pages.
- Reduce manual workspace scanning.
- Use one plain-language instruction to define which requests merit processing.
Setup
Build it in a few focused steps.
- 1Connect Notion and DeepImage to Notis once through the portal.
- 2Create an automation in the portal or tell Notis what image tasks to handle.
- 3Write one instruction asking Notis to identify explicit image-enhancement requests on pages and process their linked images.
- 4Select the Notion All Page Events trigger and a channel for reports.
- 5Test with one real page that contains a clear image task.
Questions about this workflow
Does every page update start a run?
All Page Events fires for page creation or updates across the workspace. The prompt should direct Notis to act only on relevant image tasks.
When is this broad trigger useful?
It can suit teams that record image requests in many places and prefer one workspace-wide automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to DeepImage. A trigger fires from one place; an action lands in another.
Notion triggers
DeepImage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Job
Tool to delete completed job result and remove images from the server. Use when cleaning up processed jobs that are no longer needed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Information
Tool to retrieve authenticated user's profile information including credits, username, email, API key, language preference, webhook settings, and billing address. Use when you need to check account details or credit balance.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Job Result
Tool to retrieve processing job result by hash. Use to check job status and get result URL when processing is complete.
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.
Process Image Async
Tool to schedule an image enhancement job and wait for the result. Performs selected enhancement options on an image and returns the result URL if processing completes within 25 seconds; otherwise returns a job hash for later retrieval. Use when you need to enhance images with options like denoising, deblurring, lighting improvements, or background removal.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Process Image Synchronously
Tool to process an image synchronously with Deep Image AI. Returns result URL immediately if processing completes in less than 25 seconds, otherwise returns job hash for async polling. Use for image enhancement, resizing, background removal, and other image processing tasks.
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 DeepImage, 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 DeepImage.