> 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/knowledge-base/knowledge-base-articles/macro-parameters.md).

# Parámetros de macro

Configure parámetros de macro en Remote Desktop Manager para entradas de línea de comandos, macros de escritura y terminal, incluidos los campos de entrada protegidos.

Los parámetros están disponibles para las entradas ***Command line (External Application)***, ***Command line (Macros/Scripts/Tools)***, ***Windows terminal*** y ***Typing macros (Macros/Scripts/Tools)***.

* ***Text***: parámetros que permiten introducir texto estándar.
* ***Secured***: parámetros diseñados para gestionar información sensible de forma segura, ocultando la entrada a la vista.
* ***View Command***: vea el comando desde la sección ***General***.
* ***Prompt for parameters on open***: si esta opción está habilitada, los parámetros se mostrarán cada vez que se ejecute la macro.


---

# 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/knowledge-base/knowledge-base-articles/macro-parameters.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.