Visualize your workflow on the canvas: each node represents a step that executes in order, branches with conditions, or pauses for delays. When you save, the definition persists so teammates can audit how automation behaves.

Every run records success, running, and error states per step. Use the run logs to inspect inputs, outputs, API responses, and any alerts that happened along the way.

Visibility & collaboration

Share workflows by linking them to dashboards, embed run history in docs, or duplicate definitions for testing. Assign owners and comment on runs to keep everyone aligned on the automation lifecycle.

Disable a step to temporarily skip it without deleting it entirely, then re-enable when the flow is ready. Each change keeps the run history intact so you can compare behavior before and after updates.

When you're ready to dive deeper, learn how triggers kick off workflows and how action types move data between systems.

Next up: triggers