> For the complete documentation index, see [llms.txt](https://docs.flowiseai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/llamaindex/engine/sub-question-query-engine.md).
# Sub-Question Query Engine
Un query engine diseñado para resolver el problema de responder a una consulta compleja utilizando múltiples fuentes de datos. Primero divide la consulta compleja en sub-preguntas para cada fuente de datos relevante, luego reúne todas las respuestas intermedias y sintetiza una respuesta final.
## Entradas
* Query Engine Tools
* Chat Model
* Embeddings
* [Response Synthesizer](/espanol/documentacion-oficial/integraciones/llamaindex/response-synthesizer.md)
## Parámetros
| Nombre | Descripción |
| ----------------------- | --------------------------------------------------------------------- |
| Return Source Documents | Para devolver citas/fuentes que se usaron para construir la respuesta |
## Salidas
| Nombre | Descripción |
| ---------------------- | ------------------------------------- |
| SubQuestionQueryEngine | Nodo final para devolver la respuesta |
---
# 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://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/llamaindex/engine/sub-question-query-engine.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.
%20(1)%20(1)%20(1)%20(1)%20(2)%20(1).png?alt=media)