> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/connections-and-integrations.md).

# Connections and Integrations

Understand the Connections and Integrations section of Hablla: where you connect your company's service channels and centralize all messages in a single environment.

Here is where you connect Hablla to the **communication channels** of your company. This is where WhatsApp, Email, Instagram, Facebook, Telephony and Webchat start feeding a single support environment.

Each connected channel becomes a **connection** within the platform. From then on, all messages, regardless of where they came from, arrive in the same place, are routed to the responsible department, and can be handled by human support, flows, bots, or AI.

**Where to find it:** access the **Studio**, click the **Settings** (gear) icon in the upper right corner and, in the left sidebar menu, select **Connections and integrations**.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FboEBbNElDuY6KY38vwIW%2Fconnections_central%20(1).png?alt=media&amp;token=3029c714-8350-4a66-afbc-a38bf301f037" alt=""><figcaption></figcaption></figure>

## Available channels

<table><thead><tr><th width="221.72412109375">Channel</th><th>What it's for</th></tr></thead><tbody><tr><td><strong>WhatsApp</strong></td><td>Instant conversations via WhatsApp using the Official API</td></tr><tr><td><strong>Email</strong></td><td>Email support with your own domain and personalized message templates.</td></tr><tr><td><strong>Facebook</strong></td><td>Messages from your Facebook page directly in support.</td></tr><tr><td><strong>Instagram</strong></td><td>Instagram Direct integrated into the same inbox as the other channels.</td></tr><tr><td><strong>Telegram</strong></td><td>Conversations via Telegram.</td></tr><tr><td><strong>Direct Phone Call</strong></td><td>Phone calls made and received within the platform.</td></tr><tr><td><strong>Web Chat</strong></td><td>Support directly on your company's website, with a customizable widget.</td></tr></tbody></table>

## Best practices

* Standardize connection naming. Names like <kbd>**Sales – WhatsApp**</kbd> save time when the number of channels grows.
* Link each connection to the correct department from the start: it is what determines who receives the support.
* After connecting, send a test message through the channel and confirm that the support reaches the expected queue.
* Periodically review the active connections and deactivate those that are no longer in use.

***

{% hint style="info" %}
**Note:** This documentation covers only how the feature works. For information about billing, costs, or commercial terms, refer to the current contract or contact the responsible department.
{% 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://docs.hablla.com/hablla-docs-en/hablla/settings/connections-and-integrations.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.