> 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/fr/actions/workflow-concepts/workflow-steps/ai-steps.md).

# IA

Exploitez les dernières avancées de l'IA dans vos workflows

Les étapes IA sont les outils les plus puissants à votre disposition pour développer des workflows. AirOps prend actuellement en charge les étapes IA suivantes :

1. [**Interroger le LLM**](https://docs.airops.com/docs/fr/actions/workflow-concepts/workflow-steps/ai-steps/llm.md)**:** comprendre et générer des réponses à partir d’entrées personnalisées
2. [**Transcrire un fichier audio**](https://docs.airops.com/docs/fr/actions/workflow-concepts/workflow-steps/ai-steps/transcription.md)**:** analyser et transcrire des fichiers audio ou vidéo en texte

Alors que le domaine de l’IA continue de se développer rapidement, nous sommes impatients de poursuivre l’élargissement de ces offres. En attendant, nous serions ravis de recueillir vos retours à mesure que vous commencez à explorer chaque étape IA en détail !

{% hint style="info" %}
Remarque : les étapes IA sont uniquement disponibles pour les workflows. Elles ne sont pas disponibles pour les agents pour le moment.
{% 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/fr/actions/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.
