Playbooks

Build and run Playbooks with natural-language instructions

Playbooks let you describe work as natural-language instructions, attach context like a Brand Kit, and run the process end to end while keeping reviewers in the loop.

A Playbook is made of:

• A doc-style Playbook that describes what the agent should do.

• Inputs that the Playbook accepts at run time, such as text, numbers, files, or a Brand Kit.

• Sections that contain instructions, tool calls, and Human Review checkpoints.

• Tools that the agent can use, including SEO Research, Web Research, Image and Video, MCP Connectors, and more.

• Artifacts that the Playbook produces, such as Markdown, HTML, JSON, CSV, PNG, JPG, or GIF files.

• Triggers that determine how a Playbook starts, including Schedule, Webhook, Monitor, and AEO Insight when enabled.

Key concepts

Term	Definition
Playbook	The agent definition with Inputs, Sections, Tools, Artifacts, and a Trigger. Running a Playbook produces a Session.
Section	A unit of work in a Playbook. Each Section can include instructions, tool calls, and a Human Review block.
Input	Information you provide when a Playbook runs, such as a keyword, target URL, file upload, or Brand Kit.
Tool	An action the agent can take, from web search and SEO research to MCP Connectors like Slack, Notion, and GitHub.
Artifact	A persistent output the Playbook produces, such as a blog post, image, analysis, or structured data.
Trigger	A condition that starts a Playbook automatically. Trigger types include Schedule, Webhook, Monitor, and AEO Insight when enabled.
Session	A single Playbook run. Each Session produces Artifacts and logs the work the agent performed.
Inbox	The workspace-level queue where reviewers see pending Human Review steps and Session outputs that need attention.
Run History	The record of every Session a Playbook has produced.
Human Review	A pause point where a person must approve or edit the agent's work before it continues.
Quill	The AirOps agent captain that helps you build and edit Playbooks from natural-language prompts. See Quill.
Memory	Persistence across Sessions, used when a Playbook needs to remember what it has already surfaced or completed.

The two context sources that drive quality

Before you build a Playbook, make sure AirOps Insights and your Brand Kit are current. These two context sources shape the quality of every Session.

Configure AirOps Insights

AirOps Insights is the source for AI search visibility data, including tracked prompts, LLM search responses, citations, competitor presence, and content opportunities. When a Playbook researches AEO opportunities or LLM search responses, it should use the data tracked in AirOps Insights rather than treating AI search as generic web research.

Cover the topics, personas, regions, and funnel stages you care about. Expand coverage from sources like Google Search Console queries, sales-call language, support tickets, and competitor citation gaps.

The common pattern is: AirOps Insights tracks prompts and LLM search responses, a Playbook monitors that data and finds opportunities, then a second Playbook takes action and creates or refreshes the output.

Keep your Brand Kit fresh

Every Playbook can inherit your Brand Kit, so changes to voice, writing rules, audiences, regions, product lines, visual guidelines, and competitor context flow into Playbook output. A stale Brand Kit degrades downstream output.

Audit the Brand Kit on a recurring cadence. Refresh it when you launch a product, change positioning, add a new audience, or expand into a new region.

Use Brand Kit Refresh to monitor live sources and propose Brand Kit edits for human approval.

Use the new Brand Kit format with Playbooks. Legacy Brand Kits do not work as well with Playbooks and can reduce output quality.

Anatomy of a Playbook

When you open the Playbook editor, you will see:

• A header chip row above the first Section showing Tools, Inputs, Artifacts, and Add Trigger.

• Top-right actions for Run Playbook, Publish, and Run History.

• Quill, the AirOps agent captain, as a green floating button in the bottom-right of the editor.

• Reference pills inline as you write. Inputs and Brand Kits appear as green pills. Tools appear as gray pills with icons.

Type / in any Section to open the slash menu. The slash menu surfaces Tools, Inputs, Artifacts, and other references you can insert into your instructions.

Next steps

• Create a Playbook

• Build a Playbook

• Tools

• Run a Playbook

• Playbook Triggers

• Connect Playbooks to other tools

• Apply Playbook best practices

• Troubleshoot Playbooks