Portal Community
Flow Studio

Sample Workflow Walkthrough

A complete, real, end-to-end workflow built step by step in Flow Studio — from an empty project to a running pipeline that fetches live product data, cleans it up, branches on a business rule, and reports a summary. Every field name and screenshot on these pages comes from an actual build and test run, not a mockup.

What You'll Build A workflow that calls the public dummyjson.com products API, keeps only well-stocked items, standardizes the raw API fields into a clean shape, loops over each product, and routes high-discount products to one action and everything else to another — finishing with a one-time summary once the loop completes.

The Pipeline

Manual Trigger HTTP Request Collection Operation (Filter) Data Mapping Loop If Condition Slack / Notion branch
Collection Operation (Count) Memory Store (parallel branch, feeds the Loop's exit summary)
Loop finishes SMTP Send Email — run summary

Why This Sample

Rather than a toy example, this walkthrough uses real product data from a live API and every field name is taken directly from the actual node configuration forms — not simplified or renamed for the guide. That includes a few genuine surprises encountered while building it, which are called out explicitly on the relevant pages rather than smoothed over.

Live Data

Fetches real product records from dummyjson.com — nothing pre-canned.

Data Cleansing

Data Mapping renames, transforms, and derives fields — with a real gotcha about fields that get silently dropped.

Business Rule Branching

An If Condition inside a Loop routes each product based on its discount percentage.

Run Summary

A Memory Store + SMTP Email combination reports a count once the loop finishes — not per item.

Sample Data Used Throughout

Every page in this guide traces the same two products through the pipeline:

idtitlepricediscountPercentagestock
1Essence Mascara Lash Princess9.9910.4899
2Eyeshadow Palette with Mirror19.9918.1934
Ai Studio projects dashboard
The Ai Studio "Projects" dashboard — the starting point for this whole walkthrough.
Real Discrepancies Called Out, Not Hidden While building and testing this workflow, a few things came up that didn't match the original plan — a filter threshold that was tuned differently than first documented, a branch that ended up going to a Notion page instead of WhatsApp, and an open question about which Loop output port really fires when. Each is flagged explicitly on its page rather than quietly corrected out of the guide.
Next: Create the Workflow →