Workflow spec - e6data Docs

The full field-by-field schema is being written. This page lists the rules that apply today.

The document

A workflow is a versioned JSON document stored in your durable storage.
Each version records its author and carries a compiler version.
A version must compile with the runtime compiler to be saved, whether it’s created in chat or edited in the visual builder.
One version is marked current; any version can be selected for a run.

Steps

A workflow is a graph of typed steps. See Step types for the ten types, what each step can declare, and the legacy fields that are rejected.

Inputs

Input definition	At run time
Has a non-null default	Prefilled and optional
`required: false`	Optional
A bare type, no default, or a `null` default	Mandatory

References between steps

Large intermediate results travel as FileRef, S3PathRef or ArtifactRef instead of being inlined in every step’s context.

Actions

A terminal action step takes a static directive or the Slack directive source, and approval: false, approval: true or an approval-policy ID. See Actions and approvals.

Last modified on October 1, 2026