---
title: "What is a playbook?"
description: "TL;DR: A playbook is Ballet's core unit of automation — an ordered set of steps that run deterministically with visible progress. Playbooks can call code, HTTP APIs, AI agents, and connected tools. You run them manually, on a schedule, or via webhooks."
canonical_url: "https://docs.ballet.dev/articles/what-is-a-playbook-3lHOpTgJUy"
md_url: "https://docs.ballet.dev/articles/what-is-a-playbook-3lHOpTgJUy.md"
---
# What is a playbook?

**TL;DR:** A playbook is Ballet's core unit of automation — an ordered set of steps that run deterministically with visible progress. Playbooks can call code, HTTP APIs, AI agents, and connected tools. You run them manually, on a schedule, or via webhooks.

## Who this is for

All Ballet users. Builders create playbooks; Members run them.

## What does a playbook contain?

A playbook includes:

- **Steps** — individual units of work (Code or HTTP).
- **Triggers** — what starts a run (Manual, Schedule, or Webhook).
- **Inputs** — values the runner provides when starting a run.
- **Connections** — connectors and secrets the steps use.

## How is a playbook different from a chat?

A chat is a one-off conversation. A playbook is **repeatable** — the same steps run the same way every time, with logs, history, and shareable outputs.

## Where do playbooks live?

Playbooks are organized in **Collections** — folders that can optionally sync to Git for version control.

## How do I create one?

- Use **Ask Ballet** on Home to plan and build a playbook from a description.
- Create one manually from Collections or the command palette (⌘K).
- Open an existing playbook and edit steps in the **Code** tab.

## Related articles

- [How do I build a playbook with the Console?](/articles/how-do-i-build-a-playbook-with-the-console-ask-ballet-oHptRP9mI4)
- [How do I run a playbook?](/articles/how-do-i-run-a-playbook-dChtouCzok)
- [How do Collections and Git sync work?](/articles/how-do-collections-and-git-sync-work-xHKiq1WpQR)