Email attachments are now part of the workflow
Email-started workflows can now use incoming files as Flow documents. Customer apps using Flow sign-in can access the company directory, the AI assistant can publish local ZIP packages more easily, and email deliveries retry safely with updated connection details.
Workflows started by email now receive incoming attachments as usable Flow documents, not just filenames. Accepted PDFs, images, and other files are saved to Documents before the workflow begins; later steps can open or download the document and continue according to whether each attachment was saved. A storage, quota, or size problem with one attachment no longer prevents the email from starting the workflow.
Customer apps that use Flow sign-in can now list people in the same company by name, username, and department. This makes it possible to build person selection and assignment experiences inside the app without sharing sensitive details such as email addresses or roles. The AI assistant can also take a ZIP package prepared on your computer and move it to a separate publishing approval, so large file contents no longer need to be passed through the chat.
Email delivery reliability has also improved. If a mail profile changes while a delivery is still in progress, the next attempt uses the latest connection details instead of remaining stuck on old ones.
In this release
- NewEmail attachments are saved to Documents before the workflow starts and can be used by later steps
- NewCustomer apps using Flow sign-in can list people in the same company from a privacy-conscious directory
- NewThe AI assistant can take a ZIP package from your computer into publishing without moving large file contents through chat
- FixedRetried email deliveries now use the latest connection details from an updated mail profile