Menu
Mattering Automations connector

A Cloudflare R2 MCP that reaches the objects, not just the buckets

Connect one credential carrying an account ID, a scoped API token and an R2 access key pair, and bucket management, object reads and writes, presigned URLs, lifecycle and lock rules, CORS, custom domains and event notification rules all become workflow steps. An AI agent can find a file and mint a link that expires, a workflow can archive its own output straight into a bucket, and the results land next to your tasks and databases instead of in a terminal.

38 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Cloudflare R2 MCP connector does

The Cloudflare R2 connector for Mattering Automations is 38 nodes, 17 that read and 21 that act, spanning both of R2's HTTP surfaces. On the management API: buckets from creation through storage class and deletion, CORS policies, lifecycle rules, bucket lock rules, custom domains, the managed r2.dev domain, Sippy incremental migration, account storage metrics, event notification rules, and temporary access credentials. On R2's S3 compatible API: list, head, get, put, copy and delete objects, bulk delete, multipart upload listing and abort, and locally signed presigned URLs.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can list a bucket's objects by prefix, check one key's size and content type without downloading it, and hand back a presigned URL that expires, with no one opening the Cloudflare dashboard and no shell access anywhere in the loop.

The interesting engineering here is that R2 is one product with two APIs that do not share credentials. The management API takes a scoped Cloudflare API token as a bearer header and answers in JSON. The S3 compatible API takes an R2 access key pair and requires AWS Signature Version 4 over XML. Shipping two connectors would have split the workflows people actually build, because creating a bucket and then uploading to it, or listing objects and then writing a lifecycle rule over their shared prefix, crosses that line constantly. So this is one connector with one credential holding both halves, and every node declares which plane it belongs to. A credential carrying only the API token still runs all 28 management nodes, and the S3 nodes fail with a message naming the missing field rather than a signature error. Every S3 response is parsed into flat JSON before it reaches the next node, so nothing downstream has to read XML.

The safety modeling is stated on the nodes rather than buried. Seven nodes are flagged destructive, and object deletes are the ones to respect: R2 keeps no previous object versions and has no recycle bin, so a deleted object is gone. S3 delete is idempotent by design and R2 follows S3 here, which means deleting a key that was never there still reports success, so success is not proof the object existed. Two nodes that are not flagged are worth the same care. Cloudflare R2: Set Lifecycle Rules writes rules that delete objects later on a schedule, so a wrong prefix quietly expires the wrong files, and Cloudflare R2: Update Managed Domain with enabled set to true makes every object in a bucket readable by anyone who knows the URL. Both say so in their own descriptions.

One connection, three surfaces

  • Visual automations. Drag Cloudflare R2 nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Cloudflare R2 node, ready to drop on the canvas

38 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 17

Cloudflare R2: Generate Presigned URL

Sign a temporary URL for one object. Nothing is called and nothing in R2 changes, which is why this is a safe read. What comes back is not inert: THE URL LETS ANYONE WHO HOLDS IT PERFORM THE CHOSEN METHOD ON THAT OBJECT WITH NO FURTHER AUTHENTICATION until it expires. Expiry is the expires_in field in seconds (1 to 604800, which is 7 days; this node defaults to 3600). Use a presigned PUT to let a browser or worker upload straight to R2, and a presigned GET to share a file from a private bucket without making the bucket public.

Cloudflare R2: Get Bucket

Fetch one R2 bucket's properties: creation date, location hint, default storage class and jurisdiction.

Cloudflare R2: Get Bucket CORS Policy

Read a bucket's CORS rules: allowed methods, origins and headers, exposed headers and the preflight cache duration.

Cloudflare R2: Get Bucket Lock Rules

Read a bucket's lock rules, which block deletion or overwriting of matching objects for an age, until a date, or indefinitely.

Cloudflare R2: Get Custom Domain

Read one custom domain's settings: enabled state, minimum TLS version, cipher allowlist, zone, and ownership and SSL status.

Cloudflare R2: Get Event Notification Rules For Queue

Read the notification rules that send a single queue messages for one bucket, with each rule's id, actions and filters.

Cloudflare R2: Get Lifecycle Rules

