Put Object

s3.put_object
ActionFiles & storageconnection required

PUTs the object to S3 with SigV4-signed request.

Upload a text or binary object to an S3 bucket.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Amazon S3
Secret shape
{"access_key_id", "secret_access_key"}
Config it needs
region, bucket
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
key
Object key. Supports {{ }}.
stringYes———
body
Object contents: text, or a base64 blob when content_encoding='base64'. Leave empty to upload the upstream file (e.g. from GitHub/GitLab Download Archive).
stringNo———
content_encoding
Set to 'base64' when body is a base64 blob (e.g. from a download_archive node). Defaults to the upstream file's encoding, else text.
stringNo—one of "text", "base64"—
content_type
MIME type (defaults to the upstream file's).
stringNo———

Input

FieldTypeExample
file_content
The file, base64-encoded.
string—
content_encoding
stringbase64
filename
stringapp-main.zip
content_type
stringapplication/zip
size
Raw size in bytes (before base64).
number—

Output

One shape.

result

FieldTypeExample
ok
boolean—
key
string—
etag
string—
size
number—
version_id
The version this upload created; null on an unversioned bucket. The only handle on exactly these bytes once the key is overwritten.
string—
{
  "etag": "",
  "key": "",
  "ok": false,
  "size": 0,
  "version_id": ""
}

Solutions with Amazon S3

See Put Object run in a workflow.

In a technical demo we add the Amazon S3 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.