Amazon S3 · New object — When an object is added to a bucket — checks a bucket on a schedule. Each object newer than the newest it has seen starts a run.
Who can do this
Workspace Admins and Editors. Amazon S3 is a paid-plan service: you can build and test with it on any plan; publishing needs a paid plan.
Before you start
- An Amazon S3 connection in this workspace whose key may list the bucket — see Connect Amazon S3 or an S3-compatible store.
Steps
- Open the workflow in the designer and open the trigger picker — Browse all triggers, or Change how it starts on an existing trigger.
- Select New object — Amazon S3. Or type S3 in Search triggers.
- In Connection, choose your Amazon S3 connection, then the Bucket.
- Optional: Starting with —
incoming/— to watch one "folder". - Under Checks, choose Every 5 minutes or Every 15 minutes.
- Open the Output tab and select Fetch a sample. The newest object comes in, and Test run starts with it.
- Add the steps — Download a file with
{{ trigger.key }}brings the file itself — test, then Publish.
What happens next
- The first check after publishing only notes the newest object. Objects already there never start a run.
- Each new object starts one run, oldest first, with
{{ trigger.bucket }},{{ trigger.key }},{{ trigger.name }},{{ trigger.size }},{{ trigger.modifiedAt }}and{{ trigger.etag }}. - Up to 100 new objects start runs in one check; the rest wait for the next check.
- A check that finds nothing starts no run and costs nothing.
Good to know
- New means a newer modified time. Replacing an object at the same key gives it a new time, so it counts as new again.
- Up to 10,000 objects are looked at in each check; use Starting with on a large bucket.
- Runs start in Production and count in the month's allowance.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Bucket is empty. Choose one from the list. | Bucket is not chosen. | Choose it. |
| Not checking since 10:45 with Amazon S3 refused the access key or secret. … | The key stopped working. | Reconnect, then Check now. See When an app trigger stops checking. |
| Not checking with Amazon S3 now asks for an access key, secret and region. … | The connection was made with the old form. | Reconnect it. |