Knowledge Base

Workflow Lifecycle

Every Nodlyn workflow moves through a controlled lifecycle before it can run in production. This keeps untested graphs off live triggers and gives teams a clear audit trail of who approved what.

States

  • Draft — editable in Studio; not executed by triggers or schedules.
  • Validated — graph passes structural checks (missing settings, unreachable nodes, dangerous actions flagged).
  • Approved — an Engineer or Admin signed off; ready for activation.
  • Active — triggers, schedules, and webhooks fire this version.

When to use

Use lifecycle gates whenever multiple people touch the same workflow, or when a mistake could affect production devices, APIs, or data.

Typical flow

  1. Build and test in Draft with Dry Run.
  2. Run Validate from the toolbar to catch configuration errors.
  3. Submit for Approve if your org requires sign-off.
  4. Activate to enable triggers and schedules in the Jobs panel.

See also

Nodlyn Assistant
Ask me anything about Nodlyn
Hi! 👋 I'm the Nodlyn assistant. Ask me about the product, workflow components, connectors, agent runtime, agent capabilities, deployment, and more. If I don't know an answer, I'll point you to our contact form.