> 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-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/lists/transform-a-list-into-an-array.md).

# Transform a list into an array

Create a transformer to split a list into an array, add or edit a task in a playbook, or map an instance.

1. Go to Investigation & Response → Automation → Playbooks and create or edit a playbook.
2. Select Create Task.
3. In the Choose script field, select the Set automation.
4. In the Key field, enter the key name.
5. In the value field, click {}
6. Add a transformer.
   1. Click Filters And Transformers.
   2. In the Get field, click {}.
   3. Expand the Lists node and select a list to transform.
   4. In Apply transformers on the field, click Add transformer.
   5. Search for and select Split.
   6. (Optional) In the delimiter field, type the delimiter used to separate the items in the string (default is ",").
   7. Click Save.
7. Save the task and playbook.


---

# 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-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/lists/transform-a-list-into-an-array.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.