Sending FormLister Uploads as Links Instead of Heavy Email Attachments

Large or mixed-format attachments can make a form workflow heavier than it needs to be. The donor topic showed a practical alternative for FormLister: accept uploaded files, save them to a temporary folder, and send the recipient a link instead of embedding the file directly into the email.

Why this pattern is useful

• Email delivery becomes more reliable when the message is lighter.
• You can control file naming and storage before sending anything onward.
• Recipients still get access to the uploaded material without turning every form into an attachment-heavy mail job.

Typical flow

&attachments=`ufile`
&prepareAfterProcess=`prepareUpload`

Then in the post-processing hook, move the uploaded file into a known temporary directory, normalize the filename, and expose its path to the report template as a link.

This is a strong pattern for project forms, support requests, and tender-like workflows where uploaded files matter, but mailbox stability matters too.