Short answer: Drop the "Cloudflare R2 → Get R2 Object" 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 |
|---|---|---|---|
Bucket bucket | string | Required | — |
Object Key key | string | Required | Full key including any prefix. |
{"bucket": "{{trigger.bucket}}","key": "path/to/file.png"}
{"url": "https://cdn.tinycommand.app/__tmp/abc.png","byte_size": 12345,"mime_type": "image/png"}
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.