S3 n8n INTEGRATION: AUTOMATE S3 WITH N8N

This action retrieves a list of folders from a specified S3 bucket, making it invaluable when you need to programmatically discover your storage structure or iterate through directories in subsequent workflow steps.

Key parameters: Credential to connect with (required), Resource set to "Folder" (required), Operation set to "Get Many" (required), Bucket Name (required), Return All toggle (optional), and Limit defaulting to 100 (optional).

Use this action when building workflows that need to audit folder structures, generate reports on storage organization, or dynamically process content across multiple directories. It's particularly useful for backup verification workflows or content management systems that need to sync folder hierarchies.

When you need to clean up your S3 storage programmatically, the Delete Folder action removes entire directory structures from your buckets. This is essential for maintenance workflows, temporary file cleanup, or project archival processes.

Key parameters: Credential to connect with (required), Resource set to "Folder" (required), Operation set to "Delete" (required), Bucket Name (required), and Folder Key providing the full path of the folder to delete (required).

Ideal for automated cleanup routines—for example, deleting temporary processing folders after jobs complete, or removing outdated backup directories based on retention policies.

Programmatically create new folder structures in your S3 buckets. This action is fundamental for workflows that need to organize files dynamically, such as creating date-based directories or project-specific storage locations.

Key parameters: Credential to connect with (required), Resource set to "Folder" (required), Operation set to "Create" (required), Bucket Name (required), Folder Name (required), and Additional Fields for optional configurations.

Perfect for onboarding workflows that provision storage for new clients, or content pipelines that need organized directory structures before file uploads begin.

The Upload a File action is likely your most-used S3 operation—it takes binary data from your workflow and stores it in your S3 bucket. Whether you're saving processed images, generated reports, or backup files, this action handles it all.

Key parameters: Credential to connect with (required), Resource set to "File" (required), Operation set to "Upload" (required), Bucket Name (required), File Name with full path (required), Binary File toggle (optional), Input Binary Field defaulting to "data" (required when binary is enabled), Additional Fields and Tags for metadata (optional).

Use cases include: automatically uploading invoice PDFs after generation, saving processed images from an image manipulation workflow, or archiving webhook payloads for audit purposes.

Retrieve lists of files from your S3 buckets for processing, reporting, or synchronization workflows. This action returns metadata about multiple files, which you can then iterate through for bulk operations.

Key parameters: Credential to connect with (required), Resource set to "File" (required), Operation set to "Get Many" (required), Bucket Name (required), Return All toggle (optional), Limit defaulting to 100 (optional), and Options for filtering like prefix or delimiter (optional).

Essential for workflows that need to process all files in a bucket, generate file inventories, or sync S3 contents with other systems like Dropbox or Google Sheets.

The Download action retrieves actual file content from S3 and makes it available as binary data in your workflow. This is crucial for any automation that needs to process, transform, or transfer files stored in S3.

Key parameters: Credential to connect with (required), Resource set to "File" (required), Operation set to "Download" (required), Bucket Name (required), File Key with full path (required), and Put Output File in Field defaulting to "data" (optional).

Use this when building ETL pipelines that process S3-stored data, email workflows that attach S3 files via Gmail, or integration flows that move files between S3 and other services.

Remove specific files from your S3 storage programmatically. The Delete File action is essential for cleanup routines, file rotation policies, and workflows that manage temporary storage.

Key parameters: Credential to connect with (required), Resource set to "File" (required), Operation set to "Delete" (required), Bucket Name (required), File Key with exact path (required), and Options for additional parameters (optional).

Commonly used in: log rotation workflows that delete old files, temporary file cleanup after processing completes, or content management systems that need to remove deprecated assets.

Duplicate files within or between S3 buckets without downloading and re-uploading. The Copy action is efficient for backup creation, file organization, and multi-region replication scenarios.

Key parameters: Credential to connect with (required), Resource set to "File" (required), Operation set to "Copy" (required), Source Path including bucket (required), Destination Path with new location (required), and Additional Fields for extra options (optional).

Perfect for creating backup copies before processing, organizing files into new folder structures, or duplicating assets across different bucket configurations.

Search within S3 buckets to find specific objects based on criteria. This action helps you locate files dynamically rather than hardcoding paths, making your workflows more flexible and resilient.

Key parameters: Credential to connect with (required), Resource set to "Bucket" (required), Operation set to "Search" (required), Bucket Name (required), Return All toggle (optional), Limit defaulting to 100 (optional), and Additional Fields for search filters (optional).

Useful when building workflows that need to find files matching certain patterns, locate the most recent upload, or discover files for batch processing.

List all buckets accessible with your credentials. This action is useful for administrative workflows, storage auditing, and multi-tenant applications that need to discover available storage locations.

Key parameters: Credential to connect with (required), Resource set to "Bucket" (required), Operation set to "Get Many" (required), Return All toggle (optional), and Limit defaulting to 100 (optional).

Ideal for monitoring dashboards that track storage usage, provisioning workflows that verify bucket existence, or administrative tools that manage multi-bucket environments.

Remove entire buckets from your S3 storage. This is a powerful administrative action typically used for cleanup, decommissioning, or automated environment management.

Key parameters: Credential to connect with (required), Resource set to "Bucket" (required), Operation set to "Delete" (required), and Name with exact bucket name (required).

Note: Buckets typically must be empty before deletion. Use this in controlled administrative workflows or teardown processes for temporary environments.

Programmatically provision new S3 buckets. This action is essential for workflows that need to create isolated storage for new clients, projects, or environments.

Key parameters: Credential to connect with (required), Resource set to "Bucket" (required), Operation set to "Create" (required), Name for the unique bucket name (required), and Additional Fields for settings like region or ACLs (optional).

Perfect for onboarding automations that provision storage for new accounts, or infrastructure workflows that set up complete environments including storage. Consider pairing with Supabase for database provisioning.