Appearance
AWS S3
Store, retrieve, and manage objects in Amazon S3 buckets.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://s3.amazonaws.com |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | aws-s3 |
Using AWS S3 in a workflow
- Go to Connections and click New Connection.
- Pick AWS S3 from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET / | List all buckets |
GET /{Bucket} | List objects in a bucket |
PUT /{Bucket} | Create a new bucket |
DELETE /{Bucket} | Delete a bucket |
GET /{Bucket}/{Key} | Retrieve an object |
PUT /{Bucket}/{Key} | Upload an object |
DELETE /{Bucket}/{Key} | Delete an object |
HEAD /{Bucket}/{Key} | Get object metadata |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /
List all buckets
| Detail | Value |
|---|---|
| Operation ID | cloud.listBuckets |
| Method | GET |
| Path | / |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listBuckets. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
GET /{Bucket}
List objects in a bucket
| Detail | Value |
|---|---|
| Operation ID | cloud.listObjectsV2 |
| Method | GET |
| Path | /{Bucket} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listObjectsV2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
PUT /{Bucket}
Create a new bucket
| Detail | Value |
|---|---|
| Operation ID | cloud.createBucket |
| Method | PUT |
| Path | /{Bucket} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createBucket. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
DELETE /{Bucket}
Delete a bucket
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteBucket |
| Method | DELETE |
| Path | /{Bucket} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteBucket. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
GET /{Bucket}/{Key}
Retrieve an object
| Detail | Value |
|---|---|
| Operation ID | cloud.getObject |
| Method | GET |
| Path | /{Bucket}/{Key} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getObject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
PUT /{Bucket}/{Key}
Upload an object
| Detail | Value |
|---|---|
| Operation ID | cloud.putObject |
| Method | PUT |
| Path | /{Bucket}/{Key} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.putObject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
DELETE /{Bucket}/{Key}
Delete an object
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteObject |
| Method | DELETE |
| Path | /{Bucket}/{Key} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteObject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.
HEAD /{Bucket}/{Key}
Get object metadata
| Detail | Value |
|---|---|
| Operation ID | cloud.headObject |
| Method | HEAD |
| Path | /{Bucket}/{Key} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS S3 connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.headObject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS S3 API reference.