Read a bucket's object lifecycle rules: which prefixes expire, when incomplete multipart uploads are aborted, and any storage class transitions.

Cloudflare R2: Get Managed Domain

Read the bucket's Cloudflare managed r2.dev domain and whether public access through it is switched on. Enabled means anyone with the URL can read the bucket's objects.

Cloudflare R2: Get Object

Download an object's contents. Text that decodes as UTF-8 is returned as content with encoding utf-8; anything else is base64 in the same field with encoding base64. The body is capped at 256 KB of raw bytes, and truncated plus the real size are always reported, so a clipped read is never mistaken for a whole one. For anything larger, use Cloudflare R2: Generate Presigned URL and hand the URL to a worker that can stream it.

Cloudflare R2: Get Sippy Configuration

Read a bucket's Sippy configuration: whether incremental migration is on, and which source bucket misses are copied from. Secrets are not echoed, only the access key id.

Cloudflare R2: Get Storage Metrics

Object counts and stored bytes across every R2 bucket in the account, split by storage class and by published versus uploaded state. This is a current snapshot with no date range, and Cloudflare notes it may lag the latest writes.

Cloudflare R2: Head Object

Fetch an object's metadata without downloading it: size, content type, ETag, last modified time and any custom metadata. The cheap way to check whether a key exists, since a missing key comes back as HTTP 404 with no body.

Cloudflare R2: List Buckets

List the account's R2 buckets with creation date, location hint, storage class and jurisdiction. This is the node every bucket picker in this connector reads from, and the cheapest call for checking that the API token half of the credential works.

Cloudflare R2: List Custom Domains

List the custom domains attached to a bucket, with whether each is enabled and its ownership and SSL certificate status. This node populates the domain picker on the other custom domain nodes.

Cloudflare R2: List Event Notification Rules

List every event notification rule on a bucket, grouped by the queue that receives them, with each rule's actions, prefix and suffix filters. Use it to find the queueId the other notification nodes need.

Cloudflare R2: List Multipart Uploads

List multipart uploads that were started and never completed. Their parts still occupy the bucket, so this is the node that finds the cleanup work; abort them with Cloudflare R2: Abort Multipart Upload, or expire them automatically with a lifecycle abortMultipartUploadsTransition rule.

Cloudflare R2: List Objects

List objects in a bucket with key, size, last modified time, ETag and storage class. Calls the S3 ListObjectsV2 operation and returns ONE page: set max_keys (up to 1000), narrow with prefix, and follow next_continuation_token for more. Use delimiter to fold keys into folder style groups, which come back as common_prefixes.

Action nodes 21

Cloudflare R2: Abort Multipart Upload

DESTRUCTIVE: abort an in progress multipart upload and discard every part already sent. The upload cannot be resumed afterwards; whoever was uploading has to start again. Safe and useful against uploads that Cloudflare R2: List Multipart Uploads shows as stale.

Cloudflare R2: Add Custom Domain

Attach a custom domain to a bucket so its objects are served from a hostname you control. The domain must be on a zone in the same Cloudflare account. Setting enabled to true makes the bucket's objects PUBLICLY readable at that hostname. Reversible with Cloudflare R2: Remove Custom Domain.

Cloudflare R2: Copy Object

Copy an object inside R2 without moving bytes through this automation. Source and destination may be different buckets in the same account and jurisdiction. The source is left alone, so a move is this node followed by Cloudflare R2: Delete Object. Copying onto an existing destination key replaces it.

Cloudflare R2: Create Bucket

Create an R2 bucket. Reversible with Cloudflare R2: Delete Bucket while the bucket is still empty. Bucket names are account wide, so a create fails if the name is taken.

Cloudflare R2: Create Event Notification Rule

Create notification rules that push a message to a Cloudflare Queue when matching objects change. The queue must already exist. A bucket allows up to 100 rules, and Cloudflare rejects rules that overlap so one event cannot fire twice. Reversible with Cloudflare R2: Delete Event Notification Rules.

Cloudflare R2: Create Temporary Access Credentials

