Output · Databases and cloud

S3 Sink

Saves a table to an S3 bucket as Parquet or CSV, or uploads a file another node wrote, such as a finished report.

Also known as: Upload to S3

How it works

Type the destination URI, such as s3://bucket/exports/sales.parquet, and pick an S3 credential from the vault; both are required. With a table on the input the node writes it in the chosen Format, parquet (the default) or csv, with an optional Compression for Parquet (snappy, zstd or gzip; blank uses the default) and Partition by columns that become folders under the URI. Overwrite existing is off by default, so an existing object stops the run. With a file on the input, such as the output of Write Report, Write Excel or Write CSV, the file is uploaded as is and the URI is its object key; format, compression and partitioning do not apply. Endpoint and Region are only needed for an S3-compatible service or to override the credential's region.

Inputs and outputs

Inputs

  • data — Any

Outputs

None — this node starts a workflow.

Settings

The Attributes panel of S3 Sink, as in the app: the controls work, but nothing runs — there is no data behind it.

The same settings, as the Assistant writes them
{
  uri: string
  format: "parquet"|"csv"
  credentialName: string
  compression?: "snappy"|"zstd"|"gzip"
  overwrite: boolean
  partitionBy?: string[]
  endpoint?: string
  region?: string
}

a Table input is COPYed with format/compression/partitionBy; a File input (Write Report/Excel/CSV) is uploaded as-is and uri is its object key, e.g. "s3://bucket/reports/q3.pdf" — format, compression and partitionBy apply to tables only

Example

You publish the monthly PDF to a shared bucket. Wire Write Report into the node, set URI to s3://acme-reports/monthly/2026-10.pdf, pick the credential and turn Overwrite existing on so a re-run replaces the file.