> 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/facebook-components/facebook-message.md).

# Facebook Message

### Overview

The **Facebook Messenger Message Sending Component** is an action node focused on outbound session communication. Its main function is to transmit active messages containing text or media files directly to the end user's private message inbox (DM) during the automation flow. It is used to provide informative feedback, share promotional materials, and enrich the support experience in a multimedia way within the customer's active conversation window on the page.

### Configuration Parameters

The component settings determine the format of the content that will be sent to the Meta messaging API:

* **Message type:** Dropdown menu that defines the nature and structural behavior of the message bubble the customer will receive in the chat. The options include:
  * `Text`: Messages composed strictly of text blocks (with support for emojis and links).<br>
  * `Audio`: Transmission of audio files.<br>
  * `Document`: Sharing of corporate files (PDFs, guides, e-books).<br>
  * `Image`: Sending of visual and graphic corporate files (PNG, JPG, GIFs).<br>
  * `Video`: Sharing of audiovisual media in compatible formats (MP4).<br>
* **Message (\* Required Field):** The main text body of the message that will accompany the send (in media formats such as `Document` or `Image`, this field acts as the caption or supporting text for the media sent).<br>

### Visual Builder

The graphical interface instantly adapts its form blocks according to the item selected in the field *Message Type*:

* **Basic Structure (`Text`):** Renders a clean interface composed only of the type selector and a required rich text box (`*`).<br>
* **Media Structure (`Audio`, `Document`, `Image`, `Video`):** When switching to media sending, the builder expands and adds file management fields to the screen:
  * `File URL`: Text field to enter the HTTP address or public link where the media is hosted for the Meta server to fetch.<br>
  * `Upload Button`: Opens the local operating system file window to upload the file directly to the platform's CDN.<br>
  * `Button + Add file`: Allows grouping multiple attachment files to be sent in sequential batches within the same node.<br>

### Special Operators

The logical properties of this component manage payload compilation and dynamic data injection in the Messenger view layer:

* **Scope Tag Interpolation (Dynamic Mapping):** Both the content field of the *Message* (or caption) and the field of *File URL* accept the inclusion of global and local platform variables through double-brace syntax (`{{...}}`). This allows the system to fetch an image of a product selected by the customer in a previous node and insert the link dynamically into the sending field.<br>
* **Session Window Monitoring (Exit Rule):** The automation engine processes the send in a fast linear manner. After passing the data packet to the Facebook Messenger gateway, the block's output port releases the contact instantly to the next component in the design flow, operating asynchronously.<br>

### Practical Examples

The table below demonstrates classic application scenarios for this component to trigger varied content throughout a Facebook Messenger flow:

| **Selected Message Type** | **File URL / Upload**            | **Configured Content (Message)**                                                    | **Practical Use Case**                                                                         |
| ------------------------- | -------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| `Text`                    | *None*                           | "Hello, `{{name}}`! Your appointment has been successfully confirmed for tomorrow." | Send a simple appointment confirmation text using variables collected throughout the flow.     |
| `Document`                | `{{link_catalogo_pdf}}`          | "Here is our complete product catalog in PDF!"                                      | Automatically send the catalog file to a customer who requested the pricing table in the menu. |
| `Image`                   | *Upload of banner\_promocao.jpg* | "Take advantage of our special deal of the week! 🚀"                                | Trigger a promotional graphic card with an explanatory caption at the start of a flow branch.  |


---

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