> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/send-e-mail-llm.md).

# Send e-mail (LLM)

Send LLM-generated text by email from a rule chain.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FHgft0I5hJPwb9CUXPzzr%2FLLM%20email.png?alt=media&amp;token=e076e935-c9a0-4233-a8eb-fce4b1df32f6" alt="" width="375"><figcaption></figcaption></figure></div>

Use **Send Email LLM** to send generated text by email.

This node is designed for text produced by **LLM Call**.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FzygiVrkOo7ClIeUoG0xf%2Fimage%2057.png?alt=media&amp;token=c8c17663-2c06-4d77-bbad-b52329b1782a" alt="" width="230"><figcaption></figcaption></figure></div>

### What it does

The node sends an email with generated content.

Use it to deliver reports, summaries, or alerts.

### Inputs

* **Trigger** — Starts the email action.
* **Text** — Passes the email body.
* **Subject** — Optionally passes the email subject.
* **Targets** — Optionally passes the recipients.

### Configurable settings

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FNRou1f8hMHkn5iBp70pL%2FLLM%20Eamail.png?alt=media&amp;token=e9de6361-f545-4aa0-8ada-b6891a833930" alt="" width="375"><figcaption></figcaption></figure></div>

* **Subject** — Set a fixed subject.
* **To** — Set one or more recipient addresses.
* **Fallback text** — Define a message if no text input is available.

### Typical use

Use **Send Email LLM** after **LLM Call**.

Connected inputs can override the fixed subject or target values.

### Related documentation

* [LLM Call](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/llm-call.md)
* [Mail](/collection/platform/platform-core/alert-and-escalation/escalations/notification-provider/mail.md)
* [Nodes](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes.md)

For the full editor flow, see [Configure Rule Chain](/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md).


---

# 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.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/send-e-mail-llm.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.