> 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/acciones/workflow-concepts/workflow-steps/image-and-video/screenshot-from-url.md).

# Captura de pantalla desde URL

El paso "Captura de pantalla desde URL" te permite capturar una captura de pantalla de una página web directamente dentro de tu flujo de trabajo. Esto es útil para crear referencias visuales, analizar diseños de sitios web o incluir capturas de páginas web en tu contenido.

### Cómo configurar el paso Captura de pantalla desde URL

Configurar el paso requiere establecer los parámetros mostrados a continuación:

* **URL**: Ingresa la URL completa de la página web que deseas capturar. Asegúrate de incluir el protocolo (http\:// o https\://).
* **Modo de captura**:
  * Página completa - Captura la altura completa (desplazándose hasta la parte inferior de la página) y el ancho de la página
  * Ventana visible - Captura la altura de la ventana visible original (sin desplazamiento) y el ancho completo

### Formato de salida

El paso Captura de pantalla desde URL devuelve una URL de imagen.


---

# 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/acciones/workflow-concepts/workflow-steps/image-and-video/screenshot-from-url.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.