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

# Scripts

Los scripts en Remote Desktop Manager automatizan tareas mediante PowerShell, AutoHotKey, AutoIt o VBScript, y se ejecutan de forma local o remota en torno a las conexiones.

Automatice procesos en Remote Desktop Manager mediante scripts escritos en PowerShell, AutoHotKey, AutoIt, VBScript y más. Almacene los scripts en bóvedas individuales o en la bóveda del sistema para compartirlos entre varias bóvedas, y ejecútelos de forma local o remota en uno o varios sistemas.

Combine scripts con eventos para desencadenar acciones antes o después de una conexión, y asócielos con macros de escritura para estandarizar flujos de trabajo como comprobaciones previas, recopilación de registros y limpieza.

#### Temas relacionados

* [Scripting con PowerShell](https://docs.devolutions.net/powershell/es/remote-desktop-manager-powershell/powershell-scripting)
* [Herramientas](/rdm/es/ribbon-menu-bar/tools.md)

#### Véase también

* [All Roads Lead to PowerShell](https://blog.devolutions.net/2023/09/all-roads-lead-to-powershell/)
* [Getting the Most out of Remote Desktop Manager: Guide to Real-world Use Cases](https://youtu.be/paw_cyY8BoQ?si=mTWGfe0S5ASLII0D)


---

# 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 dynamically 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/scripts.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 `build a script that syncs our docs to a CMS` 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.