Description

Cloudinary node

Use the Cloudinary node to automate work in Cloudinary, and integrate Cloudinary with other applications. n8n has built-in support for a wide range of Cloudinary features, including uploading assets, managing tags, and updating metadata.

On this page, you’ll find a list of operations the Cloudinary node supports.

Operations

• Asset

* Upload from URL/file
* Update asset tags
* Update asset metadata fields
* Get tags
* Get structured metadata definitions
* Search assets

• Transform (builds a delivery URL — no API call)

* Image: Optimize, Resize, Crop, Convert
* Video: Optimize, Resize, Crop, Trim, Thumbnail
* Custom Transformation (raw transformation string)
* Compose: Combine Transformations (multi-step, in one node)

• Widget

* Video Player (builds an embed URL + player config)

Search assets

Uses the ).

The node emits one n8n item per matching asset, so downstream nodes can map over results directly without a Split Out step.

• Resource Types — Cloudinary’s Search API defaults to image-only when no resourcetype: clause is in the expression. This node injects the clause automatically based on the Resource Types you select (defaults to image). To search across all types, select all three. If your expression already contains a resourcetype: clause, the selection is ignored.
• Return All — when enabled, the node automatically paginates through Cloudinary’s next_cursor until all matching assets have been returned. When disabled, only the first page (up to Max Results, capped at 500) is returned.
• Rate limits — the node surfaces 429/420 responses with a clear “rate limit exceeded” error including the server’s Retry-After.
• Eventual consistency — newly uploaded assets may take a few seconds to appear in search results. Avoid searching for something you just uploaded in the same workflow without a delay.

Transformations and chaining

A transformation is the instruction string Cloudinary applies when delivering an asset — for example cfill,w400 (crop to 400px wide) or fauto/qauto (auto format and quality). Each Transform operation builds one and returns it on the output as transformation, alongside the finished secure_url.

Real edits usually need several transformations applied in sequence (“first crop, then optimize”). In Cloudinary’s URL these are components joined with /, applied left to right — each acts on the output of the one before it. For example cfill,w400/fauto/qauto means crop, then auto-format, then auto-quality. There are three ways to build a chain with this node, from simplest to most flexible:

1. One operation. A single Transform op (e.g. Image: Resize) when one step is all you need.

2. Combine Transformations (one node). The Compose → Combine Transformations operation takes an ordered, reorderable list of steps and chains them inside a single node. Best when the whole recipe is known up front and lives in one place.

3. Continue From Transformation (across nodes). Every chainable Transform op has an optional Continue From Transformation field. This is the bridge that makes chaining work across separate nodes, and it relies on one property mapping:

> The upstream op’s transformation output → the downstream op’s Continue From Transformation input.

Wire it with an expression: set Continue From Transformation to {{ $json.transformation }}. The node prepends that incoming string before the current op’s own transformation, so the two compound into one delivery URL. Example — a Resize node outputs transformation: "cfill,w400"; feed it into an Optimize node’s Continue From Transformation, and the Optimize node delivers cfill,w400/fauto/qauto.

This field is available on all single-purpose Transform ops. It is intentionally not offered on Custom Transformation (you already control the entire string there) or Combine Transformations (which chains its own steps internally).

Tip: Resize and Crop don’t auto-optimize. To also get fauto/qauto, either add an Optimize step in Combine Transformations, or chain an Optimize node after them via Continue From Transformation.

Video Player (Widget)

The Widget → Video Player operation builds a effectsandenhancements”>video effects.

• Adaptive streaming vs. format selection. If you select an adaptive-streaming Source Type (HLS or MPEG-DASH), the transformation must not pin a delivery format (an f component such as fauto:video, which an Optimize step adds). The two are incompatible — Cloudinary can’t apply a streaming profile to a fixed non-streaming format. The node detects this and fails with a clear message; for adaptive streaming, keep the transformation to resize/crop/trim only.
• Aspect Ratio crops on top of your Transformation. Setting an Aspect Ratio makes the player re-crop the video to those proportions using the Crop Mode field (Smart, Fill, or Pad — default Smart). With the default Smart mode, that re-crop can’t be combined with a Transformation that already crops the video, and the player rejects it. The node fails fast with a clear message; to render either set Crop Mode to Fill or Pad, or clear Aspect Ratio and let your Transformation define the framing.

#### AI-generated content (captions, title, description, chapters)

The AI-Generated Content options let the player generate content on demand — no caption files to author. Toggle Generate Captions (auto-transcript shown as toggleable captions), Generate Title, Generate Description, and/or Generate Chapters. The player only generates what doesn’t already exist, and transcript generation needs the video’s audio to contain dialogue. These options are emitted into the playerconfig (the JS player.source() config), not the iframe embed URL. On most accounts these are enabled by default under Settings → Security → Unsigned actions allowed — so there’s nothing to switch on. See the Cloudinary Add-ons page (Console → Settings → Add-ons) — the free tier is enough to try it.
> 2. Allow it as an unsigned transformation: Console → Settings → Security → Unsigned add-on transformations allowed → enable Google Translate.
>
> Base captions (the Generate Captions toggle, single language) need no add-on — only translation into other languages does.

Supported authentication methods

• API key & API secret

Authentication

Using API key

To configure this credential, you’ll need a Cloudinary account and:

• A Cloud name
• An API Key
• An API Secret

#### Get your credentials from the Console

1. Create a free Cloudinary account — you can sign up with Google, GitHub, or an email address. Skip to step 2 if you already have one.
2. In the Cloudinary Console, go to Settings > API Keys. Viewing keys requires the Master admin, Admin, or Technical admin role.
3. Copy the API Key and API Secret. A new account already ships with an active key — use Generate New Access Key only if you’d rather issue a dedicated key for n8n.
4. Copy the Cloud name from the top of the page (it’s also on the Console Dashboard).
5. Enter the cloud name, API key, and API secret into your n8n credential.

Treat the API secret like a password: it authenticates every signed Upload and Admin API call this node makes, and should never leave your organization.

#### Or ask an agent to provision a cloud for you

If you’re setting this up alongside a coding agent — or you just want working credentials in under a minute without signing up first — ask an agent to run this, and it will provision a sign up the normal way) and use those credentials.

#### Private CDN / custom delivery hostname (advanced)

Most users can skip this. If your organization is on a Advanced plan that uses a mediaguides”>Cloudinary’s documentation for more information on this service.