> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/email-trigger-and-send-message/email-message.md).

# Email message

### Overview

The **Email Sending Component** is an action node focused on structured outbound email communication. Its main function is to send institutional, transactional, or informational emails to contacts moving through the automation flow. The component operates integrated with email providers and allows loading preconfigured models (*templates*), offering flexibility to customize or locally rewrite the message content without changing the original matrix saved in the platform's global settings.

### Configuration Parameters

The block configuration manages sending credentials, addressing, routing, and message content construction:

* **Connection:** Dropdown menu used to select which integrated email account (e.g., `support@company.com`) will be responsible for physically sending the message.<br>
* **Template:** Dropdown menu that lists the pre-registered email templates in the selected connection. When you choose an item from this list, the platform pulls the layout and the original structured text blocks.<br>
* **Send to (\* Required Field):** Text input field that defines the email recipient. It accepts manual entry of emails or dynamic injection of tags (such as `{{email}}`).<br>
* **Department / User / Campaign (Assignment and Traceability):** Optional dropdown menus to manage the contact's association if they reply to the message. It allows associating the lead with a support queue (*Department*), a fixed operator (*User*) or marking the journey tag (*Campaign*).<br>
* **Subject (\* Required Field):** Header line that defines the email title seen by the customer in their inbox.<br>
* **Message (\* Required Field):** The main body of the email. This rich text editor is automatically filled when a template is selected, but remains 100% editable for minor changes.<br>
* **Do Not Open Support Case (Toggle Switch):** When enabled, if the customer replies to the email sent by this node, the system ignores the interaction in the human queue. When disabled (default), any reply automatically opens a ticket for the operators.<br>

### Visual Builder

The builder interface was designed to balance pattern-based automation with agile customization flexibility:

* **Isolated Local Message Editor:** As shown in the configuration interface, the builder's great advantage is allowing free editing inside the *Message* box. Text, link, or formatting changes entered in this editor alter the behavior **only for this specific component in the flow tree**, keeping the integrity and format of the original template untouched in the global library.<br>
* **Sending Validation Lock:** The asterisks (`*`) in the fields of *Send to*, *Subject* and *Message* ) work as required visual validators. The graphical builder prevents the automation from being published if the destination email or title is empty.<br>

### Special Operators

The logical properties of this component handle HTML string interpreters and dynamic interpolation of corporate tags:

* **Layered Variable Interpolation (Merge Tags):** Both the *Subject* field and the *Message* body accept the use of double braces `{{...}}`. This makes it possible to cross-reference dynamic CRM data (such as `{{name}}`, `{{codigo_pedido}}` or `{{link_boleto}}`) directly in the email text, generating personalized mass messages for each contact that passes through the node.<br>
* **Continuous Asynchronous Processing:** In the flow graph editor, this component displays traditional connection ports. As soon as the platform engine processes the command and passes the structured data (MIME) to the connection's SMTP server, the contact is immediately released to the next connected block in the flow output, executing the sending in the background.<br>

### Practical Examples

The table below shows scenarios for using the component by combining registered templates with customized local edits:

| **Selected Connection**                                  | **Selected Template** | **Local Edit Made in the "Message"**                                                                                    | **Send to**                  | **Practical Use Case**                                                                                                                 |
| -------------------------------------------------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| [**sales@company.com**](mailto:vendas@empresa.com)       | `Default_Welcome`     | An extra paragraph was added with an exclusive invitation: *"By the way, `{{name}}`, we have an invitation for you..."* | `{{email_contato}}`          | Send the brand's traditional welcome email, but include a personalized notice and dynamic links valid only for that specific campaign. |
| [**finance@company.com**](mailto:financeiro@empresa.com) | `Billing_Overdue`     | The default text was changed to include the phrase in bold: **"ATTENTION: Deadline extended until tomorrow"**.          | `{{cliente.email_cadastro}}` | Adjust the urgency tone of a billing sequence in a specific cart recovery flow, without affecting the general billing template.        |
| [**support@company.com**](mailto:suporte@empresa.com)    | *None (Free Text)*    | Writing a 100% manual email informing about scheduled maintenance on the company's servers.                             | `{{contato.email}}`          | Send one-off technical notices using the channel infrastructure without needing to create a permanent template on the platform.        |


---

# 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://docs.hablla.com/hablla-docs-en/automation-flows/all-components/email-trigger-and-send-message/email-message.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.