> 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/content-processing/convert-pdf-url-to-text.md).

# Convertir URL de PDF a texto

El paso "Convertir URL de PDF a texto" te permite extraer el contenido textual de un documento PDF disponible en una URL específica. Esta potente herramienta te permite analizar, procesar y trabajar con contenido de texto de PDFs sin necesidad de copiar o extraer manualmente.

### Cómo configurar el paso Convertir URL de PDF a texto

* **URL del PDF**: Introduce la URL completa del documento PDF que quieres convertir a texto.

{% hint style="info" %}
Importante: la URL debe apuntar directamente a un archivo PDF que sea de acceso público. Los PDF protegidos con contraseña no se pueden procesar.
{% endhint %}

### Formato de salida

El paso Convertir URL de PDF a texto devuelve el texto extraído:

```
Actualizaciones de la plataforma AirOps

Hola,
Estamos comenzando el año con actualizaciones que simplifican la forma en que creas y gestionas los flujos de contenido en AirOps. Hemos mejorado nuestras integraciones con CMS y análisis SERP, introducido más LLM en línea y creado ayudas de resolución de problemas más inteligentes para simplificar el desarrollo de tus flujos de trabajo. ¡Vamos a ello!

...
```


---

# 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/content-processing/convert-pdf-url-to-text.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.