> 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/lists.md).

# Lists

Create and edit lists for use in playbooks and scripts.

A list is a data container for storing data and is mainly used in [playbooks](/cortex-agentix/configure-cortex-agentix/automations/playbooks/playbooks-overview.md) and [scripts](/cortex-agentix/configure-cortex-agentix/automations/scripts.md) but can be accessed anywhere the context button appears (double-curly brackets). For example, in a playbook task, access the data in a list via the context button under **Lists**, or by using the path `${lists.<list_name>}`. Different types of data can be stored in a list, for example, text, string, numbers, Markdown, HTML, CSS, and JSON objects.

{% hint style="info" %}

### Note

The maximum size of a list is 209715 characters.
{% endhint %}

**Use cases**

The following are use cases for lists:

* **Defining HTML templates**: An HTML template can be defined as part of a communication task.
* **Configuring Automation Exclusion Policies**: Create lists of critical assets that should be excluded from automated remediation. For more information, see [Manage automation exclusion policies](/cortex-agentix/configure-cortex-agentix/automations/automation-exclusion-center/manage-automation-exclusion-policies.md).
* **Organizing Network Security**: Use lists to keep track of internal networks and their corresponding IP addresses. Compare them to a set list to ensure only authorized connections are allowed through.
* **Store Data Objects**: For example, a list of URLs, which you can call as an input for scripts and playbooks.
* **Prioritizing Case Response**: Create lists to identify critical assets, such as important users or servers. This helps improve incident management by prioritizing the most important incidents.


---

# 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-agentix/configure-cortex-agentix/automations/lists.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.