> 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/telegram-components/inbound.md).

# Inbound

### Overview

The **Telegram Incoming Messages Trigger** is an input node (*inbound trigger*) based on communication events via messaging. Its main function is to listen to a specific Telegram bot and trigger an automation flow or chatbot instantly when a user sends a new message or interacts with the bot for the first time (command `/start`).

**Service Retention Rule:** Just like in WhatsApp and Facebook channels, the trigger has built-in state control intelligence. It will only start the automation if the contact **does not have a human agent conversation or an open ticket** is in the system. If the conversation is already under the responsibility of an operator, the messages sent by the user will be sent directly to the attendant's chat screen, ignoring this trigger to avoid duplication or interference in the human conversation.

### Configuration Parameters

The trigger setup links the automation to the bot's official account on the platform through the following criterion:

* **Channel:** Drop-down menu used to select which Telegram Bot integrated with the platform will be monitored by this specific flow. It lists all bots that were connected through the API token provided by the *BotFather*.<br>

### Visual Builder

The graphical interface is designed to be clean, isolating the automation's starting point:

* **Textual Instance Search:** The drop-down menu has an internal search field (*Type your search here*) to quickly locate the correct bot in workspaces that manage multiple accounts and support bots.<br>
* **Inputless Start Node:** In the flow graph editor, this component is positioned at the far left end of the screen. It has no input connectors, as its execution is triggered exclusively by an external stimulus (the message sent by the end user to the bot).<br>

### Special Operators

The logical properties of this component manage the capture of profile identities and the control of native variables in the Telegram ecosystem:

* **Profile Payload Injection (Telegram Metadata):** As soon as the user sends the activating message, the trigger engine captures the data publicly provided by the Telegram API, such as the **User ID (Chat ID)**, the **Username** (username starting with `@`), the **First Name** (*First Name*) and the **Last Name** (*Last Name*), making these variables immediately available for use in the next blocks.<br>
* **Opening an Unrestricted Communication Window:** Unlike other channels based on recharges or approved templates (HSM), activating the Telegram trigger opens a free communication channel. The automation can respond to the user with message blocks of any format and with no session time limits, as long as the bot has not been blocked by the user.<br>

### Practical Examples

The table below shows trigger behavior scenarios according to the user's current status in the system:

| **Selected Bot (Channel)**      | **User Status in the Dashboard**             | **User Action on Telegram**        | **Trigger Behavior**                                                                                                            |
| ------------------------------- | -------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **@Bot\_Atendimento\_Ficticio** | No open tickets.                             | Clicked "Start" or sent a "Hello". | **Triggers the flow:** The trigger captures the contact and starts the self-service chatbot menu.                               |
| **@Bot\_Suporte\_Ficticio**     | Currently being assisted by Operator Daniel. | Sent a log file or text message.   | **Ignores the trigger:** The content goes directly to Daniel's screen; the automation does not interfere with the conversation. |
| **@Bot\_Atendimento\_Ficticio** | Waiting in the General Waiting Queue.        | Sent the message "I need help".    | **Ignores the trigger:** The contact remains in the human dashboard’s waiting queue, keeping the original arrival priority.     |


---

# 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/telegram-components/inbound.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.