Workflow Lifecycle
The full path from trigger, context, data, browser changes, output, and errors.
Flow Logic
Flow logic decides what runs next. It is separate from data mapping: mapping changes the shape of data, while flow logic changes the path a run takes through the workflow.
flowchart TD
Trigger["Trigger"] --> Step["Run node"]
Step --> Branch{"Condition?"}
Branch -->|true| TruePath["True path"]
Branch -->|false| FalsePath["False path"]
TruePath --> Merge["Merge or finish"]
FalsePath --> Merge
Merge --> Next["Next step"]
Core Ideas
Section titled “Core Ideas”Execution Order
How nodes run, how branches are selected, and why in-page actions can change later results.
Branches And Merges
Use splitting, conditions, and merging to keep workflow paths understandable.
Loops And Waiting
Repeat work over many items and wait for page or time-based conditions before continuing.
Practical Rule
Section titled “Practical Rule”Keep browser actions, flow decisions, and data transformations visually separate when possible. That makes it much easier to find whether a failure came from page timing, an incorrect condition, a missing field, or an external service.