Keep your media metadata definitions aligned
When an asset data source changes, connect that structural update to the Cloudinary metadata definition it affects.
Trigger
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.
Action
Update Metadata Field
Tool to update a metadata field definition by external id. use when modifying an existing schema field (e.g., changing label or validation) without redefining all properties.
Why this helps
Schema changes are easy to make in a planning database and easy to forget in the media catalog.
- Keep documented asset fields aligned across tools.
- Reduce forgotten metadata maintenance.
- Make schema changes easier to trace.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cloudinary to Notis once in the portal.
- 2Create an automation that asks Notis to update the corresponding Cloudinary metadata field when a relevant Notion property is renamed or changed.
- 3Choose the Notion Data Source Schema Updated trigger for the asset data source.
- 4Select a channel for run reports and test with a planned schema change and its matching Cloudinary field.
Questions about this workflow
Does every schema change have to update Cloudinary?
No. Describe which kinds of property changes should lead to a metadata field update.
Can the automation know which property changed?
The trigger includes updated property details. State the correspondence in plain language and review the proposed field change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudinary. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudinary actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Folder
Tool to create a new asset folder. use when you need to organize assets into nested directories. use after confirming the folder path does not already exist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Metadata Field
Tool to create a new metadata field definition. use when extending your metadata schema with new fields.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Trigger
Tool to create a new webhook trigger for a specified event type. use after configuring your webhook endpoint and choosing the event type. example: "create a trigger for uploads to https://example.com/hooks/cloudinary"
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.
Create Upload Mapping
Tool to create a new upload mapping folder and url template. use when you need to dynamically map external url prefixes to a cloudinary asset folder before uploading files.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Upload Preset
Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.
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.
Delete Derived Resources
Tool to delete derived assets. use when you need to remove specific derived assets by their ids. example: "delete derived assets with ids [id1, id2]".
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 Metadata Field Datasource Entries
Tool to delete datasource entries for a specified metadata field. use when you need to soft-delete (inactivate) specific entries in a field's datasource. example prompt: "delete entries ['color1','color2'] from metadata field 'color id'"
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 Folder
Tool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.
Connect any two apps with Notis in the middle.
Notion and Cloudinary, 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 Cloudinary.