> 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/detect-investigate-and-respond-to-threats/extended-threat-intelligence/using-xti-in-playbooks.md).

# Using XTI in playbooks

Automate XTI indicator triage, enrichment, and response with supported playbook commands in Cortex AgentiX.

Extended Threat Intelligence (XTI) utilizes existing Threat Intel Management (TIM) to automate triage, enrichment, and response for threat intel use cases.

## Playbook commands supported by XTI

The following built-in commands (also referred to as system commands) can be used with XTI.

The supported commands are:

* *createNewIndicator:* Create an indicator (IP, domain, file hash, or URL).

{% hint style="info" %}
The *createNewIndicator* command is only supported with indicator *type=IP|Domain|File|URL*.
{% endhint %}

* *setIndicator:* Update an indicator (IP, domain, file hash, or URL).

**Related links**

For more information on specific built-in commands, see the in-product Script Helper available from Incident **Response → Automation → Scripts → Script Helper**.

For general information about playbooks, see [Playbooks](/cortex-agentix/configure-cortex-agentix/automations/playbooks.md).

<br>


---

# 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-agentix/detect-investigate-and-respond-to-threats/extended-threat-intelligence/using-xti-in-playbooks.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.