Check image capacity as a new database begins
Start a Notion database for media work and get a Kraken.io capacity check without adding another reminder.
Trigger
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.
Action
Check Kraken.io User Status
Tool to retrieve current kraken.io account status and quota usage. use when you need to verify plan limits and remaining quota before processing images.
Why this helps
New structures for handling media can lead to processing plans that exceed current quota.
- Make quota visible as a media database is introduced.
- Reduce setup-time follow-up work.
- Receive account status in your selected report channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kraken.io to Notis once.
- 2Create an automation through the portal or ask Notis conversationally.
- 3In one instruction, ask Notis to check Kraken.io plan limits and remaining quota when a media-related database is created.
- 4Select Notion's Database Created trigger and choose a channel for reports.
- 5Test with a real database creation or a safe test scenario.
Questions about this workflow
Does this include new data sources added to an existing database?
No. Database Created is for the container creation event; a new data source has its own trigger.
Can this action resize images?
No. It checks Kraken.io account status and quota only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kraken io. A trigger fires from one place; an action lands in another.
Notion triggers
Kraken io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Kraken.io User Status
Tool to retrieve current kraken.io account status and quota usage. use when you need to verify plan limits and remaining quota before processing images.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Optimize Image by URL
Tool to optimize an image from a public url. use when you need to compress, resize, or convert an externally hosted image. returns result immediately if 'wait' is true.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Preserve Image Metadata
Tool to preserve exif and other metadata during kraken.io image optimization. use when you need to maintain metadata while compressing images.
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.
Sandbox Image Upload
Tool to upload and optimize images in sandbox mode. use when you want to test the kraken.io api without consuming 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 Kraken io, 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 Kraken io.