Trouble Listing Files from Cloudflare R2 Using the n8n S3 Node

Below is some guidance on using the S3 node with Cloudflare R2 for listing files:

---

What’s Happening

• Bucket list works but not file listing:
  The S3 node in n8n supports a “Get all files” operation. However, when using non‑AWS endpoints (like Cloudflare R2) things may behave differently. It appears that while getting the bucket list works, listing files via the S3 node may not work as expected with R2. This isn’t necessarily a bug in n8n but can be due to differences in how Cloudflare R2 implements the S3 API.

---

Suggestions & Workarounds

1. Double-check your configuration:

   • Ensure that you have set the S3 endpoint correctly in your credentials. R2 requires you to supply a custom endpoint.
   • Verify that your access permissions for listing objects (files) in your R2 bucket are correctly configured.

2. Use the AWS S3 node with Cloudflare R2 endpoint:
   Although Cloudflare R2 isn’t AWS, its API is S3‑compatible. In some cases, configuring the credentials to use the AWS S3 node (with a custom endpoint pointing to your Cloudflare R2 region) has been a workaround for others.

3. Use HTTP Request node as an alternative:
   Even though you mentioned it “doesn’t seem easy or possible,” you might try constructing a request that directly calls the Cloudflare R2 compatible API for listing objects. This requires following Cloudflare’s API documentation:

   • You’d need to build a request with proper authentication headers.
   • Parse the response to extract file details.
     While this adds some complexity, it offers full control over the API call.

4. Check Cloudflare R2 documentation:
   There could be nuances in how Cloudflare R2 handles listing operations compared to AWS S3. Reviewing the official R2 API guidelines may reveal any additional query parameters or headers that need to be set.

---

Final Note

It’s not uncommon for S3‑compatible storage services like Cloudflare R2 to have subtle differences in their API behavior. While the S3 node in n8n is designed to work with many non‑AWS endpoints (like MinIO, Wasabi, or Digital Ocean Spaces), sometimes additional configuration or a different approach (like using HTTP Request) is required for full functionality.

I hope this helps clarify the situation and offers a path forward. If you’re still having trouble, checking the n8n community forums or submitting a feature request might help improve support for Cloudflare R2 in future versions.

---