Building Network Workflows Visually: Chain Templates Into Repeatable Automation

A single template checks one thing. Real operations are sequences: back up the config, push the change, verify reachability, and roll back if anything fails. The Workflow Builder is where you assemble those steps into one named, repeatable flow you can run on demand or on a schedule.

The canvas model

A workflow is a graph of nodes connected by edges. Each node is either a template step or a control node, and each edge defines order — what runs after what. You build it visually: search the template sidebar, click to add a node, then drag between nodes to wire the sequence.

• Template nodes — a step that runs a catalog template with its parameters.
• Branch nodes — a conditional path, typically taken on failure of a prior step.
• Parallel groups — steps that run together instead of one after another.

Build it in four moves

1. Search the sidebar and click templates to drop them onto the canvas.
2. Drag from one node to the next to connect them in order.
3. Add a branch for on-failure handling, or a parallel group for fan-out steps.
4. Name the workflow, set an optional cron schedule, and save.

Run, inspect, and schedule

Save first, then run — the builder streams back per-step results with status, duration, and a short log for each node, so you can see exactly which step passed, failed, or was skipped. Once a flow is trustworthy, give it a cron expression and let it run unattended.