Turn connection confirmation into a key check
Once someone confirms setup in a comment, verify the current key automatically.
Trigger
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.
Action
Check API Key
Tool to check validity of current api key. use after obtaining your api key to validate its authenticity.
Why this helps
A setup confirmation can be mistaken for a working integration without a validity check.
- Follows up on a human setup confirmation automatically.
- Separates reported setup completion from verified key validity.
- Sends the result where run reports are delivered.
Setup
Build it in a few focused steps.
- 1Connect Notion and All images ai to Notis once in the portal and configure the API key securely in All images ai.
- 2Create an automation in the portal or ask Notis to check the current key when a setup comment confirms the connection is configured.
- 3Choose the Notion Comment Created trigger and select a channel for run reports.
- 4Test by adding a real setup confirmation comment and reviewing the check result.
Questions about this workflow
Should someone paste the key in the comment?
No. The key should remain in the connected All images ai service configuration.
What capability is needed for comment triggers?
The Notion integration needs Read comments enabled and may need to be reauthorized after that capability is added.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to All images ai. A trigger fires from one place; an action lands in another.
Notion triggers
All images ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check API Key
Tool to check validity of current api key. use after obtaining your api key to validate its authenticity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create webhook endpoint
Tool to add a webhook endpoint to an api key. use when you want to receive print event callbacks at a custom endpoint.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Automated Images
Tool to list all images generated automatically for bulk use. use after creating automated-image batches to review and manage them.
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.
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 All images ai, 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 All images ai.