> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/es/inbox.md).

# Bandeja de entrada

Revisa el trabajo de AirOps que necesita tu atención

La bandeja de entrada es la cola a nivel de espacio de trabajo para el trabajo que requiere tu atención. Reúne en un solo lugar las revisiones pendientes de Playbook y las propuestas de Brand Kit.

## Qué aparece en la bandeja de entrada

La bandeja de entrada puede incluir:

* [Playbook](/docs/es/acciones/playbooks.md) Sesiones en espera en un punto de control de Revisión humana
* [Actualización del Brand Kit](/docs/es/contexto/brand-kit/refresh.md) propuestas que están listas para revisar

## Revisar un elemento

1. Abrir **Bandeja de entrada**.
2. Selecciona un elemento para ver su origen y el contexto de revisión.
3. Revisa o edita el resultado.
4. Completa la acción disponible para continuar o cerrar el elemento.

Para obtener un registro de cada ejecución, incluidas las ejecuciones que no necesitan revisión, usa [Historial de ejecuciones](/docs/es/tu-espacio-de-trabajo/monitoring/run-history.md). Para la configuración de revisión específica de Workflow, consulta [Revisión humana](/docs/es/acciones/workflow-concepts/workflow-steps/flow/human-review.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://docs.airops.com/docs/es/inbox.md?ask=<question>&goal=<user_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.