There\u2019s a one-time setup gotcha worth knowing up front. After you import a workflow and pick your Cloudinary credential on the first node, press Cmd\/Ctrl+S<\/strong> to save before running. That single save persists the credential to every Cloudinary node in the flow at once, so a full Execute Workflow<\/strong> run finds credentials everywhere. Skip the save and the run can fail node-after-node with \u201cNode does not have any credentials set,\u201d even though the credential looks selected. (More in the section \u201cAdd your Cloudinary credentials\u201d.)<\/p>\n<\/div>\n\n\n To recap, you’ll build:<\/p>\n\n\n\n The release adds three things that matter for automation:<\/p>\n\n\n\n Now let’s put them to work.<\/p>\n\n\n\n The problem: <\/strong>Marketing ships one master video. It needs a 9:16 for TikTok\/Reels, a 1:1 for the feed, and a 16:9 for YouTube \u2014 each trimmed, each with a poster frame, each optimized. Today that’s a manual export-fest.<\/p>\n\n\n\n The workflow: <\/strong>01-social-video-variations.json<\/a><\/p>\n\n\n\n Upload the master once, then three Compose: Combine Transformations<\/strong> nodes each build a single delivery URL that trims > crops to the platform’s aspect ratio (with auto-focus to keep the subject in frame) > auto-optimizes<\/strong>. A matching Video: Thumbnail<\/strong> generates each poster. A final Code node collects everything into a tidy list of { The win:<\/strong> One trigger produces every platform’s asset, ready to hand to a social scheduler or CMS. Add a platform by copying a node and changing one aspect ratio.<\/p>\n\n\n\n The problem:<\/strong> Product photography arrives in every shape and on every background. Your storefront wants identical, square, optimized product images for thousands of SKUs.<\/p>\n\n\n\n The workflow:<\/strong> 02-ecommerce-image-pipeline.json<\/a><\/p>\n\n\n\n For each product, the flow ingests the photo, then runs Image: Crop with Generative Fill \u2014 instead of cropping the product, Cloudinary extends the canvas to a perfect 1200\u00d71200 square and paints a matching background with AI (guided by a prompt like “clean seamless studio background”). It then chains a Convert \u2192 WebP step onto that same transformation. Out comes one catalog-ready URL per product.<\/p>\n\n\n The win:<\/strong> Consistent, optimized product imagery with zero designer time \u2014 and it scales to your whole catalog by swapping the input list for a Cloudinary Search or a PIM lookup.<\/p>\n\n\n\n Generative Fill is a generative-AI effect: it uses a special transformation count, is subject to your plan limits, and may render asynchronously on the first request. Create a free account to try it.<\/p>\n\n\n\n The problem:<\/strong> You’re still hand-exporting @1x\/@2x assets, and shipping desktop-sized images to phones.<\/p>\n\n\n\n The workflow:<\/strong> 03-responsive-srcset.json<\/a><\/p>\n\n\n\n Point it at one source image and a list of widths. It builds an Image: Resize URL per width (using Limit fit so it never upscales), chains Optimize ( The win:<\/strong> Crisp Retina displays and lightweight mobile loads from a single asset \u2014 with the markup generated for you. Change a breakpoint by editing one array.<\/p>\n\n\n\n The problem:<\/strong> Putting a real video player on a landing page or CMS usually means a JS build step and a streaming setup.<\/p>\n\n\n\n The workflow:<\/strong> 04-embeddable-video-player.json<\/a><\/p>\n\n\n\n The flow trims a preview cut, grabs a matching poster frame (chained onto the trim), and generates a Video Player<\/strong> embed with HLS adaptive streaming<\/strong> and an MP4 progressive fallback<\/strong>, picture-in-picture, The win:<\/strong> a production-grade, adaptive player as a paste-in snippet \u2014 no front-end code.<\/p>\n\n\n\n The workflow feeds the player the trim<\/em> transformation, not an optimize<\/em> one \u2014 adaptive streaming (HLS\/DASH) can’t be combined with a format-pinned transform ( The problem:<\/strong> at scale, media libraries rot. Untagged assets, oversized files, content nobody owns. Cleaning it up by hand doesn’t happen.<\/p>\n\n\n\n The workflow:<\/strong> 05-asset-governance-audit.json<\/a><\/p>\n\n\n\n Asset \u2192 Search Assets<\/strong> with Return All<\/em> paginates through all matching assets (it handles pagination and surfaces rate-limit errors clearly), emitting one n8n item per asset with its tags. The template is scoped to The win:<\/strong> continuous, policy-driven hygiene that works identically on 50 assets or 50,000. Swap the tag action for structured-metadata updates or (carefully) deletes.<\/p>\n\n\n\n The problem:<\/strong> Captions are often required by accessibility standards and regulations (such as WCAG, the ADA, and the European Accessibility Act), and a global audience needs subtitles in several languages. Authoring caption files for every video, by hand, doesn’t scale.<\/p>\n\n\n\n The workflow:<\/strong> 06-accessible-video-player.json<\/a><\/p>\n\n\n\n This is the workflow that shows what Cloudinary’s video features can do. The Video Player<\/strong> node ships an accessibility-first config \u2014 keyboard controls on, no autoplay-with-sound<\/strong>, playsinline, chapters button visible \u2014 plus an AI-Generated Content<\/strong> section that’s just a set of toggles:<\/p>\n\n\n\n These are enabled by default<\/strong> on most accounts, so there’s nothing to switch on. The player only generates content that doesn’t already exist, returning a 202 while it works and caching the result. Nobody writes a caption file: no code is needed to generate captions \u2014 the workflow’s Code node only formats the player embed snippet.<\/p>\n\n\n\n Need subtitles in other languages? Set Subtitle Languages<\/strong> (e.g., The win:<\/strong> videos with dialogue can get captions, chapters, and optional translated tracks automatically \u2014 as part of the same flow that published them, with no caption files to author.<\/p>\n\n\n\n Auto-generation lives in the player’s JS config (not iframe URL params), so this workflow outputs a Every workflow is a single Follow these instructions<\/a> to install the Cloudinary community node ( Open the workflows list, click the\u00a0three-dot\u00a0menu (top-right) >\u00a0Import from File\u2026<\/strong> > Select one of the\u00a0 The workflow opens with its sticky-note README already on the canvas explaining what every node does.<\/p>\n\n\n\n The templates contain no connection details<\/strong> \u2014 they’re yours to add.<\/p>\n\n\n\n First, create the credential once: in the Credentials<\/strong> sidebar > Add Credential<\/strong> > Cloudinary API<\/strong>, and paste your Cloud name<\/strong>, API Key<\/strong>, and API Secret<\/strong> from the Cloudinary Console \u2192 API Keys<\/a>. Save it. Now it’s offered in the dropdown on every Cloudinary node, in this template and every one you import later.<\/p>\n\n\n\n Then, on the imported workflow, open the first<\/strong> Cloudinary node and pick that credential from the Credential<\/strong> dropdown. n8n back-fills the other nodes that share it \u2014 you’ll see “Added this credential to N other node(s).”<\/em><\/p>\n\n\n\n Then save before you run \u2014 this is the important bit.<\/strong> Press Cmd\/Ctrl+S<\/strong> right after picking the credential. The save persists the binding to every Cloudinary node at once, so a full Execute Workflow<\/strong> run finds credentials everywhere.<\/p>\n\n\n\n If you don’t<\/em> save first, the full run can fail one node at a time with “Node does not have any credentials set”<\/strong> \u2014 even though the credential clearly looks selected on the node. (Tell-tale sign: running a node on its own with Execute step<\/strong> works, but Execute Workflow<\/strong> fails.) A save fixes it in one shot.<\/p>\n\n\n\n Click Test workflow<\/strong>. The first few workflows upload a public Cloudinary demo asset into your<\/em> account so everything downstream resolves against your cloud \u2014 so they run out of the box, then become yours the moment you point them at your own media.<\/p>\n\n\n\n These six are starting points, not end points. Because every Transform op emits a reusable Install the node, import a workflow, and let the media steps run themselves.<\/p>\n\n\n\n Which Cloudinary feature are you missing in the n8n integration?<\/strong> We’re actively expanding the node \u2014 tell us what you’d build next by opening an issue on GitHub<\/a> or reaching out through Cloudinary Support<\/a>.<\/p>\n\n\n\n Ready to level up your media workflow? Start using Cloudinary for free<\/a> and build better visual experiences today.<\/p>\n\n\n\nWhat You’ll Build<\/h2>\n\n\n\n
\n
srcset<\/code>.<\/li>\n\n\n\n\n
secure_url<\/code> and a reusable transformation string. Because they’re pure URL construction, they’re instant and free of round-trips.<\/li>\n\n\n\n\n
\n
The 6 Importable n8n Workflows<\/h2>\n\n\n\n
1. One Source Video: A Cut for Every Platform<\/h3>\n\n\n\n
platform<\/code>, video_url<\/code>, poster_url<\/code>}.<\/p>\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137781\/blog-Automate_Your_Media_at_Scale-_6_Cloudinary_Workflows_You_Can_Import_Into_n8n_Today-1.webp\")
<\/figure><\/div>\n\n\n2. Bulk Product Photos \u2192 Uniform, AI-Filled Catalog Images<\/h3>\n\n\n\n
![\"An](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137782\/blog-Automate_Your_Media_at_Scale-2.png\")
<\/figure><\/div>\n\n\n3. One Image \u2192 A Responsive
srcset<\/code> You Can Paste Into Any Page<\/h3>\n\n\n\nf_auto\/q_auto<\/code>) onto each so Cloudinary serves AVIF\/WebP\/JPEG per browser at the right quality, and assembles a ready-to-paste block.<\/p>\n\n\n
![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137781\/blog-Automate_Your_Media_at_Scale-3.webp\")
<\/figure><\/div>\n\n\n4. A Source Video \u2192 A Polished, Embeddable Player<\/h3>\n\n\n\n
playsinline<\/code>, and muted autoplay-on-scroll. It outputs both an embed_url<\/code> and a responsive <iframe><\/code> snippet.<\/p>\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137781\/blog-Automate_Your_Media_at_Scale-4.webp\")
<\/figure><\/div>\n\n\nf_auto:video<\/code>). Helpfully, the node catches that exact conflict and tells you how to fix it.<\/p>\n\n\n\n5. Audit and Govern a Sprawling Library \u2013 Automatically<\/h3>\n\n\n\n
tags=n8n-blog<\/code> so it’s safe to run as-is \u2014 change or remove that expression (e.g. folder:products\/*<\/code>, or leave it empty) to scan more broadly, up to your whole library. A Code node applies your governance rules \u2014 here, flag anything untagged or over 1 MB<\/em>. Flagged assets get a needs-review<\/code> tag appended (existing tags preserved); everything rolls up into an audit report you can send to Slack or email.<\/p>\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137781\/blog-Automate_Your_Media_at_Scale-5.webp\")
<\/figure><\/div>\n\n\n6. Accessible Video With AI-Generated Captions \u2013 No
.vtt<\/code> Files<\/h3>\n\n\n\n\n
es<\/code>, fr-FR<\/code>) for auto-translated tracks. Translation uses the Google Translate add-on<\/strong>: Register for it (free tier available) on the Cloudinary Add-ons page<\/a>, then enable it under Settings \u2192 Security \u2192 Unsigned add-on transformations<\/strong>. The original-language captions above need no add-on.<\/p>\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137782\/blog-Automate_Your_Media_at_Scale-6.webp\")
<\/figure><\/div>\n\n\nplayer.source(...)<\/code> snippet for the Cloudinary Video Player SDK<\/a>. On most accounts the unsigned actions for generating video details, transcripts, and chapters are enabled by default \u2014 see the customization docs<\/a>.<\/p>\n\n\n\nHow to Import These Workflows<\/h2>\n\n\n\n
.json<\/code> file \u2014 each section above links straight to it. Importing one takes a few seconds.<\/p>\n\n\n\n1. Install the Cloudinary Node (Once)<\/h3>\n\n\n\n
n8n-nodes-cloudinary<\/code>).<\/p>\n\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137784\/blog-Automate_Your_Media_at_Scale-7.png\")
<\/figure>\n\n\n\n2. Import the Workflow<\/h3>\n\n\n\n
.json<\/code>\u00a0files. (You can also drag the file onto the canvas.)<\/p>\n\n\n![\"The](\"https:\/\/cloudinary-marketing-res.cloudinary.com\/image\/upload\/v1786137784\/blog-Automate_Your_Media_at_Scale-8.png\")
<\/figure><\/div>\n\n\n3. Add Your Cloudinary Credentials<\/h3>\n\n\n\n
4. Run It<\/h3>\n\n\n\n
Where to Take It Next<\/h2>\n\n\n\n
transformation<\/code> string and every node speaks plain n8n JSON, you can drop these media steps into any<\/em> pipeline:<\/p>\n\n\n\n\n