Workflows vs. Runbooks

Learn how Workflows compare to Runbooks
Workflows offer the same core functionality as Runbooks, except they are expressed as native code rather than a DAG of operations. Workflows are optimized for developers which gives a number of advantages:
  • Control flow is expressed with familiar language constructs such as if statements, for loops, and branches.
  • Workflows can be managed as code. For example, you can automatically deploy them through git.
  • Workflows can make on-the-fly decisions, such as conditionally requiring approvals.
  • Workflows mirror the data model of tasks and runs, offering a familiar UX to developrs and operators.
  • Logic can be reused by splitting it into functions that can be imported from other workflows.
While workflows are designed to be developer-first, runbooks are designed to be built from the Airplane app. This is the area where runbooks shine, as they can be built from a user-friendly UI without requiring a local development environment. If that's what you are looking for, we recommend continuing to build with runbooks. A UI for building workflows is coming soon.


You can migrate existing runbooks to workflows by mapping features between the two products:
Replace Task blocks......with the Task execution SDK
Replace Built-in blocks......with Built-in SDK methods
Replace Form blocks......with Prompts
Replace Note blocks......with Markdown displays
Replace Start conditions......with native if statements