> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/es/portal-de-administracion/settings/log-exporter/teams.md).
# Teams
## Requisitos previos
Para ingerir los registros de RADIUSaaS en un **Canal de Microsoft Teams**, solo Microsoft Teams y privilegios para agregar **conectores** al correspondiente **canal** son necesarios.
## Pasos de configuración
Siga estos pasos para enviar los registros de RADIUSaaS a un **Canal de Microsoft Teams**:
1. Vaya a **Microsoft Teams**
2. Haga clic en el **Canal** > **Más opciones** > **Administrar equipo**
3. Vaya a **Aplicaciones**
4. Haga clic en **+ Obtener más aplicaciones**
5. Busque "**Webhook entrante**"
6. Haga clic en **Agregar** luego **Agregar a un equipo**
7. Seleccione su equipo
8. Haga clic en **Configurar un conector**
9. Proporcione un **Nombre** para el conector
10. Cargue un logotipo
11. Haga clic en **Crear** para generar el **URL del conector Webhook**
{% hint style="warning" %}
Asegúrese de copiar la URL.
{% endhint %}
Ahora es el momento de configurar el destino de exportación en Log Exporter.
* Vaya a su **Portal de administración de RADIUSaaS > Log Exporter**
* Haga clic en **+ Agregar** > **Teams**
* Proporcione un **Nombre** y **Descripción**
* Configure el **Filtros de mensajes** según sus necesidades
* Pegue el **URL del conector Webhook** en el campo **URL de webhook del canal de Teams**
* Configure el **Mensaje** para que se envíen a su canal de Microsoft Teams
---
# 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.radiusaas.com/es/portal-de-administracion/settings/log-exporter/teams.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.
