> 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/ai-steps.md).

# IA

Aprovecha lo último en IA en tus flujos de trabajo

Los pasos de IA son las herramientas más potentes a tu disposición al desarrollar flujos de trabajo. AirOps actualmente admite los siguientes pasos de IA:

1. [**Prompt de LLM**](/docs/es/acciones/workflow-concepts/workflow-steps/ai-steps/llm.md)**:** comprender y generar respuestas basadas en entradas personalizadas
2. [**Transcribir archivo de audio**](/docs/es/acciones/workflow-concepts/workflow-steps/ai-steps/transcription.md)**:** analizar y transcribir archivos de audio o video a texto

Como el campo de la IA sigue desarrollándose rápidamente, estamos deseando seguir ampliando estas funciones. Mientras tanto, ¡nos encantaría conocer tus comentarios a medida que comienzas a explorar cada paso de IA en detalle!

{% hint style="info" %}
Nota: los pasos de IA solo están disponibles para flujos de trabajo. Por el momento no están disponibles para los agentes.
{% 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.airops.com/docs/es/acciones/workflow-concepts/workflow-steps/ai-steps.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.