Create Bucket: AWS S3 action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Bucket Name bucket	string	Required	Bucket Name. Example: my-company-assets
Region Override region	string	Optional	Region Override. e.g. "uses connection region if blank"
ACL acl	options	Optional	ACL. Options: Private, Public Read

Sample request

{
  "bucket": "e.g. my-company-assets",
  "region": "uses connection region if blank",
  "acl": "{{trigger.acl}}"
}

Returns

{
  "Location": "/my-company-assets"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Bucket.

What does the Create Bucket action do in AWS S3?

Creates a new S3 bucket in the chosen region. Bucket names are globally unique across all AWS accounts, so pick something account-prefixed; default ACL is private.

What inputs does Create Bucket require?

Required: Bucket Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if AWS S3 returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Bucket support batch operations?

Yes. Run Create Bucket inside a Loop node to process arrays. Tiny Command handles AWS S3's rate limits automatically so you don't have to throttle manually.

More actions