> 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/whatsapp-mini-apps/send-whatsapp-mini-apps-native-flows-via-bot-builder.md).

# Send WhatsApp Mini Apps / Native Flows Via Bot Builder

Follow these steps to make your Mini App interactive inside a chatbot:

Step 1: Create Bot Flow

1. Go to **Chatbot → Create Bot Flow**
2. Enter a **Flow Title**
3. Click **+ → WhatsApp Chatbot**
4. Select **Keyword Trigger**, Channel, and Condition
5. Click **Save**

Step 2: Add Mini App Block

6. Click **Add Question Block**
7. Scroll and select **WhatsApp Mini App**
8. Add Header and Body text (optional)
9. Enter a **Button Label** (e.g., Register Now)
10. Select your **Mini App Flow** (Draft or Published)
11. Choose the **Landing Screen**
12. Save response to a **Super Field** (if required)

Step 3: Finalize

13. Click **Save Question**
14. Save and **Enable** the workflow

Now your WhatsApp Mini App is fully integrated inside the chatbot and ready to collect structured data directly into CRM.

{% embed url="<https://youtu.be/kshys99IpPI>" %}


---

# 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/whatsapp-mini-apps/send-whatsapp-mini-apps-native-flows-via-bot-builder.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.