> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/line-bot.md).

# Line Bot

Connect the LINE messaging platform with ZBrain Flow to build, manage, and automate conversational bots for your users.

Line Bot is an automated chatbot service for LINE, a popular messaging app. It allows businesses and developers to create interactive chat experiences, automate responses, and integrate with external services for customer engagement and support. This is a bot development platform for the LINE messaging app.

ZBrain integration with Line Bot enables these capabilities:

**Push Message**

Push message to the line account

**Custom API Call**

Send a custom API call to a specific endpoint

#### **How to Connect Line Bot to ZBrain Flow?** <a href="#how-to-connect-line-bot-to-zbrain-flow" id="how-to-connect-line-bot-to-zbrain-flow"></a>

To integrate Line Bot with ZBrain Flow, follow these steps to select and utilize the desired capabilities:

1. **Search for the Line Bot Component**: Search the Line Bot component within the ZBrain interface.
2. **Select the Required Capability**: Select the desired element such as Push message or Custom API call.

#### **Additional Settings to Create Line Bot Connection** <a href="#additional-settings-to-create-line-bot-connection" id="additional-settings-to-create-line-bot-connection"></a>

1. **Connection Name** - Enter a name for this connection to identify it.
2. **Bot Token** - Provide the LINE Bot token to authenticate API requests.
3. **Save** - Click to establish the connection with the provided credentials.

#### **Additional Settings to** **Push Message**  <a href="#additional-settings-to-push-message" id="additional-settings-to-push-message"></a>

1. **Bot Token** - Select a connection to authenticate the LINE bot.
2. **User ID** - Enter the recipient's user ID obtained from the webhook payload.
3. **Text** - Provide the message content to be sent to the user.

#### **Additional Settings to** **Custom API Call** <a href="#additional-settings-to-custom-api-call" id="additional-settings-to-custom-api-call"></a>

Send a custom API call to a specific endpoint

1. **Bot Token** - Provide the LINE Bot token for authentication.
2. **URL** - Enter the API endpoint URL for the request.
3. **Method** - Select the HTTP method (GET, POST, etc.) for the API call.
4. **Headers** - Add request headers for API authentication or configuration.
5. **Query Parameters** - Specify query parameters for the API request.
6. **Body** - Input the request payload (JSON format) for the API call.
7. **No Error on Failure** - Skip errors and continue the workflow when enabled.
8. **Timeout (in seconds)** - Set a timeout limit for the API call execution.


---

# 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://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/line-bot.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.
