Connect Google Drive to Cloudinary

When something happens in Google Drive, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Google Drive to Cloudinary

View example

Find the Cloudinary folder for each new Drive brief

When a new brief appears in Google Drive, search Cloudinary folders for the matching campaign or project location.

View example

Check Cloudinary for assets referenced by an updated Drive file

When a Drive file changes, use its available identifying details to retrieve a corresponding Cloudinary asset by public ID.

View example

Review Cloudinary assets when a Drive file is shared

When a Drive file gains sharing permissions, list the assets directly in a related Cloudinary folder for a quick handoff review.

View example

Include Cloudinary top-level folders in a Drive file review

When a new Drive file matches your existing query trigger, retrieve Cloudinary root folders to help place it in the asset library.

View example

Check Cloudinary references when a Drive file is deleted

When a Drive file is trashed or deleted, retrieve a referenced Cloudinary asset so the report can support a human review of related content.

View example

Send a Cloudinary usage snapshot alongside Drive planning files

On a recurring schedule, retrieve Cloudinary usage and summarize it alongside a designated Drive planning file if one is available.

View example

Look up a Cloudinary folder from a Drive intake request

Start from an HTTP request containing Drive file details, then search Cloudinary folders for a likely destination.

View example

Review Cloudinary transformations against Drive campaign plans

On a schedule, retrieve Cloudinary transformations and compare the names with campaign or delivery needs described in a designated Drive planning file.

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Cloudinary. A trigger fires from one place; an action lands in another.

Google Drive triggers

Cloudinary actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Metadata Field

Tool to create a new metadata field definition. use when extending your metadata schema with new fields.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

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"

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

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.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Create Upload Preset

Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.

ActionInstant

File Shared (Permissions Added)

Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.

TriggerPolling

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]".

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

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'"

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Delete Folder

Tool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.