Today we're shipping Ironflow — a visual, node-based logic builder that lets marketing and ops teams design sophisticated feed transformations without filing engineering tickets.
The problem Ironflow solves
Feed mapping has always been stuck between two bad options. Either you write spreadsheet rules that break the second your data shape changes, or you ship the work to engineering and wait two weeks for a script. Neither scales when your team runs dozens of channels across multiple markets.
How it works
Ironflow models every transformation as a graph. You drag source nodes (a Shopify field, a price, an image URL), connect them through transformation nodes (regex, lookup table, conditional, AI rewrite), and route the result into channel-specific output nodes.
- Live preview against real catalog rows as you build
- Version history with one-click rollback
- Reusable sub-flows — define a "title formula" once, apply it to every channel
- Built-in validators so a broken node never ships a broken feed
Why visual matters
A graph is the right abstraction because feed logic is a graph. Hiding it behind nested IF statements in a sheet or a wall of Python obscures what the pipeline actually does. With Ironflow, the shape of the data flow is the documentation.
What's next
We're rolling out community templates for the most common channel mappings — Google Shopping, Meta Catalog, TikTok Shop, Amazon — so new teams can start from a working baseline instead of an empty canvas. Expect those in the coming weeks.
Ironflow ships to all IRONFEED accounts today. See it in action or start a free trial to build your first flow.