How do I go from a Grid to a Workflow?

Stale workflow versions cause downstream errors in your Grid. Editing, publishing, and managing Playbook Output Workflows correctly in AirOps Workflow Studio ensures every Grid column runs the version you intend. This tutorial covers the full publishing process and how to stay in control of your Playbook versions.

Key takeaways

  1. Publishing a Workflow creates a versioned snapshot; only published Workflows appear in the Grid column dropdown and run for all Grid executions.
  2. Drafts are not saved permanently; only the most recent draft is retained, so publish your work when it's ready.
  3. Multi-output Workflows return multiple named values from a single run, populating several Grid columns at once and reducing redundant executions.
  4. Understanding the step sequence (Inputs, Run Code, Write to Grid, Format Outputs) helps you troubleshoot and customize your output.
  5. Quick Actions give you shortcuts for common tasks including Run, Rename Version, Create Grid, Embed, and Enable Sharing.

Tutorial overview

Playbook output Workflows define exactly how your Grid processes and formats content for each row. You build these in Workflow Studio, where you control every step from input settings to final output mapping.

Each Workflow is made up of steps you can customize: Input Settings, Run Code, Write to Grid, and Format Outputs. Together, these steps determine how raw data becomes polished, ready-to-use content in your Grid columns.

Publishing a Workflow creates a permanent Default Version that your Grid references when running rows. You can keep editing a draft without affecting the published version, so your production content stays stable while you iterate. Once published, you unlock Quick Actions like running the Workflow, embedding it, renaming versions, replicating it as a Playbook, or contributing it as a Power Agent. You decide when changes go live, and your Grid always runs the version you've approved.

Practice

  1. Go from a Grid to a Workflow in AirOps

    Promote the logic in a Grid into a reusable Workflow for broader use across AirOps. Move from a Grid view into Workflow setup so your automation is available beyond bulk runs.