Configuration
| Setting | Description |
|---|---|
| Integration | Your connected S3 integration |
| Destination Path | Target path in S3 — supports Mentions for dynamic paths (e.g., reports/{{date}}/) |
| Attachments | Files from upstream nodes to upload |
| Title | A human-readable description of the action |
| Setting | Description |
|---|---|
| Display Name | Human-readable name for the file |
| Field Name | The field containing the file data |
| Node ID | The upstream node that produced the file |
| MIME Type | File content type (e.g., text/csv) |
How It Works
Add a file-producing node upstream
Place an Export to CSV node before this one to generate the file.
Configure the destination
Set the S3 path where the file should be uploaded. Use Mentions for dynamic paths.
Output
The file is uploaded to the specified S3 path when the Agent runs. The upload is logged as a task.Example
Archive weekly reports to S3:- Export to CSV → generate a weekly account report
- Upload File → upload to
s3://reports/weekly/accounts-{{date}}.csv
Best Practices
- Use dynamic paths with Mentions to organize files by date, region, or category
- Pair with Export to CSV for the most common use case
- Verify S3 permissions are correctly configured on the integration
Related Nodes
- Export to CSV — generates the CSV file to upload
- Private Export — exports to BonData’s internal storage instead of S3