Connect Notion to Cloudinary
When something happens in Notion, Notis takes the next step in Cloudinary. 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 Cloudinary
View exampleCreate a Cloudinary folder for each new Notion project
When a project is added to Notion, create a matching Cloudinary folder to keep its media together from the start.
View examplePrepare Cloudinary upload mappings from new Notion intake pages
Use a new Notion intake page to create an upload mapping that routes incoming media into the right Cloudinary location.
View exampleCreate Cloudinary upload presets when media guidelines change
A change to a Notion media guideline can prompt a Cloudinary upload preset for the updated standards.
View exampleCreate Cloudinary metadata fields from evolving Notion standards
When a Notion media standards page changes, create a Cloudinary metadata field for newly documented asset details.
View exampleFind the Cloudinary folder behind a Notion asset comment
When a Notion comment flags an asset location, search Cloudinary folders so the follow-up can begin with relevant results.
View exampleRetrieve Cloudinary asset details from a Notion review comment
A review comment that names an asset can prompt Notis to retrieve its Cloudinary details for a more informed follow-up.
View exampleInventory Cloudinary assets for new campaign subpages
When a campaign subpage is added in Notion, retrieve assets in its matching Cloudinary folder to make the media inventory visible.
View exampleRename Cloudinary folders when Notion asset records change
A property update to an asset record can prompt a Cloudinary folder rename or move to reflect the revised organization.
View exampleAdd Cloudinary metadata for newly documented brand assets
When a brand asset is added to Notion, create a Cloudinary metadata field if the record introduces a new tracking attribute.
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.
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 Cloudinary
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.