Short answer: Drop the "Cloudinary → List Resources" 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 |
|---|---|---|---|
Type type | options | Optional | Type. Options: Upload, Private, Authenticated |
Max Results max_results | number | Optional | Max Results |
{"type": "{{trigger.type}}","max_results": "{{trigger.max_results}}"}
{"resources": [{"url": "http://res.cloudinary.com/demo/image/upload/sample.jpg","bytes": 524288,"width": 1920,"format": "jpg","height": 1080,"public_id": "sample","created_at": "2026-04-11T10:00:00Z"}],"next_cursor": "cursor123"}
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.