> 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-6.x-faqs/cortex-xsoar-6-faqs/content-feature-requests.md).
# Content Feature Requests
How to submit a content feature request in Cortex XSOAR 6x.
You can submit content feature requests to your Account Team or Customer Success Team.
To ensure we fully understand your needs, include the following information:
For a new integration or integration enhancement:
**Product details**
* Name and version of the product you want to integrate with.
* The deployment type for the product (SaaS, Hybrid, On-premise).
* API documentation and specific needed API calls (if available).
**Use case details for the new integration or integration enhancement**
* High-level description of what you want to achieve. For example, *While analyzing a phishing incident, I would like to utilize the integration to detonate the attached file*.
* Specific workflows or tasks the integration will support.
* Examples of relevant incidents or commands.
* Integrations that will be used as part of the use case.
For a new use case request
* Describe the use case flow.
* Provide a list of integrations you would like to be supported as part of the use case (if available).
* Describe what data needs to be extracted or what actions are to be triggered.
* Share any relevant flow charts or example playbooks you may have created.
---
# 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-xsoar-6.x-faqs/cortex-xsoar-6-faqs/content-feature-requests.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.