> 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-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/develop-your-playbook/task-4.-add-custom-playbook-features.md).
# Task 4. Add custom playbook features
Customizing a playbook helps you automate tasks to match your needs, making workflows more efficient, accurate, and easier to integrate with your existing processes.
You can customize your playbook to do the following.
| Custom action | Description |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Customize the SOC name](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/customize-the-soc-name.md) | Customize the name of the SOC that appears in the survey header. |
| [Add a sub-playbook](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/configure-a-sub-playbook.md) | Playbooks can be divided into two categories, depending on their use.
- Parent playbooks are playbooks that run as the main playbook of an incident. For example, Phishing - Generic v3.
- Sub-playbooks are playbooks that are nested under other playbooks. They appear as tasks in the parent playbook flow and are indicated by the sub-playbook icon. A sub-playbook can also be a parent playbook in a different use case. For example, IP Enrichment - Generic v2.
|
| Field mapping | You can map output from a playbook task directly to an incident field. This means that the value for an output key populates the specified field per incident. This is a good alternative to using a task with a set incident command.
You can map when you select a script in a Standard or Conditional task. For more information, see Create a standard task.
|
| [Filter and transform data](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/filter-and-transform-data.md) | Filters extract relevant data to help focus on relevant information and discard irrelevant or unnecessary data.
Transformers take one value and transform or render it to another value or format.
|
| [Use scripts](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/scripts.md) | Perform specific automated actions using commands that are also used in playbook tasks and in the War Room.
Configure script error handling.
|
| [Extract indicators](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/extract-indicators.md) | Extract indicators from incident fields and enrich them using commands and scripts defined for the indicator type. |
| [Extend context](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/extend-context.md) | Save additional data from the raw response of commands that return data. |
| [Set and update incident fields](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/set-and-update-incident-fields.md) | Use the **setIncident** script in a playbook task to set and update incident fields. |
| [Use playbook polling](/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/customize-your-playbook/playbook-polling.md) | Configure a playbook to stop and wait for a process to complete on a third-party product, and continue when it is done. |
---
# 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-xsoar-8-on-prem/8.7/configure-cortex-xsoar/playbooks/develop-your-playbook/task-4.-add-custom-playbook-features.md?ask=&goal=
```
`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.