Keep processing capacity visible as asset views grow
Create a new way to review assets in Notion and get a timely Kraken.io quota check.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
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
As asset processes grow, quota checks can be skipped amid the work of organizing them.
- Connect organization changes with a useful capacity check.
- Reduce the need to remember a separate status review.
- Get a concise account status report.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kraken.io to Notis once in the portal.
- 2Create the automation in the portal, or ask Notis for it conversationally.
- 3Ask Notis in one instruction to check Kraken.io status and remaining quota when a new asset-related view is created.
- 4Select Notion's View Created trigger and choose a channel for reports.
- 5Test with a real asset view or a safe test scenario.
Questions about this workflow
Does every new view necessarily indicate more image usage?
Not always. Use a plain-language instruction to check status only when the new view is relevant to asset processing.
Does the status action change my Kraken.io plan?
No. It retrieves current account status and quota usage.
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.