Naming and structure
Use clear, descriptive names for workflows and tasks so you and your team can understand them at a glance. Organize complex workflows with conditions and parallel branches instead of one long linear chain where possible.
Test before going live
Use manual runs to test your workflow before enabling API, webhook, scheduled, or form triggers. Fix any validation errors (red icons on nodes) before publishing. See Workflow Node Rules and Validation for what the system checks.
Use references for dynamic data
Map trigger and previous-task outputs into later steps using Input Mapping and Workflow References ($trigger.* and $task.*.outputs.*) instead of hard-coding values. This keeps workflows flexible and correct when input changes.
Versioning workflow
Edit and test in a draft version, then publish when ready. Runtime triggers (API, webhook, scheduled, form, workflow) always run the published version. See Workflow Versioning and Publishing for details.