> 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-posture-management/cases-and-issues/investigation-and-response/automation/context-data/add-context-data-to-an-issue.md).
# Add context data to an issue
Add context data to an issue.
You can add keys and values to an issue's context data to be used in playbooks or other automations.
To add context data to an issue, run the `Set` command in CLI, in a script, or in a playbook task. The Set command enables you to set a value under a specific key. For more information about the Set command, see [Set](https://xsoar.pan.dev/docs/reference/scripts/set).
Use the CLI
Run the `!Set` command in the issue **War Room**.
1. Open an issue and select the **War Room** tab.
2. Run the `!Set` command.
Example 35. Example
The following example adds the key and value `hello:world` to the issue context data.
```programlisting
!set key="hello" value="world"
```
Use a script
In the JSON file, add `Set` to the `demisto.executeCommand` key.
The following example adds the key and value `hello:world` to the issue context data.
```programlisting
demisto.executeCommand("Set", {"key":"hello", "value":"world"})
```
Use a playbook
Use the `Set` script in a standard task.
Example: An issue's context data contains the following values:
```programlisting
{
"Account":
{
"firstName": "Bob",
"lastName": "Jones",
}
}
```
For an automation, you need to use the full name value. You can use the `Set` script to add an new `fullName` value to the JSON:
Result:
```programlisting
{
"Account":
{
"firstName": "Bob",
"fullName": "Bob Jones"
"lastName": "Jones",
}
}
```
---
# 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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/context-data/add-context-data-to-an-issue.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.