> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/es/concepts/advanced-concepts/events.md).

# Eventos

Los eventos de Remote Desktop Manager activan macros, scripts o herramientas antes y después de abrir o cerrar conexiones para automatizar las tareas y la limpieza de la sesión.

Los eventos de Remote Desktop Manager le permiten ejecutar automáticamente macros, scripts o herramientas antes o después de que se abra o se cierre una conexión. Utilice los cuatro activadores: Before Open, After Open, Before Close y After Close para estandarizar las tareas previas y posteriores a la conexión.

Entre los usos habituales se incluyen iniciar una herramienta auxiliar necesaria, lanzar una macro de escritura o ejecutar un script de PowerShell para recopilar registros o hacer limpieza después de una sesión. Los eventos funcionan junto con las macros y los scripts almacenados en sus bóvedas para poder reutilizarlos y mantener la coherencia.

#### Temas relacionados

* [Configuración de eventos de los tipos de entrada](/rdm/es/knowledge-base/how-to-articles/entry-types-events-settings.md)
* [Registros](/rdm/es/ribbon-menu-bar/window/logs.md)
* [Registros de actividad](/rdm/es/ribbon-menu-bar/reports/activity-logs.md)
* [Scripting con PowerShell](https://docs.devolutions.net/powershell/es/remote-desktop-manager-powershell/powershell-scripting)

#### Véase también

* [Devolutions Academy - Streamlining Remote Connections with Event Triggers](https://academy.devolutions.net/student/path/1925316/activity/2668000)
* [Devolutions Blog - All Roads Lead to PowerShell](https://blog.devolutions.net/2023/09/all-roads-lead-to-powershell/)


---

# 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.devolutions.net/rdm/es/concepts/advanced-concepts/events.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.