Core Concepts

Workflow

A named automation process composed of a directed graph of activities. Workflows are versioned. Each version holds the graph definition.

Draft

An unpublished workflow version. Users can continue editing and saving drafts. Multiple drafts may exist, but only the latest is editable. Drafts cannot be executed by triggers.

Version

A numbered snapshot of a workflow's graph definition. Each save creates a new version with an auto-incrementing number. All versions are retained for audit.

Release (Publishing)

Publishing promotes the latest draft to a published version. Only one version per workflow can be published at any time. Published versions are immutable.

Environment

Deployment stages for workflow promotion (Development, Staging, Production). Achieved by deploying separate hub instances or by runner labeling.

Execution

A single run of a published workflow version on a specific runner. Statuses: QUEUED, ASSIGNED, RUNNING, COMPLETED, FAILED, STOPPED.

Trigger

Defines how a workflow execution is initiated: Manual (user/API), Schedule (cron expression), or Webhook (external HTTP POST).

Runner

A registered execution agent. Statuses: ONLINE (available), BUSY (executing), OFFLINE (no heartbeat for 120 seconds).

Execution Modes

Runners can execute workflows interactively (user clicks Run in Studio) or in the background via scheduled triggers, webhooks, or API calls. The license enforces a total runner limit for the organization.