Short answer: Drop the "Cloudinary → Upload Image" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Image URL file | url | Required | Image URL. e.g. "https://example.com/photo.jpg" |
Folder folder | string | Optional | Folder. e.g. "uploads/2026" |
Public ID public_id | string | Optional | Custom name for the image (optional) |
{"file": "https://example.com/photo.jpg","folder": "uploads/2026","public_id": "{{trigger.public_id}}"}
{"url": "http://res.cloudinary.com/demo/image/upload/photo.jpg","bytes": 524288,"width": 1920,"format": "jpg","height": 1080,"version": 1712835600,"public_id": "uploads/2026/photo","secure_url": "https://res.cloudinary.com/demo/image/upload/photo.jpg"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.