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

# WhatsApp Message

### Overview

The **WhatsApp Message Sending Component** is an action node focused on session outbound communication. Its main function is to transmit active messages containing text or media files directly to the end user's device during the automation flow. It is used to provide informative feedback, share informational materials, and enrich the support experience with various media within the customer's active conversation window.

### Configuration Parameters

The component configuration determines the format of the content that will be sent to the application's sending queue:

* **Message type:** Dropdown menu that defines the nature and structural behavior of the message bubble the customer will receive. The options include:
  * `Text`: Messages composed strictly of text blocks (with support for emojis and links).<br>
  * `Audio`: Transmission of sound files (usually sent with the native recording property).<br>
  * `Document`: Sharing of corporate or tax files (PDFs, spreadsheets, text files).<br>
  * `Image`: Sending visual and corporate graphic files (PNG, JPG).<br>
  * `Video`: Sharing of audiovisual media in compatible formats (MP4).<br>
  * `Payment`: Specialized module for sending billing orders or interactive charges.<br>
* \_*Message (* Required Field):\_\* The body of the message's main text that will accompany the sending (in media formats such as `Document` or `Image`, this field functions as the media caption).<br>

### Visual Builder

The graphical interface is highly responsive and instantly adapts its form blocks according to the item selected in the field *Message type*:

* **Basic Structure (`Text`):** Renders a lean interface composed only of the type selector and a required rich text box (`*`).<br>
* **Advanced Media Structure (`Document`, `Image`, `Video`):** When switching to media sending, the builder expands and adds new management blocks on screen:
  * `File URL`: Text input field to provide the HTTP address or public link where the media is hosted for the API server to fetch.<br>
  * `Upload Button`: Native purple button that opens the local system's file window to upload the file directly to the platform's CDN.<br>
  * `documents block (+ Add file)`: List repeater selector that allows grouping multiple attachment files in batch within the same processing node.<br>

### Special Operators

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

* **Scope Tag Interpolation (Dynamic Mapping):** Both the content field of the *Message* (or caption) and the field of the *File URL* accept the inclusion of global and local variables from the platform through double-brace syntax (`{{...}}`). This allows the system to fetch the link to a PDF payment slip generated by a previous API node and dynamically insert the link into the sending field.<br>
* **Sequential Asynchronous Sending:** The automation engine processes the sending quickly in a linear manner. After passing the data package to the WhatsApp gateway, the block's output port releases the contact instantly to the next component in the design flow, avoiding freezes in the experience.<br>

### Practical Examples

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

| **Selected Message Type** | **File URL / Upload**  | **Configured Content (Message)**                                                | **Practical Use Case**                                                                             |
| ------------------------- | ---------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| `Text`                    | *None*                 | "Thank you for registering, `{{name}}`! A consultant will contact you shortly." | Send a simple registration confirmation text using variables collected during the screening.       |
| `Document`                | `{{link_boleto_pdf}}`  | "Here is the billing slip for your invoice generated for the current month."    | Automatically send the PDF billing file to a customer who requested a second copy in the menu.     |
| `Image`                   | *Upload of banner.png* | "Check out our new service hours for the end of the year! 🎄"                   | Trigger an informative graphic card with an explanatory caption at the opening of a specific flow. |


---

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