Workflows

A Workflow is a directed acyclic graph (DAG) of nodes connected by edges. When a trigger fires, EzFlow executes the graph in order and records the result as a Job.

Anatomy of a Workflow

Every Workflow has three building blocks:

• Trigger node — the entry point. Exactly one trigger starts each run. See Triggers.
• Action and logic nodes — the steps that do the work: send a message, call an API, transform data, evaluate a condition, and so on. See Nodes.
• Connections — directed edges that carry data from one node's output handle to the next node's input handle. See Connections.

Where Workflows live

Workflows are created and edited at My Workflows (app route /my-maps). Each Workflow belongs to a Business Unit and lives on a branch managed by the versioning system.

Lifecycle

1. Build — drag and connect nodes on the visual canvas. See the Quickstart for a step-by-step walkthrough.
2. Commit — save your changes to the active branch. The committed DAG is what the engine runs.
3. Run — a trigger fires (or you click Run manually) and the engine executes the graph. Each execution creates a Job.
4. Inspect — open Executions & Jobs to see the per-node result, timing, and payloads.

The DAG for each Workflow is stored per branch. You can edit a Workflow on a feature branch without affecting the version running in production. See Versioning.

Related

• Nodes — what each step can do
• Connections — how data flows between nodes
• Triggers — what starts a run
• Executions & Jobs — what a run produces
• Versioning — branches, commits, and pull requests