Skip to main content

Building blocks

  • Input Node β€” Named entry ports.
  • Processing Nodes β€” Actions/Agents/Flows.
  • Output Node β€” Named exit ports.
  • Edges β€” Data/control movement between Nodes.

Patterns

  • Linear β€” Input β†’ Action β†’ Output.
  • Branching β€” Route by condition into multiple paths.
  • Parallel β€” Fan‑out work; aggregate results downstream.
  • Iterative β€” Loop over collections or conditional repetition using nested loop structures.

Enhanced Flow System

Recent improvements to the Flow system include:
  • Better validation β€” Enhanced graph validation catches structural errors early
  • Loop support β€” Native support for nested flow structures with iteration
  • Improved schema handling β€” Better validation logic for complex data flows
  • Build/edit operations β€” Expanded flow interface allows iterative development

Practices

  • Keep Flows legible top down.
  • Favor shallow graphs; compose via sub‑Flows for depth.
  • Remove unused ports and edges to reduce confusion.
  • Use loops for batch processing and iterative operations.
  • Validate flow structure early to catch connection issues.
tip: Design for testing β€” Save example Payloads at the Flow level to lock in expected shapes and make regression checks easy.