Create a Playbook

Start a Playbook from scratch, from a Workflow, or from a template

You can start a Playbook from a blank Playbook, an existing Workflow, or a template.

Build from scratch

Use a blank Playbook for net-new use cases or when no existing Workflow is close to what you need.

1. Click Create.

2. Select Playbook.

3. Select Blank Playbook.

4. Name the Playbook in the editor.

5. Add Inputs, Sections, Tools, Artifacts, and any Triggers the Playbook needs.

6. Run a test Session before publishing.

Replicate a Workflow as a Playbook

Use Replicate as Playbook when you have an existing Workflow and want a Playbook with similar structure.

1. Open the Workflow editor.

2. Open the dropdown next to Publish.

3. Select Replicate as Playbook.

4. Review the draft Playbook that AirOps creates.

QA the converted Playbook before publishing. The converter handles instructions and Inputs, but Tools such as web scrape or Google Search may not always populate. Add missing Tools with the slash menu, and confirm the Brand Kit Input uses the Brand Kit type.

Install a template

Use templates when you want a working reference you can run, study, or fork. AirOps shows the published Playbook templates available to your workspace.

1. Click Create.

2. Select Playbook.

3. Select From Template.

4. Choose a template.

5. Complete any template-specific setup.

The template list can include content creation, content refresh, monitoring, and Brand Kit Refresh templates. If you select Brand Kit Refresh, AirOps asks you to choose an eligible Brand Kit and creates a refresh Playbook for that Brand Kit.

Templates are useful as implementation examples even when you plan to build a custom Playbook.

Conversion checklist

When you convert an existing Workflow to a Playbook:

• Run Replicate as Playbook from the Workflow editor's Publish dropdown.

• Confirm the Brand Kit Input type is Brand Kit, not Text.

• Confirm you are using the new Brand Kit format.

• Confirm the Prompt coverage is complete for the use case.

• Add any Tools that did not carry through the conversion.

• Reference each Knowledge Base by name in every Knowledge Base search step.

• Reference Artifacts by name in downstream Sections.

• Add Human Review blocks at logical checkpoints.

• Configure the Trigger, if the Playbook should run automatically.

• Run a test Session and review every Artifact.

• Verify connected destinations like Slack, CMS tools, or Grids.