> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/message-blocks/document-message-block.md).

# Document Message Block

The **Document Message Block** inside **Send Message** allows you to automatically send documents such as **PDFs, brochures, invoices, or reports** to users during a chatbot conversation.

#### How to Use the Document Message Block

1. Open your **Chat Flow** in the bot builder.
2. Set the **Trigger or Keyword**.
3. Click **Add Node**.
4. Select **Send Message → Document Message**.

#### Add Document

You can add the document in two ways:

* **Upload the document** directly from your system, or
* Paste the **document URL**.

After uploading, you can also provide a **file name** for the document.

#### Add Caption (Optional)

You can include a caption to explain the document.

5. Click **Start Upload** and then **Save Message**.

Once the flow is triggered, the document will be automatically sent to the user in the chat.

{% embed url="<https://www.youtube.com/watch?v=_Mp1kWt480g>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/message-blocks/document-message-block.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.