> 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-xsiam/configure-cortex-xsiam/automations/context-data/add-context-data-to-a-case.md).
# Add context data to a case
Add keys and values to Cortex XSIAM case context data.
You can add keys and values to a case's context data to be used in playbooks or other automations. By default, context data is added to cases only. To run automations on a case, add context data to the case from its related issues.
To add context data to a case, run the `setParentIncidentContext` command in the CLI, in a script, or in a playbook task.
Use the CLI
Run the `!setParentIncidentContext` command in the issue **War Room** or the **Case War Room**.
{% hint style="info" %}
If you run the command in the issue **War Room**, the data is added to the following places:
* The case context data.
* The issue context data under the case tab.
If you run the command in the **Case War Room**, the data is added to the case context data only.
{% endhint %}
Run the command in the issue War Room
1. Open an issue and select the **War Room** tab.
2. Run the `!setParentIncidentContext` command.
The following example adds the key and value `hello:world` to the case and issue context data.
```programlisting
!setParentIncidentContext key="hello" value="world"
```
Run the command in the case War Room
1. Open a case and switch to the **Detailed view**.
2. Select the **Case War Room** tab.
3. Run the `!setParentIncidentContext` command.
The following example adds the key and value `hello:world` to the case context data.
```programlisting
!setParentIncidentContext key="hello" value="world"
```
Use a script
In any script that runs in an issue, the data is written to the issue context data. If you want to add the data to the case context from your script, run the `setParentIncidentContext` using the `demisto.executeCommand` key, as follows:
`demisto.executeCommand("setParentIncidentContext", {"key":"", "value":""})`
The following example creates a new key name `AuditID` with a `90210` value to your script.
```programlisting
demisto.executeCommand("setParentIncidentContext", {"key":"AuditID", "value":"90210"})
```
Use a playbook
When a playbook runs, the playbook data is written to the issue context data. To write the data to the parent case context data, use the `setParentIncidentContext` script in a standard task.
The following example adds the TicketID to the case context. To see a full use case that includes this standard task, see [Use context data in a playbook](#UUID-050987be-fc55-bed7-3671-8170a9a2e58c).
---
# 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-xsiam/configure-cortex-xsiam/automations/context-data/add-context-data-to-a-case.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.