> 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-developer-guide/cortex-xsiam-development-guide/playbooks.md).

# Playbooks

Playbooks are a series of tasks, conditions, scripts, conditions, commands, and loops that run in a predefined flow to save time and improve efficiency and results of the investigation and response process.

Playbooks enable you to automate complex workflows in Cortex XSIAM without requiring complicated coding, and they are created and edited directly in the UI via the Playbook Editor. For more information, see [Playbooks](/cortex-xsiam/learn-about-cortex-xsiam/readme.md).

After the playbook is complete, it can be downloaded and added to a content pack for submission.

Playbooks can be triggered by:

* Alerts

  Playbooks can run on incoming alerts automatically per alert type. Consider whether you need to create a new alert type as part of your content pack.

  You can add a playbook trigger to run a specific playbook for an alert with specific characteristics. For example, you can set a condition for a specific playbook to run based on the alert source, severity, or MITRE TTP. For more information, see Playbook triggers.
* Indicator queries

  TIM playbooks can run based on indicator queries. Determine what indicator query (for example, all IP indicators retrieved from a particular feed) should be used.
* Sub-playbooks

  A parent playbook can invoke a sub-playbook. If you use sub-playbooks, consider what inputs and outputs your playbook should support and determine the default values. See the Cortex XSIAM **Playbook Design Guide** for more details.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/playbooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.