# 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.
The node expects an email address to be configured in the email address field. If not provided, it will use `user.email` by default.
Send email
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.
#### 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.
