> For the complete documentation index, see [llms.txt](https://help.blinger.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blinger.io/documentation/section-apps/adding-accounts/custom-app.md).

# Custom app

## General information

#### The integration allows you to connect: <a href="#integraciya-pozvolyaet-podklyuchit" id="integraciya-pozvolyaet-podklyuchit"></a>

* your own(or flexible 3rd party) online-chat
* chat in mobile application
* any 3rd party messaging app (if it's not present in tab "Apps")
* chat-bots in messaging apps according to the following scheme " Messaging app - chat-bot - Blinger.io",

to process customer message requests in Blinger.io, Zendesk, Intercom, Kayako or SalesForce.

## Connect Custom app? <a href="#podklyuchit-custom-app" id="podklyuchit-custom-app"></a>

### Step 1. Open the tab Apps and click on "Add new app"

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-Llpe99u5FiBf_oc410Z%2F-LlqAvctzb5OCngjsdci%2Fimage.png?alt=media\&token=b4095bfb-4510-4a53-a27e-c3b5a6583011)

### Step 2. **Select channel Custom app and click on "Add Custom App"**

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-Lm981Kn8OJ7FyAaHu19%2F-Lm9roVGkKfvYEJMBiQM%2Fimage.png?alt=media\&token=481628f1-e94a-4ae0-8d79-45ce3ddaff75)

### Step 3. Set up a**dding the channel** <a href="#adding-the-channel" id="adding-the-channel"></a>

| **Field**           | Type    | Description                               |
| ------------------- | ------- | ----------------------------------------- |
| **Name\***          | varchar | App name                                  |
| **Custom app ID\*** | varchar | Unique App ID                             |
| **Webhook URL\***   | varchar | URL for sending a message from Blinger.io |

### Step 4. Set up sending and receiving messages from end-user <a href="#receiving-messages-from-end-user" id="receiving-messages-from-end-user"></a>

{% hint style="info" %}
The messages arrive in **json-format**
{% endhint %}

**Receiving messages from end-user**

| Field                     | Type    | Description                                                                                                                          |
| ------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **token\***               | varchar | Authorization token. It is passed in the title Authorization: Bearer TOKEN. It is generated upon adding the app in Blinger interface |
| **custom\_channel\_id\*** | varchar | Unique field. Is defined upon adding the app in Blinger interface                                                                    |
| **client\_id\***          | varchar | End-user ID                                                                                                                          |
| **client\_name**          | varchar | End-user name                                                                                                                        |
| **client\_phone**         | varchar | End-user phone number                                                                                                                |
| **info**                  | json    | End-user additional information                                                                                                      |
| **type\***                | varchar | <p>Message type:</p><ul><li>text</li><li>image</li><li>file</li></ul>                                                                |
| **data\***                | text    | Message text or file URL                                                                                                             |
| **echo**                  | boolean | echo message from third-party solution                                                                                               |
| **echo\_outgoing**        | boolean | outgoing echo message                                                                                                                |

### **Sending end-user messages** <a href="#sending-end-user-messages" id="sending-end-user-messages"></a>

| **Field**               | Type    | Description                                                                   |
| ----------------------- | ------- | ----------------------------------------------------------------------------- |
| **token**               | varchar | It is passed in the title Authorization: Bearer TOKEN.                        |
| **custom\_channel\_id** | varchar | Unique field. Is defined upon adding the app in Blinger interface             |
| **client\_id**          | varchar | End-user ID                                                                   |
| **type**                | varchar | <p>​</p><p>Message type:</p><ul><li>text</li><li>image</li><li>file</li></ul> |
| **data**                | text    | Message text or file URL                                                      |

### Step 5. Set up Webhooks <a href="#webhooks" id="webhooks"></a>

You can check the webhooks for incoming and outgoing messages on the app settings page.

Example:

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-LaytOe5FzhRNt6RIS04%2F-Laz4QZLCEb1ks4S6urm%2Fassets--LB1W87r5cFc0hgB5qdy--LayMdAozVVCqfVxbzK9--LayY9rwYgT8OAdOYFvE-image.png?alt=media\&token=af3c8b07-cf34-4d55-ac36-bdbbe9a3d77a)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


---

# 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://help.blinger.io/documentation/section-apps/adding-accounts/custom-app.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.