> 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-trigger.md).

# Email Trigger

### Overview

The **Inbound Email Trigger** (identified in the interface by the technical title `Email Trigger`) is an entry node (*inbound trigger*) based on inbox synchronization events. Its main function is to monitor corporate email accounts and instantly trigger an automated flow of processes or electronic responses the moment the selected connection receives a new email message from an external sender.

### Configuration Parameters

The trigger configuration associates the automation with the correct mailbox configured on the platform:

* **Channel:** Dropdown used to select which integrated email account (via IMAP/POP3 protocols or keys from approved providers) will be responsible for activating this specific flow. The selector displays the corporate emails available in the organization (e.g.: `support@company.com`).<br>

### Visual Builder

The graphical interface follows the streamlined standard of the platform's native trigger blocks:

* **Direct Association Dropdown:** A simplified dropdown menu that allows you to directly link the monitored email account, ensuring that the engine starts reading messages from the corresponding *Inbox* as soon as the node is saved.<br>
* **Initial Node Without Input:** In the graphical flow editor, this component is positioned at the far left starting edge of the screen. It has no connectors or input ports receiving links from other nodes, since its execution is activated 100% by an external stimulus (the arrival of an email sent by a customer).<br>

### Special Operators

The logical properties of this component manage email payload extraction, header reading, and file routing:

* **Email Payload Injection (Message Metadata):** As soon as an email is received and processed by the trigger, the engine automatically captures crucial MIME structure properties and transforms them into dynamic variables ready for use in subsequent blocks. The payload includes:
  * `email.sender`: The email address of the person who sent the message (used as the contact identifier).<br>
  * `email.subject`: The subject typed in the *Subject*.<br>
  * `email.body`: The main text contained in the message (in plain text or HTML format).<br>
  * `email.attachments`: A list containing the URLs of the files attached to the message.<br>
* **Thread Traceability Control (In-Reply-To):** The component reads the email header IDs. If the received email is a reply to a previous conversation triggered by the system, the trigger can associate the message with the same ticket or contact already existing in the CRM database.<br>

### Practical Examples

The table below shows classic scenarios of how to structure the use of the email trigger to automate operational routines:

| **Selected Channel (Email)**                             | **Subject of the Received Email** | **Content / Sender Action**           | **System Behavior**                                                                                                                                                                 |
| -------------------------------------------------------- | --------------------------------- | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**support@company.com**](mailto:suporte@empresa.com)    | "Problem with my access"          | Sent text reporting a bug.            | **Triggers the flow:** The trigger captures the sender, extracts the body text and starts an automated flow that opens a support ticket and sends a reply email confirming receipt. |
| [**finance@company.com**](mailto:financeiro@empresa.com) | "Proof of Payment Submission"     | Email containing a PDF file attached. | **Triggers the flow:** The automation starts, isolates the file from the variable `email.attachments` and sends it directly to a billing API block for internal validation.         |
| [**sales@company.com**](mailto:vendas@empresa.com)       | "Proposal Request"                | Text requesting a catalog.            | **Triggers the flow:** The system validates the lead's email and triggers a subsequent component that replies to the customer, attaching the product catalog fully autonomously.    |


---

# 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-trigger.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.