> 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/external-api-integration-in-bot-flow.md).

# External API Integration in Bot Flow

This feature allows you to connect an external API and fetch real-time data inside your WhatsApp chatbot.

#### Steps:

1. Go to **Chatbot** and click on **Create Bot Flow**
2. Enter **Bot Flow name**
3. Add a **Trigger** (Keyword) and select channel
4. Add **Ask Question** block to collect user name
5. Add another question to collect **Phone Number / Booking ID**
6. Send a message like “Please wait while we fetch details”
7. Add a node → **Automation App → External API Call**
8. Select request type (**GET/POST**)
9. Enter **API URL**
10. Add **Headers** (e.g., Content-Type: application/json)
11. Select **Body Type (JSON)** and add request body
12. Run and save API configuration
13. Map API response variables
14. Add **Interactive Message** to confirm booking (Confirm/Cancel)
15. Save and **Enable Bot Flow**

This setup helps fetch and display real-time data from external systems directly in your chatbot.

{% embed url="<https://youtu.be/-aVZEBNUDUw?si=yILmsd5KbW_pZz-n>" %}


---

# 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/external-api-integration-in-bot-flow.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.