> 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-xsiam/insights-and-tips-cortex-xsiam/automation-and-integrations/playbook-capabilities.md).

# Playbook capabilities

Build Cortex XSIAM playbooks with visual tasks, custom code, flow controls, error handling, and execution tracking.

Playbooks automate response workflows. Build them in a visual drag-and-drop editor, and add custom code where you need it.

### Build playbooks

* **Visual editor:** Drag tasks from the task library and connect them. No code is required for most workflows.
* **Custom code:** Write scripts in Python, PowerShell, or JavaScript, and call them from tasks.
* **Prebuilt content:** Install playbooks and integrations from the Marketplace, including common response playbooks for phishing, malware, and identity compromise, then customize them.
*

### Task types and flow control

### Error handling

### Track execution

The **Work Plan** shows each task's status, inputs, and outputs in real time. The War Room records commands and playbook tasks for each issue.

{% hint style="info" %}
How long it takes to build and test a playbook depends mostly on its integrations and approvals: API credentials, permissions, and organizational sign-off. Start from a Marketplace playbook and test it in the playground.
{% endhint %}


---

# 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-xsiam/insights-and-tips-cortex-xsiam/automation-and-integrations/playbook-capabilities.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.