Mint a short lived S3 access key, secret and session token scoped to one bucket, and optionally to named objects or prefixes. Hand these to a service that should reach only that slice of R2. THE RETURNED SECRET AND SESSION TOKEN GRANT REAL ACCESS for ttlSeconds and cannot be revoked early, so keep the ttl short and do not log the output. Nothing is created that needs cleaning up: the credentials expire on their own.

Cloudflare R2: Delete Bucket

DESTRUCTIVE: delete an R2 bucket. The bucket must already be empty. Its configuration (CORS, lifecycle, domains, notification rules) and its name reservation are gone and cannot be restored.

Cloudflare R2: Delete Bucket CORS Policy

DESTRUCTIVE: remove a bucket's whole CORS policy. Browser requests from other origins start failing immediately, and the previous rules are not recoverable from R2. Capture them with Cloudflare R2: Get Bucket CORS Policy first if you may want them back.

Cloudflare R2: Delete Event Notification Rules

DESTRUCTIVE: remove the bucket's notification rules for one queue. Downstream workflows stop receiving messages immediately and the rule definitions are gone; capture them with Cloudflare R2: Get Event Notification Rules For Queue first if you may need to restore them.

Cloudflare R2: Delete Object

DESTRUCTIVE: permanently delete one object. R2 keeps no previous versions and there is no recycle bin, so the bytes are gone. Note that S3 delete is idempotent: deleting a key that does not exist still returns success, so a success here is not proof the object was there.

Cloudflare R2: Delete Objects In Bulk

DESTRUCTIVE: permanently delete up to 1000 objects in one call. R2 keeps no previous versions, so every key listed is gone for good. The response reports each key under deleted or errors, and a partial failure still deletes the rest, so read both lists rather than only the status code.

Cloudflare R2: Disable Sippy

Turn Sippy off for a bucket. No objects are deleted: reads simply stop falling back to the source bucket, so anything not yet copied starts returning not found. Reversible with Cloudflare R2: Enable Sippy, which needs the source credentials again.

Cloudflare R2: Enable Sippy

Enable Sippy on a bucket: a read that misses in R2 is fetched from the source bucket and copied into R2 in the background. Both objects carry live cloud credentials, so treat this node's config as secret material. Reversible with Cloudflare R2: Disable Sippy, though objects already copied stay.

Cloudflare R2: Put Object

Upload an object. Give it content_url and the runner downloads that URL and stores the bytes, which is the right shape for real files; give it content for small inline text such as a JSON blob or a rendered report. One or the other, never both. Writing to a key that already exists REPLACES that object, and R2 keeps no previous version, so treat an overwrite as a delete plus a create.

Cloudflare R2: Remove Custom Domain

DESTRUCTIVE: detach a custom domain from a bucket. Every URL on that hostname stops resolving to the bucket immediately, and its TLS settings are discarded. Re-attaching means waiting for certificate issuance again.

Cloudflare R2: Set Bucket CORS Policy

REPLACE a bucket's CORS rules with the supplied list. This is a whole policy write, not a merge: rules you leave out are removed. Read the current policy first with Cloudflare R2: Get Bucket CORS Policy and write the edited list back.

Cloudflare R2: Set Bucket Lock Rules

REPLACE a bucket's lock rules with the supplied list. Rules you leave out are removed. Note what a lock rule DOES: while it applies, matching objects cannot be deleted or overwritten, including by you, so an Indefinite condition is a decision to keep those objects.

Cloudflare R2: Set Lifecycle Rules

REPLACE a bucket's lifecycle rules with the supplied list. Rules you leave out are removed, so read the current set first. The rules themselves delete objects on a schedule, so check the prefix and age before writing: a wrong prefix here expires the wrong objects later, quietly.

Cloudflare R2: Update Bucket Storage Class

Change a bucket's DEFAULT storage class, which applies to objects uploaded after the change. Existing objects keep the class they were written with; move those with a lifecycle storage class transition instead. Reversible by setting the previous class back.

Cloudflare R2: Update Custom Domain

Update an attached custom domain: turn public access on or off, raise the minimum TLS version, or set a cipher allowlist. Only the fields you fill in are sent. Setting enabled to false stops serving the bucket at that hostname without detaching the domain.

Cloudflare R2: Update Managed Domain

