> For the complete documentation index, see [llms.txt](https://manuals.dialox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.dialox.ai/studio/flows/nodes/send-email.md).

# Send: Email

Using the **Send: Email** node, it is possible to send out emails as part of a Flow. Emails can be sent to either the user that is engaging with the Bot, or the business or owner of the Bot using a specified email address.

<figure><img src="/files/oDSbpPsaVYO5RWZ7miZ8" alt=""><figcaption></figcaption></figure>

The node expects an email address to be configured in the email address field. If not provided, it will use `user.email` by default.

<figure><img src="/files/9PYsqOq0stbv1m7dQRyL" alt=""><figcaption><p>Send email</p></figcaption></figure>

If "email address from variable" is selected as the destination, the email address will be fetched dynamically from the variable entered in the "email\_variable" field: `new_email` in the below example.

<figure><img src="/files/Ksg4nwdD3MGznkj3mShw" alt=""><figcaption></figcaption></figure>

#### Email attachments

Email attachments require three fields:

* **Caption:** the name that will be given to the file when attached in the email
* **URL**: the URL pointing to the file; the file must be publicly accessible
* **File type**: should be one of 'image', 'audio', 'video', or 'file'.

| Property       | Description                                            | Explanation                                                                                                                                  |
| -------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Subject        | The subject of the message                             | Variables can be embedded using #{ … }                                                                                                       |
| Message        | The message body                                       | Variables can be embedded using #{ … }                                                                                                       |
| Destination    | Target destination                                     | Define how the target email address is configured, either by providing an email address or selecting a variable which holds an email address |
| Email address  | The recipient of the email                             | When this field is left blank, it will use the user's email address                                                                          |
| Email variable | The variable in which the email address is to be found | The chosen variable should hold the email address to which to send the email to                                                              |
| CC             | Carbon copy email addresses                            | use the Add cc button to add email addresses that should be used to send a carbon copy of the email.                                         |
| Attachments    | File attachments                                       | Set the correct file type and url of the attachment                                                                                          |

## Changing the email template

Standard emails that are sent out by the platform use labels, which can be configured in the `labels.yaml` file. For this you need the developer role.

<figure><img src="/files/JAN6WJPER4e1iQwkklF5" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manuals.dialox.ai/studio/flows/nodes/send-email.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.