AWS S3
S3 buckets as a workflow read/write target
AWS S3 on Tiny Command exposes five actions for the object-storage primitive that powers most of the modern web. Get Object retrieves an object by bucket and key (binary or text), Delete Object removes it, List Objects iterates a prefix, List Buckets enumerates the buckets your IAM role can see, and Create Bucket spins up a new one (with optional region and ACL). The integration authorizes with an AWS access key + secret pair, scoped to whatever IAM policy you assign. Tiny Command never inherits more permission than the key grants. Object content is streamed for large files; small files (<5MB) come back as base64 in the response, larger files as a presigned URL the workflow can hand to the next step. Common pattern: a Gmail trigger with attachment lands the file as binary, a Get Object call retrieves a config template from S3 that's applied to the attachment, and the result writes back to a different bucket as a processed artifact. S3 triggers (via SNS or EventBridge) are on the roadmap.
Do anything AWS S3 can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Bucket | 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. |
| Delete Object | Deletes a single object (file) from an S3 bucket by key. If versioning is enabled on the bucket, this just creates a delete marker; specify a VersionId to actually remove a version. |
| Download Object | Downloads an object (file) from an S3 bucket by key. Large objects should usually be streamed via a presigned URL rather than buffered into a workflow step. |
| List Buckets | Lists all S3 buckets in your AWS account, regardless of region. Used to populate a bucket picker or for audit/compliance reports. |
| List Objects | Lists objects in an S3 bucket, optionally scoped by prefix (folder). Returns up to 1000 keys per page; paginate with ContinuationToken for large buckets. |
Pre-built AWS S3 workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect AWS S3 once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every AWS S3 field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the AWS S3 integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect AWS S3 to Tiny Command?
What AWS S3 triggers does Tiny Command support?
What AWS S3 actions can I run from a workflow?
Is the AWS S3 integration real-time?
Do I need to write code to use AWS S3 with Tiny Command?
How much does the AWS S3 integration cost?
More cloud & storage apps people connect.
Same category as AWS S3, ordered by how often teams pair them. Hover the carousel to pause.
Do more with AWS S3.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
