> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/playbooks/playbooks-overview.md).

# Playbooks overview

Learn how playbooks automate investigation and response workflows in Cortex AgentiX.

Cortex AgentiX playbooks are visual canvases that automate security response workflows. They orchestrate actions across products, manage case data, and interact with users. This provides a consistent and rapid response to security events.

### One-stop playbook development

Before you build a playbook, review your organization's playbook list on the **Playbooks** page. The **Playbook Catalog** contains available out-of-the-box playbooks that are not yet in use. You can adopt a catalog playbook or develop one from scratch. The playbook editor supports the complete development flow. You can create and edit tasks, configure automation rules, and set up integrations.

### Task Library

The **Task Library** in the playbook editor contains objects you can add to a playbook. You can create tasks from scripts, repurpose existing tasks, and use playbooks as sub-playbooks.

Playbook tasks display unique logos. These identify task type and origin, such as third-party integration commands, built-in scripts, and manual-input tasks.

| Task Library Object    | Action                                                                               | See More                                                                                                                                                                                          |
| ---------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AI Prompts**         | Add AI prompts with inputs and outputs that run automatically.                       | See [Add AI Prompt tasks](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/add-objects-from-the-task-library/add-ai-prompt-tasks.md).                           |
| **Commands & Scripts** | Add commands and scripts from installed integrations. Configure instances as needed. | See [Add commands and scripts](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/add-objects-from-the-task-library/add-commands-and-scripts.md).                 |
| **Playbooks**          | Add sub-playbooks from your Org repository or the Playbooks Catalog.                 | See [Add sub-playbooks](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/add-objects-from-the-task-library/add-sub-playbooks.md).                               |
| **Manual Tasks**       | Add tasks from playbooks in your Org repository.                                     | See [Add manual tasks and blank tasks](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks.md). |
| **Header**             | Add section headers to organize your playbook.                                       | See [Create a section header](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/create-a-section-header.md).                                                     |
| **Blank Task**         | Create a new task from scratch.                                                      | See [Add manual tasks and blank tasks](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks.md). |

### Post-development playbook testing

After developing the playbook, including its automation rules, run the debugger for initial testing.

After confirming the playbook runs correctly with issues, you can use it in production.

To see which playbook ran for an issue, go to **Cases & Issues** → **Issues**. Scroll to the **Playbook** column. Select an issue, then select the **Work Plan** tab to view or change its playbook.

To see whether a playbook ran in a case, go to **Cases & Issues** → **Cases**. Check the **Automation** section of the case **Overview** tab. To view or change the playbook, select an issue in **Issues & Insights**, then select **Work Plan**.

For more information, see [Analyze and resolve cases](/cortex-agentix/detect-investigate-and-respond-to-threats/investigation-and-response/analyze-and-resolve-cases.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/playbooks/playbooks-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.