Step 10 · Loop Exit
Run Summary Email
Connects from the Loop node's once-only exit port — fires after every item has finished, not per item — and reports how many Slack alerts went out.
Depends on the open question from the Loop page
This node is designed to connect from whichever Loop output port genuinely fires once, after all items finish — assumed here to be the port labeled Completed on the live canvas. That assumption hasn't been verified yet (see the Loop page's callout). Confirm which port actually behaves this way before wiring this node up for real.
Configuration — SMTP Send Email
| Field | Value |
|---|---|
host | smtp.example.com |
port | 587 |
userName | [email protected] |
password | (masked placeholder) |
tls | on (default) |
fromEmail | [email protected] |
fromName | BizFirst Flow Studio |
toEmail | [email protected] |
subject | Product Discount Alert — Run Summary |
text | Workflow finished. {{memory.slackSentCount}} Slack alert(s) were sent for high-discount products. |
Example (our 2-product sample)
Subject: Product Discount Alert — Run Summary
Body: Workflow finished. 1 Slack alert(s) were sent for high-discount products.
Not yet built on the canvas
Like the Count High-Discount Items and Memory Store nodes, this hasn't been added and tested yet. Verify the exact field values above once it's wired up — and note the filter threshold discrepancy from the Filter In-Stock Items page changes what the real count would be in an actual run.
What you built
An end-to-end workflow that fetches live data from an external API, standardizes it into your own shape while preserving every original field, branches per-record on a business rule, and reports a one-time summary once the batch finishes — using nothing but the standard node set and the shared common forms every node in Flow Studio can attach.