Keep asynchronous ImageKit work on your radar
A scheduled status check can help close the loop on a bulk move or copy job that runs in the background.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Bulk Job Status
Tool to check status of a bulk job. Use when monitoring progress of a bulk copy or move folder operation.
Why this helps
Asynchronous media operations can finish out of sight while the founder has moved on to other priorities.
- Reduces manual status-checking and context switching.
- Keeps background media operations visible until they finish.
- Supports more reliable follow-through on bulk organization work.
Setup
Build it in a few focused steps.
- 1Connect ImageKit io to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to check a known ImageKit bulk job on a schedule.
- 3In one instruction, identify how the relevant job is selected and what status summary to report.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with a real bulk job and confirm the reported status is useful.
Questions about this workflow
Can this check every bulk job?
The action checks a job status; the instruction needs a known job identifier or reliable way to select the job.
What operations use bulk jobs?
ImageKit returns job IDs for asynchronous bulk copy or move folder operations.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Imagekit io. A trigger fires from one place; an action lands in another.
Notion triggers
Imagekit io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Job Status
Tool to check status of a bulk job. Use when monitoring progress of a bulk copy or move folder operation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk Move Files
Tool to move multiple files in bulk. Use when you need to relocate up to 100 ImageKit files to a specified folder in one API call.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Bulk Remove Tags
Tool to remove tags from multiple files in bulk. Use when you need to strip specified tags from up to 50 existing files in one API call.
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.
Copy Folder
Tool to initiate a bulk copy of a folder. Use when you need to asynchronously duplicate a directory (optionally including all versions) at another path in ImageKit. Returns a jobId to track progress with IMAGEKIT_IO_BULK_JOB_STATUS.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Custom Metadata Field
Tool to create a custom metadata field. Use when you need to define a new field in ImageKit DAM.
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.
Create Folder
Tool to create a new folder. Use when you need to organize assets into a structured folder hierarchy.
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.
Delete Custom Metadata Field
Tool to delete a custom metadata field. Use when you have the field ID and need to permanently remove the metadata schema field. Call after confirming irreversible deletion.
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.
Delete File
Tool to delete a file. Use when you have the file ID and need to permanently remove the file. Call after confirming irreversible deletion.
Connect any two apps with Notis in the middle.
Notion and Imagekit 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 Imagekit io.