Keep campaign image files lighter
Update a campaign record in Notion and let Kraken.io optimize its linked image for a smoother handoff.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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.
Why this helps
Campaign owners often lose time reopening assets to compress them after the record is already updated.
- Reduce a repeated asset-prep task after campaign updates.
- Make optimization part of the record-change routine.
- See a report from each run.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kraken.io to Notis once.
- 2In the portal, create an automation, or ask Notis conversationally to create one.
- 3In one instruction, ask Notis to optimize the public image URL associated with a changed campaign record.
- 4Select Notion's Page Properties Updated trigger and choose where to receive run reports.
- 5Try it on a real campaign record with an image URL.
Questions about this workflow
Does every property edit optimize an image?
The trigger detects property updates. The plain-language instruction should tell Notis to proceed only when the page contains a relevant campaign image URL.
Can Kraken.io optimize an image already in our workspace?
This action uses a public URL, so the image must be externally hosted and accessible.
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.