> 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-xdr/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence/using-xti-in-playbooks.md). # Using XTI in playbooks Automate XTI indicator triage, enrichment, and response with supported playbook commands and scripts. Extended Threat Intelligence (XTI) provides built-in commands and scripts to automate triage, enrichment, and response for threat intel use cases. ## XTI playbook commands/scripts The following built-in commands and scripts can be used to investigate XTI indicators and threat objects. The supported commands and scripts are:

Category	Command/Script	Type	Description
Category	Command/Script	Type	Description
Commands
Indicator Lifecycle	createNewIndicator	Write	Create an indicator (IP, domain, file hash, or URL). Note: The createNewIndicator command is only supported with types IP\|Domain\|File\|URL.
Indicator Lifecycle	setIndicator	Write	Update an indicator (IP, domain, file hash, or URL).
Scripts
Threat Object	CortexXTIGetThreatActors	Read	List and describe threat actors.
Threat Object	CortexXTIGetMalwareFamilies	Read	List and describe malware families.
Threat Object	CortexXTIGetReports	Read	List and describe threat intel reports.
Behavioral Threat Analysis (BTA)	CortexXTIGetBTAContext	Read	Show Behavioral Threat Analysis (BTA) context.

\ For more information on specific scripts, see the in-product Script Helper available from **Investigation & Response → Automation → Scripts → Script Helper**.
**Related links** For general information about playbooks, see [Playbooks](/cortex-xdr/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/playbooks.md).
--- # 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-xdr/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence/using-xti-in-playbooks.md?ask=&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.