> 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/concepts/advanced-concepts/events.md).

# Events

Events in Remote Desktop Manager trigger macros, scripts, or tools before and after connections open or close to automate session tasks and cleanup.

Events in Remote Desktop Manager let you automatically run macros, scripts, or tools before or after a connection opens or closes. Use the four triggers: Before Open, After Open, Before Close, and After Close to standardize pre and post connection tasks.

Typical uses include starting a required helper tool, launching a typing macro, or running a PowerShell script to collect logs or clean up after a session. Events work alongside macros and scripts stored in your vaults for reuse and consistency.

#### Related topics

* [Entry types events settings](/rdm/knowledge-base/how-to-articles/entry-types-events-settings.md)
* [Logs](/rdm/ribbon-menu-bar/window/logs.md)
* [Activity logs](/rdm/ribbon-menu-bar/reports/activity-logs.md)
* [PowerShell scripting](https://docs.devolutions.net/powershell/remote-desktop-manager-powershell/powershell-scripting)

#### See also

* [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/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.