Scalable storage in the cloud
Amazon S3 currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New or Updated File
Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.
Upload File
Upload an File to S3
Read File
Read a file from S3 to use it in other steps
Generate signed URL
Generate a signed URL for a file in a s3 bucket
Move File
Move a File to Another Folder
Delete File
Deletes an existing file.
List Files
List all files from an S3 bucket folder/prefix.
Decrypt PGP File
Decrypt a PGP encrypted file from S3 using a private key stored in AWS Secrets Manager
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Amazon S3 event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New or Updated File
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Amazon S3 action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Upload File
Combine Amazon S3 with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New or Updated File
Finishes with
Upload File, then preserve the outcome in Coherence
The exact authentication fields depend on Amazon S3. The workflow structure stays straightforward:
Authorize the Amazon S3 account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Amazon S3 or provide a complementary trigger or action.
Amazon S3 currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Amazon S3 currently lists 1 trigger and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Amazon S3 triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
