> 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/send-email.md). # Send Email This is a pre-built action in Avo Assure and comes under **@Email Element.** The functionality of this action in Avo Assure is to send an email to the receiver. ### Syntax **Input Value:** `N/A or (optional-Ignore Subject)>` | Argument | Description | | ----------------------------------------- | --------------------------------------------------------------------------- | | N/A | No input is required to send the email if the subject is already specified. | |

\

(Optional)

| Optional input to bypass the Outlook warning for missing email subject. | {% hint style="warning" %} **Note:** If you attempt to send an email without specifying a subject, a pop-up will appear asking if you still want to send the email without a subject. To bypass this prompt, you can provide the input "**ignore subject**. {% endhint %} **Output Value:**
ArgumentDescription
<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)This dynamic variable holds the status of the action as True or False.
**Example 1** **Sends the composed email in the Outlook application using optional parameter** The **Send Email** action takes the value from the Input Value column (e.g., **Ignore Subject**) and performs the send operation for the drafted email in Outlook. If no subject is provided, a confirmation pop-up appears. To bypass this pop-up and send the email without a subject, input the value **Ignore Subject**.
**Example 2** **Sends the composed email in the Outlook application** The **Send Email** action sends the composed email in Outlook. If the subject is already specified in the email then, no input value is required.
--- # 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/send-email.md?ask=&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.