OtherReal-timeUpdated June 2026

Cloudflare R2 integration

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.

Connect Cloudflare R2

No credit card required · Set up in under 2 minutes

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

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	Inputs	Open action
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.	2 inputs	View
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.	0 inputs	View
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).	3 inputs	View

Recipes

Pre-built Cloudflare R2 workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Cloudflare R2 → Slack alerts

AI-triage every Cloudflare R2 event, ping the right channel only when it matters.

Cloudflare R2 → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Cloudflare R2 → Notion database

Turn Cloudflare R2 into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

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.

No JSON to read

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.

FAQ

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?

Open the Tiny Command workflow builder, drop in a Cloudflare R2 node, and click Connect. Authorize Cloudflare R2 once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Cloudflare R2 triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Cloudflare R2 today. Use Tiny Command's universal Webhook or Schedule trigger to start Cloudflare R2 workflows, then run any Cloudflare R2 action you need.

What Cloudflare R2 actions can I run from a workflow?

3 Cloudflare R2 actions are available out of the box, covering other operations like "Get R2 Object". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Cloudflare R2 integration real-time?

Cloudflare R2 actions execute synchronously inside your workflow. Tiny Command waits for Cloudflare R2's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Cloudflare R2 with Tiny Command?

No. Every Cloudflare R2 trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Cloudflare R2 API endpoint directly.

How much does the Cloudflare R2 integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Cloudflare R2 integration itself has no per-app surcharge.