How do I import "Upload a file and get a list of all the files in a bucket" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "Upload a file and get a list of all the files in a bucket" use?

It uses: manual, httpRequest, s3. The flow diagram above shows how each service connects across the 4 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.

What trigger type does "Upload a file and get a list of all the files in a bucket" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "Upload a file and get a list of all the files in a bucket" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, s3.

← Workflows

Upload a file and get a list of all the files in a bucket

4 nodes · manual, httpRequest, s3

Engine: n8n
Nodes: 4
Trigger: scheduled/triggered
Source file: 1088_Manual_S3_Import_Webhook.json

Workflow flow

IntegrationsManualHTTPS3

100%

TRIGGER

On clicking 'execute'

Manual

HTTP Request

HTTP

4 steps · flows top to bottom, branches left to right

Browse by integration

manual httpRequest s3

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Upload a file and get a list of all the files in a bucket is a free n8n workflow on OpenRuna — 4 nodes connecting manual, httpRequest, s3. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"Upload a file and get a list of all the files in a bucket" is an n8n automation built from 4 nodes spanning manual, httpRequest, s3. 4 nodes · manual, httpRequest, s3 A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Use it as a starting template when wiring manual, httpRequest, s3 — adjust node parameters to your accounts and record IDs.
Import "Upload a file and get a list of all the files in a bucket" into n8n, reconnect credentials for manual, httpRequest, s3, and run the same automation in your own workspace.
Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
Study how data moves from manual to httpRequest before building your own variant.

Example output

Imported into n8n, "Upload a file and get a list of all the files in a bucket" exposes 4 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, s3. Set your credentials on the manual node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Upload a file and get a list of all the files in a bucket" into Claude and ask it to explain each of the 4 nodes. Claude is good at suggesting credential mappings for manual, httpRequest, s3, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Upload a file and get a list of all the files in a bucket" to your accounts — which manual, httpRequest, s3 credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 4 nodes.

Frequently asked questions

How do I import "Upload a file and get a list of all the files in a bucket" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Upload a file and get a list of all the files in a bucket" use?: It uses: manual, httpRequest, s3. The flow diagram above shows how each service connects across the 4 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.
What trigger type does "Upload a file and get a list of all the files in a bucket" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Upload a file and get a list of all the files in a bucket" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, s3.