Give every new campaign its own ImageKit folder
A campaign starts in Notion; its asset space is ready in ImageKit without a separate setup task.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Folder
Tool to create a new folder. Use when you need to organize assets into a structured folder hierarchy.
Why this helps
Starting a campaign means remembering a second organizational chore before the team can even store its first asset.
- Removes the manual folder setup step from each campaign kickoff.
- Keeps campaign assets grouped around the work record that created them.
- Makes it easier to hand off creative work without asking where files belong.
Setup
Build it in a few focused steps.
- 1Connect Notion and ImageKit io to Notis once through the portal.
- 2Create a new automation in the portal, or ask Notis conversationally to create it.
- 3In one plain-language instruction, ask Notis to create an ImageKit folder for each new campaign page using its campaign name.
- 4Pick the Notion New Page trigger for the campaigns data source and choose a channel for run reports.
- 5Test by adding one sample campaign and confirm its folder appears in ImageKit.
Questions about this workflow
Does this create a folder for any new Notion page?
Choose the New Page trigger for the campaigns data source so the automation runs for campaign records there.
Can I use this for launches as well as campaigns?
Yes. Describe the kind of Notion records and the folder naming convention in the instruction.
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.