> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/report-and-run-integrate/content/images/add-follow-up-image.md).
# Agregar imagen de seguimiento
Agrega imágenes de seguimiento a imágenes existentes del informe para mostrar el progreso a lo largo del tiempo y dar una actualización visual del estado.
1. Toca un informe para abrirlo.
2. Toque una imagen.
3. Deslice hacia arriba la barra de herramientas debajo de la imagen para mostrar más opciones.\
4. Desplácese hacia abajo hasta *Imágenes de seguimiento* sección en la parte inferior de la pantalla.\
5. Toca el **Imagen** icono para subir una imagen que ya tiene guardada en su dispositivo.\
6. Toca el **Cámara** icono para tomar una imagen de seguimiento usando su cámara.
7. Toca el **Creador de imágenes** icono para añadir una imagen de seguimiento junto a la imagen original (para un [antes y después](/manual/es/report-and-run-integrate/content/image-builder/create-before-and-after-image.md)).\
{% hint style="info" %}
Solo la imagen de seguimiento más reciente se mostrará en los informes.
{% endhint %}
---
# 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.reportandrun.com/manual/es/report-and-run-integrate/content/images/add-follow-up-image.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.