Before
A reviewer saved supplier attachments, moved files between storage and analysis locations, and requested assessment manually. They also had to send the assessment email and track the resulting handoffs for each attachment.
How it works
- Receive a supplier email and iterate through every attachment.
- Store each attachment in binary and encoded forms, then pass its references to the document assessment workflow.
- Send the configured assessment email and retain the storage and delivery receipts for traceability.
Workflow details
- Trigger: The workflow starts when an email containing supplier evidence attachments is received.
- Attachment processing: It iterates through each attachment, retaining the filename and checksum while generating separate binary and encoded storage references. In this demonstration, the storage operations use simulated responses.
- Document assessment: Each stored artifact is passed to the supplier document assessment workflow, which receives both the raw and encoded evidence references for analysis.
- Notification and traceability: After the assessment handoff, the flow sends the configured assessment email and preserves storage and email delivery receipts for each attachment. The demonstrated connector responses are simulated rather than live external writes.
What changed
Each attachment is processed through the same storage, assessment, and notification sequence automatically, with its own evidence and delivery references. The human no longer needs to coordinate the handoff between storage, document analysis, and email delivery.
Work removed
Saving attachments manually, moving files between storage and analysis, requesting document assessment, sending the assessment email, and tracking storage and delivery receipts for each attachment.
Expected outcome
For each attachment, the workflow is designed to produce one traceable storage handoff, one assessment handoff, and one email-delivery receipt, replacing at least three recurring manual coordination actions.