Turn the bucket's managed r2.dev domain on or off. Turning it ON makes every object in the bucket readable by anyone who knows the URL, with no authentication. Reversible by setting enabled back to false.

Connecting Cloudflare R2 takes one credential

R2 has to be enabled on the account before any of this is reachable: Cloudflare's own getting started guide has you add an R2 subscription through a checkout flow, and it runs through billing checkout, so an account with no billing profile is asked to complete one. After that, one credential carries four values, because R2's two APIs authenticate differently. Both planes need the account ID, and Cloudflare's documented way to get it is to search the dashboard, or press CMD or CTRL plus K, and choose Copy account ID; the same value also forms part of the S3 API endpoint shown on the R2 page. The API token is a scoped Cloudflare API token with R2 permissions, created at dash.cloudflare.com under My Profile, then API Tokens, and it authenticates the 28 management nodes as a bearer header. The R2 access key ID and secret access key are a separate pair, created from the R2 object storage page by selecting Manage next to API Tokens under Account Details, and they sign the 10 S3 nodes with AWS Signature Version 4. The R2 secret access key is shown exactly once at creation, so copy it then. The account ID is stored on the credential rather than asked for on each node, so the two halves can never point at different accounts inside one run.

1

Enable R2 on the account first. Cloudflare's getting started guide has you add an R2 subscription by completing a checkout flow, and the R2 API token screen the next steps depend on is not reachable until that is done. Cloudflare runs the flow through billing checkout, so an account with no billing profile is asked to complete one.

2

Sign in at dash.cloudflare.com and get your account ID: search the dashboard, or press CMD or CTRL plus K, and choose Copy account ID. The same value appears again as part of the S3 API endpoint on the R2 page.

3

Open My Profile, then API Tokens, and click Create Token. Build a token with the R2 permissions your workflows need and copy it when Cloudflare shows it.

4

Go to the R2 object storage page and, under Account Details, select Manage next to API Tokens, then Create API token. Copy both the access key ID and the secret access key before you leave the page: the secret is shown once and cannot be retrieved later.

5

In Mattering Automations, open Connectors, click Add Connector, choose Cloudflare R2, and create a credential with all four values.

6

Click Test Connection. Mattering lists the account's R2 buckets, which proves the account ID and the API token. It does not exercise the S3 half, so run Cloudflare R2: List Objects against a real bucket once to confirm the access key pair as well.

7

All 38 nodes appear in the canvas palette. Run Cloudflare R2: List Buckets first: it feeds every bucket picker in the connector.

Common uses for the Cloudflare R2 MCP

Share a private file without making the bucket public

Cloudflare R2: Generate Presigned URL signs a link locally, calling nothing and changing nothing in R2, and the link lets its holder run one method on one object until it expires. That is the whole pattern for sending a customer their export or letting a browser upload straight to R2 with a presigned PUT, without ever switching on public access. Expiry is set in seconds, anywhere from 1 second to 604800 seconds, and the node defaults to 3600. Treat the URL as the credential it is: it cannot be revoked before it expires, so keep the window short and keep it out of anything that logs URLs.

Workflows that archive their own output

Cloudflare R2: Put Object takes content_url and downloads that URL server side before storing the bytes, so a rendered PDF, an export from another connector, or a generated report goes into a bucket without anyone pasting a file into a canvas field. Small inline text, a JSON blob or a summary from an upstream node, goes in the content field instead. One or the other, never both. The honest caveat is that writing to an existing key replaces the object and R2 keeps no previous version, so date or run the key if you want history.

An agent that can read a bucket safely

The read surface is the one to hand an assistant first. Cloudflare R2: List Objects walks a bucket by prefix, which is a real hierarchical filter because R2 keys are path shaped, so asking for invoices/2026 narrows the listing instead of filtering a page after the fact. Cloudflare R2: Head Object answers whether a key exists and what it weighs without downloading it, and Cloudflare R2: Get Object returns the bytes with a 256 KB cap and an explicit truncated flag so a clipped read is never mistaken for a whole file. None of the three can change anything in the bucket.

Storage housekeeping on a schedule

