> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/desktop/email/set-to-email-id.md).

# Set To email ID

This is a pre-built action in Avo Assure and comes under **@Email Element.** The functionality of this action in Avo Assure is to set the mail ID in the ‘To’ field of the Outlook application.

### Syntax

**Input Value:** `<Mail ID 1>;<Mail ID 2>; …;<Mail ID n>`

| Argument                                                           | Description                                                           |
| ------------------------------------------------------------------ | --------------------------------------------------------------------- |
| <p>\<Mail ID 1>;\<Mail ID 2>; …;\<Mail ID n>></p><p>(Required)</p> | Provide one or more recipient email addresses separated by semicolons |

{% hint style="warning" %}
**Note:** We need to right-click on the folder in the outlook desktop application that the user wants to switch, copy the path, and add it in the input followed by a ‘\’ and the folder name, as shown in the example below.

Example: \\\\<john.white123@.com>\Inbox\*
{% endhint %}

**Output Value:**

<table><thead><tr><th valign="top">Argument</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">&#x3C;Dynamic Variable>(Optional);&#x3C;Dynamic Variable>(Optional)</td><td valign="top">This dynamic variable holds the status of the action as <strong>True</strong> or <strong>False</strong>.</td></tr></tbody></table>

**Example**

**Sets the recipients in the ‘To’ field of the Outlook desktop application**

The **Set To email ID** action takes the value from the Input Value column (e.g., **<Jack@example.com>**;**<Alice@example.com>**) and enters the provided email IDs in the ‘To’ field of the Outlook application.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FyY4AMCIzsBF26S550tof%2Fimage.png?alt=media&amp;token=9d6f4620-dead-44e1-b52e-9d068379d1db" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/desktop/email/set-to-email-id.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.