Connect Notion to Imagekit io
When something happens in Notion, Notis takes the next step in Imagekit io. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Imagekit io
View exampleCreate a folder for every new campaign
When a campaign is added to a Notion database, create its matching folder in ImageKit so the asset home is ready before creative work begins.
View examplePrepare an asset folder for each project page
A new Notion project page prompts ImageKit to create a matching folder, giving founders one predictable place for project visuals.
View examplePurge ImageKit cache after a published-page update
When a selected Notion page's content changes, prompt an ImageKit cache purge for the related live image URL so updated creative can show promptly.
View exampleKeep ImageKit asset details aligned with record updates
A change to a Notion asset record's properties can update the corresponding ImageKit file details, reducing repeated maintenance across tools.
View exampleFetch ImageKit details when a reviewer comments
A new Notion comment can trigger a lookup of the related ImageKit file details, bringing file context into review follow-up.
View exampleRename an asset when its Notion page changes
When a tracked Notion page is updated, rename its associated ImageKit file according to the naming convention in the instruction.
View exampleCreate asset folders for new content briefs
When a content brief is added beneath a Notion planning page, create an ImageKit folder for its visuals so a new brief has an obvious asset home.
View exampleAdd an ImageKit metadata field when the asset schema grows
A new property in a Notion asset data source can cue creation of a matching custom metadata field in ImageKit.
View exampleCreate a metadata field when a new gallery signals a media workflow
A newly created Notion gallery view can cue an ImageKit metadata field that supports the media classification behind that gallery.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Imagekit io
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.