Hi naveen,

Sending e-mail via Process flows usually happens using the SMTP connector. From there, you have two options. 

1. Disk file attachments; Optional. A list of file paths separated by semi-colons. The files will be added as an attachment to the email. Only for use without a file storage location.
2. Storage attachments path; Optional. You can add one absolute path that refers to a file in the file storage containing the email attachments.
   This parameter can only be used when a file storage location is specified in this process action's Form tab.

With option 1, it requires you to have all attachments you would like to attach, written to disk first. From there you can list all paths to the files and separating them with semi-colons (;). 

For example: \\server\folder\files\file1.pdf; \\server\folder\files\file2.pdf; \\server\folder\files\file3.pdf

With option 2, you can only add one single file. But, what you can do in the 2022.2 release is using the ZIP file process action to zip all the files you would like to send first, then thereafter attaching that ZIP-file to the e-mail. Note that it still requires all attachments to be available somewhere in storage, but to the contrary of option 1, this storage could be Azure, AWS or Google Cloud for example.

Hope this helps!