Automation Core

The vocabulary of what users build and what runs: flows, their versions, the steps inside them, and the runs they produce.

Language

Flow: A named automation consisting of a trigger and one or more action steps, stored as a versioned JSONB graph. Avoid: workflow, automation, pipeline, scenario

FlowVersion: An immutable (once locked) snapshot of a flow's trigger + action graph; DRAFT is editable, LOCKED is published. Avoid: version, revision

Draft: The editable FlowVersion state; only one draft exists per flow at a time.

Published: A LOCKED FlowVersion pointed to by flow.publishedVersionId; the version that runs in production. Avoid: live, active version

FlowOperationRequest: The discriminated union of all 26 modification types dispatched to the single flow update endpoint.

Step: Generic term for any node in a flow graph — either a trigger or an action. Avoid: node, block

Action: A single executable step within a flow that performs an operation (HTTP call, data transform, code execution, etc.). Avoid: task, command

Trigger: The entry point of a flow that initiates execution via webhook, polling, app event, or manual invocation. Avoid: event source, starter

TriggerStrategy: The mechanism a trigger uses: POLLING, WEBHOOK, APP_WEBHOOK, or MANUAL. Avoid: trigger type

TriggerSource: The external registration (webhook URL, polling job, app-event subscription) that fires a flow.

FlowRun: A single execution instance of a published flow, tracking status, logs, timing, and step results. Avoid: execution, job, run instance

FlowRunStatus: The state machine for a run: QUEUED, RUNNING, PAUSED, SUCCEEDED, FAILED, TIMEOUT, CANCELED, and others.

RunTimeline: A run's latency breakdown as legs of four phases — Queue, Provision, Boot, Run — persisted on flow_run and shown as a stacked bar in the run detail view. Avoid: latency breakdown, waterfall

TimelinePhase: One labeled segment of a RunTimeline leg: QUEUE (waiting), PROVISION (install bundle/pieces/engine), BOOT (engine fork/boot), or RUN (flow execution). Avoid: stage, span

Sample Data: Captured step input/output stored as File entities per flow version, used for testing downstream steps. Avoid: test data, mock data

Agent: A flow step type that runs an LLM-driven autonomous loop, calling tools until it produces a final answer. Avoid: AI step, bot

AgentTool: A discriminated union of the four tool types attachable to an agent step: Piece, Flow, MCP, or Knowledge Base.

Folder: A grouping container for organizing flows and tables within a project. Avoid: directory, category