Docs
Reference

Step Reference

Quick Answer

Use this page as the step hub: compare step families here, then jump to the
detailed step page you need. For the broader docs map, use
Reference Index. For the full CLI surface, use
CLI Commands.

Built-in step families use unqualified keywords like :http and :files.
Flow-local packaged steps defined under top-level :steps use qualified
keywords like :github/open-pr and are invoked through the same flow/step
surface. Flow-local agent definitions under top-level :agents use qualified
keywords like :review/security and are also invoked through flow/step.

Step Families At A Glance

Step typeCore fieldsNotes
:http:connection or :url, :path, :method, :query, :headers, :json, :body, :response-as, :client-opts, :persist, :auto-search-index?, :retryLarge and binary bodies should use :persist; safe page GETs can be auto-indexed for workspace search.
:llm:connection, :model, :messages or :prompt, :template, :dataUse templates for long prompts. Multipart messages can include uploaded image resources for vision-capable models.
:agent:objective, :inputs, :connection, :tools/:available-steps, :memory, :cost, :approval, :trace, :output-persistAgent with memory, approval, tracing, and bounded tools. Expose narrow built-ins directly; wrap broad side effects in packaged :steps.
:mcp:adapter, :tool, optional :argumentsDeterministic outbound Streamable HTTP MCP tool call through a top-level :mcp adapter. Use :tools {:mcp [...]} on :llm/:agent when the model should choose the call.
:db:database, :connection, backend-specific fieldsSQL/BigQuery use :sql/:template + params; Firestore uses :collection/:where.
:wait:key, :notify, :timeoutSupports human/webhook resume patterns.
:function:code or :ref, :input, :load, :persistMap-oriented transforms; persist large or table-shaped outputs.
:job:op, plus :job-type, :job-id, or :batch-id depending on opExternal jobs control plane submit/get/await surface.
:notify:channels (:http), optional :template, :dataExternal delivery channels only.
:kv:operation, :key, operation-specific fields (:value, :ttl, :prefix)Useful for state handoff/cache patterns.
:table:op, :table, op-specific fields (:where, :sort, :group-by, :metrics, :column)Bounded table-resource query, aggregate, export, authored-column, and derived-table surface; creation happens through :persist {:type :table ...}.
:files:op, :source, op-specific fields (:query, :paths, :path-prefix, :changeset, :edit, :branch, :commit-message, :title)Source-tree read/search/edit/materialize/capture with persistent changeset-ref overlays; supports publish/change-request flows. Direct flow/step :files calls are valid in orchestration; agent tool exposure only supports the safe subset directly, and broad repo/session ops such as :resolve-source, :materialize, :capture, :heartbeat, :status, :release, :publish, and :open-change-request need packaged :steps wrappers.
:fanout:items, optional :max-concurrency, :on-error, :transformAsync only for one child-workflow mode at a time: all :call-flow items or all named :agent items. Legacy non-child items run on the sequential compatibility path.
:sleepone of :seconds, :millis, or :durationDeterministic delay boundary.
:ssh:connection, :command, :env, :workdir, :timeoutRemote exec over SSH; for agents use :ssh kickoff + :wait callback.
:search:query, optional :mode, :targets, :limit, :hydrate, storage filtersWorkspace search across :resources, :flows, :runs, and :connections; resource search defaults to hybrid retrieval and can opt into strict lexical or semantic-only retrieval.
:breyta:op, :allow, optional :args, optional :mutations, optional :require-approvalWorkspace-scoped control-plane operations for agents, including flows, runs, docs, resources, and explicitly granted mutations.

Common Step Options

OptionMeaningTypical use
:titleReadable step labelImproves timeline readability.
:timeoutStep timeout secondsBound slow external operations.
:retryRetry policyHandle transient external failures.
:on-errorError policy (:fail, :skip, :checkpoint)Control failure handling behavior.
:persistStore outputs as refsKeep large outputs out of inline payloads.
:meteringAdvisory per-step cost estimateAdd fixed API/tool costs to creator-facing run cost breakdowns.
:review / :confirmHuman checkpointsAdd explicit approval/verification points.

For packaged steps, these common options still live on the outer flow/step
wrapper. The packaged definition itself should focus on the simplified
input/output contract for the wrapped built-in step.

Detailed References

ReferenceScope
Step HTTPHTTP request/response and persistence behavior
Step LLMLLM message/prompt and tool usage
Step AgentObjective/input-oriented wrapper over the LLM tool loop
Step MCPDeterministic outbound MCP tool calls through flow-level adapters
Step BreytaNative workspace-scoped Breyta control-plane operations for agents
Step DBShared DB step concepts and backend split
Step DB SQLSQL backends (:postgres, :mysql, :clickhouse)
Step DB BigQueryBigQuery-specific DB behavior
Step DB FirestoreFirestore-specific DB behavior
Step WaitWait/signal/timeout and approval flows
Step Function:function step and deterministic transforms
Step JobJobs control plane submit/get/await step surface
Step NotifyNotification channel delivery
Step KVKV read/write/list operations
Step TableTable-resource query, aggregate, column-authoring, export, and bounded mutation operations
Step FilesSource-tree resolution plus persistent changeset-ref overlays for read/search/edit/materialize/capture/diff, then branch publish and pull-request operations over that same logical state
Step FanoutBounded child-workflow fanout and legacy compatibility behavior
Step SleepSleep timing semantics
Step SSHRemote exec and agent kickoff patterns
Step SearchWorkspace search step behavior and limits
Packaged StepsFlow-local qualified-keyword step wrappers with schema, direct invocation, and agent tool publication
Persisted Results And Resource RefsWorking with persisted refs/resources
Run Cost Estimates:metering, token pricing, and run cost breakdowns

Related

As of Jul 13, 2026