Cloudflare R2: List Multipart Uploads finds uploads that were started and never finished, whose parts still sit in the bucket, and Cloudflare R2: Abort Multipart Upload clears them. Cloudflare R2: Set Lifecycle Rules handles the recurring version of the same job, expiring objects under a prefix and aborting stale multipart uploads automatically. Read the current rules with Cloudflare R2: Get Lifecycle Rules first, because a lifecycle write replaces the whole rule set rather than merging into it, and check the prefix twice: these rules delete objects later, when nobody is watching the run.

Provision a bucket and its front door from a workflow

Cloudflare R2: Create Bucket stands up storage, Cloudflare R2: Set Bucket CORS Policy lets a specific origin's browser code reach it, and Cloudflare R2: Add Custom Domain serves the objects from a hostname you control, on a zone in the same Cloudflare account. The alternative front door is the managed r2.dev domain through Cloudflare R2: Update Managed Domain, and it deserves a deliberate decision rather than a default: switching it on makes every object in the bucket readable by anyone with the URL. Cloudflare R2: Set Bucket Lock Rules goes the other way, blocking deletion or overwriting of matching objects, including by you, for as long as the rule applies.

Storage reporting that lands in a database

Cloudflare R2: Get Storage Metrics returns object counts and stored bytes across every bucket in the account, split by storage class and by published versus uploaded state, and Cloudflare R2: List Buckets gives the names and creation dates to join them to. A scheduled sweep can write both into a Mattering database and open a task when a bucket grows faster than expected. One thing to know before building a chart on it: the metrics node is a point in time snapshot with no date range, and Cloudflare notes it can lag the latest writes, so track change by storing successive snapshots rather than asking the API for a window it does not offer.

Example: A report is generated, stored, and shared with a link that expires

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a scheduled run, or a webhook from the workflow that finished producing the file, carrying the URL of the generated report.

2

Cloudflare R2: Put Object stores it with content_url, writing to a dated key such as reports/2026/08/weekly.pdf so the previous week's file is not replaced.

3

Cloudflare R2: Head Object confirms the object landed and reports its real size, which is the cheap check that the upload was not silently empty.

4

Cloudflare R2: Generate Presigned URL mints a GET link with a short expiry, so the recipient can download the report without the bucket ever becoming public.

5

The workflow posts the link into a Mattering Comms channel and opens a task in Mattering Productivity for whoever reviews the numbers.

6

A separate weekly run uses Cloudflare R2: List Objects with the reports/ prefix and Cloudflare R2: Delete Objects In Bulk to clear anything older than the retention window, or Cloudflare R2: Set Lifecycle Rules does the same job once and leaves it to R2.

Cloudflare R2 MCP questions, answered

What Cloudflare R2 operations are supported?

38 nodes, 17 query and 21 action, across R2's two APIs. On the management API: buckets (list, get, create, default storage class, delete), CORS policies (get, set, delete), lifecycle rules, bucket lock rules, custom domains (list, get, add, update, remove), the managed r2.dev domain, Sippy incremental migration (get, enable, disable), account storage metrics, event notification rules (list, get by queue, create, delete), and temporary access credentials. On the S3 compatible API: list objects, head object, get object, put object, copy object, delete object, bulk delete, list multipart uploads, abort multipart upload, and presigned URL generation. Deliberately not shipped: the create and upload and complete half of multipart uploads, Super Slurper bulk migration, and the S3 operations the management plane already exposes as readable JSON.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

How is this different from the Cloudflare connector on Mattering?

The Cloudflare connector covers the wider Cloudflare API: DNS, cache purge, zone settings, Workers KV, Worker scripts and more, and it includes four R2 bucket management nodes so a workflow about DNS can also see a bucket list. This connector is about the objects. It holds the S3 credentials the other one deliberately does not, so it can read, write, copy, delete and presign the contents of a bucket, and it surrounds those with the bucket settings that object work actually touches: CORS, lifecycle, lock rules, custom domains and event notification rules. The overlap on bucket listing is intentional and the node types do not collide. Run whichever fits, or both.

Cloudflare runs its own MCP servers. How is this different?

