Cloudflare R2
Cloudflare R2 zero-egress object storage
Cloudflare R2 is Cloudflare's S3-compatible object storage with zero egress fees — the breakthrough pricing that makes it attractive for content-distribution workloads where AWS S3's egress costs would be punishing (CDN origins, video hosting, large media downloads). Tiny Command exposes three actions, no triggers (R2 doesn't emit object-change webhooks directly; for event-driven workflows, use Cloudflare Workers to react to R2 events and POST to a Tiny Command webhook trigger): List Buckets (every R2 bucket in the connected Cloudflare account), List Objects (within a bucket, with optional prefix filter), Get Object (download an object's metadata or content). The connection uses R2-specific access keys (Cloudflare dashboard → R2 → Manage R2 API Tokens) which are S3-compatible. R2's S3 compatibility means most S3 client libraries work against R2 with just a base URL change. The endpoint is per-account: https://{account_id}.r2.cloudflarestorage.com.
Do anything Cloudflare R2 can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get R2 Object | Downloads object content from an R2 bucket. For workflows that need to fetch and process R2-stored content (CDN-origin files, archived backups, user-uploaded assets) downstream. |
| List R2 Buckets | Returns every R2 bucket in the account with name and creation date. Useful for bucket-inventory workflows and for resolving bucket names at workflow-build time. |
| List R2 Objects | Paginated objects within a bucket with optional prefix filter. Useful for batch-processing workflows that need to discover all objects matching a pattern (e.g., "all .csv files under exports/" for incremental ingestion). |
Pre-built Cloudflare R2 workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Cloudflare R2 event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Cloudflare R2 into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Cloudflare R2 once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Cloudflare R2 field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Cloudflare R2 integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Cloudflare R2 to Tiny Command?
What Cloudflare R2 triggers does Tiny Command support?
What Cloudflare R2 actions can I run from a workflow?
Is the Cloudflare R2 integration real-time?
Do I need to write code to use Cloudflare R2 with Tiny Command?
How much does the Cloudflare R2 integration cost?
More other apps people connect.
Same category as Cloudflare R2, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Cloudflare R2.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
