Hi all,
I recently set up an SMTP connector process action to send emails with attachments stored in an AWS S3 file storage location, and collected the full set of file storage status codes along the way (-6, -7 and -8), so I feel qualified to ask this question now. 🙂
What I learned:
- **-6**: the storage location wasn't linked to the process action yet. Fixed.
- **-7**: *Storage attachment path* must be the full absolute path *including* the storage location root (e.g. `https://bucket.s3.eu-central-1.amazonaws.com/2026/06/file.jpg`) — even though the storage location is already selected on the process action itself. A relative path within the storage location is rejected. Slightly surprising, and not great for maintainability if the storage location ever changes, but okay.
- **-8**: this is where I'm stuck. I tried semicolon-separated paths to attach multiple files, the way *Disk file attachments* works. The connector treats the whole string as a single (non-existent) file path. The documentation confirms *Storage attachment path* accepts exactly one path.
Â
So my question: **what is the intended way to send a single email with multiple attachments from a file storage location?**
Â
Workarounds I'm aware of:
1. Zip the files first with the Zip file action and attach the single zip — functional, but the recipient gets a zip instead of the individual documents.
2. Per file: Read file (from S3) → Write disk file to a temp location → SMTP connector *without* a storage location, using *Disk file deletable attachments* with a semicolon-separated list. This works but round-trips every file through local disk, which somewhat defeats the purpose of the file storage integration.
Â
If there's no direct way, I'd like to turn this into a feature request: support a semicolon-separated list in *Storage attachment path*, consistent with *Disk file attachments*. Bonus points for also accepting paths relative to the selected storage location.
Â
Current platform version: 2025.3
Â
Thanks!
