Supplier inbox triage
Northline Supply's service coordinator needs a testable triage flow for supplier requests.
The fictional event supplies from, reference, department and lines. Produce one receipt to the sender, one desk route, one open-line summary and one audit email. Keep unknown departments for manual review; empty line arrays have a count of zero.
Northline Supply needs an inbox routine that acknowledges a supplier, routes the request and gives operations an open-line count. Build it in small increments. Each step keeps your previous cards, so a later edit must preserve the effects already agreed with the service desk.
The two supplied event shapes differ in sender, reference, department and line count. One has an unknown department and no open lines. That case must still receive a receipt and a manual-review owner. A final audit message identifies the same event without exposing the entire payload. Use the action ids shown in your designer when referencing earlier outputs. The finished flow should be readable in Run history: a coordinator can trace the acknowledgement, route and count without interpreting an unlabelled block of expressions.
Cloud flow: Supplier inbox triage
Trigger: When a new email arrives (V3)
from:
subjectFilter:
Send an email (V2) [receipt]
To: @triggerBody()?['from']
Subject: Received
Body: @triggerBody()?['reference']
The receipt follows the current sender and reference.