It is, and they are worth knowing about: Cloudflare hosts a set of MCP servers, including a Cloudflare API server at mcp.cloudflare.com/mcp that covers the REST API across Cloudflare's products, R2 bucket management among them, and a separate Workers Bindings server. The distinction is which R2 API is on the other side. Cloudflare's API server proxies the REST API, and the REST API has no object level operations at all, because R2 exposes object reads and writes only through its separate S3 compatible plane. This connector holds both halves of the credential, so listing, reading, writing, copying, deleting and presigning the contents of a bucket are available as nodes, alongside the bucket settings that object work touches: CORS, lifecycle, lock rules, custom domains and event notification rules. They answer different questions, and running both is fine.

Why does one credential need both an API token and an R2 access key pair?

Because R2 has two HTTP surfaces with different authentication and they cannot be merged. The management API authenticates a scoped Cloudflare API token as a bearer header and returns JSON; the S3 compatible API authenticates an R2 access key pair with AWS Signature Version 4 and speaks XML. The account ID sits on the credential too, because the S3 plane builds its hostname from it. The halves are independent in practice: a credential with only the API token runs all 28 management nodes, and the 10 S3 nodes report exactly which field is missing and why that plane needs it. The tradeoff is one setup that takes a few minutes longer, in exchange for workflows that can create a bucket and upload to it without keeping two connections in sync.

Can it upload and download large files?

Uploads, yes, within limits: Cloudflare R2: Put Object takes a content_url and the runner downloads that URL server side, capped at 100 MB, so a real file never has to be pasted into a canvas field. For anything larger, use Cloudflare R2: Generate Presigned URL to mint a presigned PUT and let the browser, worker or service holding the file upload straight to R2. Downloads through the canvas are deliberately smaller: Cloudflare R2: Get Object caps at 256 KB of raw bytes and always reports truncated plus the true size, because pushing a large binary through an automation payload helps nobody. A presigned GET is the right way to hand a big object to whatever should actually consume it.

Is it safe to let an AI agent generate presigned URLs?

It is safe in the sense that the node changes nothing in R2, and worth a policy in the sense that what it returns is a working credential. The signing happens locally, no API call is made, and no object is created or altered, which is why it is classed as a safe read. But the URL grants whoever holds it the chosen method on that exact object with no further authentication until it expires, and it cannot be revoked early. R2 allows expiries from 1 second to 604800 seconds, which is 7 days, and this node defaults to 3600. Keep the window as short as the task allows, prefer GET over PUT and DELETE when the agent only needs to share a file, and remember that the URL is as sensitive as the object behind it. R2 supports presigned GET, HEAD, PUT and DELETE; presigned POST form uploads are not supported.

What are the rate limits?

The management plane is governed by the Cloudflare API limit of 1,200 requests per 5 minutes, and the number is cumulative rather than per token: the dashboard, an API key and an API token all draw from the same budget, so a heavy automation sweep and a person clicking around the dashboard compete with each other. Cloudflare's docs differ on what that budget is attached to. The general API reference scopes it per user, while the R2 limits page scopes the same number across the account, so plan a heavy sweep against the tighter reading and you are safe under either. The S3 compatible plane is a separate surface with its own behaviour and Cloudflare does not document a fixed public per-account request ceiling for it, so this page will not invent one. It does publish one S3 plane constraint worth designing around: a limit of one concurrent write per second to the same object name, so the shape to avoid is a loop repeatedly overwriting a single key, while writes spread across different keys are not the same problem. Either way, nodes report the error on their output rather than silently retrying, so a workflow can wait and continue rather than losing the run.

What happens if an automation deletes the wrong object?

It is gone. R2 keeps no previous object versions and has no recycle bin, so Cloudflare R2: Delete Object and Cloudflare R2: Delete Objects In Bulk are final, and both are flagged destructive. Two behaviours make this worth designing around rather than trusting to care. S3 delete is idempotent by design and R2 follows S3 here, so deleting a key that does not exist still returns success, which means a green run is not evidence the object was there. And bulk delete can partially fail, reporting each key under deleted or errors while still deleting the rest, so read both lists rather than only the status code. The pattern that holds up is list or head first, gate the delete behind a condition or an approval task, and use bucket lock rules on anything that must not be deletable at all.

38 nodes waiting on the canvas

Put Cloudflare R2 to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Cloudflare R2 is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products