> 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/webchat/como-excluir-uma-conexao-de-webchat.md).
# How to delete a Webchat connection
Permanently delete a Webchat connection from your Hablla, confirming deletion with the keyword requested by the system.
When a Webchat channel is no longer needed, you can **delete it permanently** from your Hablla. This guide shows the full process, from the settings menu to the final confirmation.
{% hint style="danger" %}
**This action cannot be undone.** When you delete the connection, Webchat stops working on **all** the websites where the script is installed, and the channel disappears from your list of connections. Check with your team before proceeding.
{% endhint %}
{% hint style="info" %}
**Do you just want Webchat to stop appearing on a specific website?** If you lost access to the code for that page and just want to disable the widget there, without deleting the channel, see [How to disable Webchat on a website without touching the code](/hablla-docs-en/hablla/settings/connections-and-integrations/webchat/como-desativar-o-webchat-em-um-site-sem-mexer-no-codigo.md).
{% endhint %}
{% stepper %}
{% step %}
### 1. Access the connection you want to delete
**1.1.** Click **Settings** (the gear icon) in the upper-right corner of your screen to open your workspace settings.
**1.2.** In the left sidebar, go to **Connections and Integrations**
**1.3.** Locate the card for the **Web Chat** and open the list of channels.
**1.4.** Click on the **connection you want to delete** to open its settings.
{% endstep %}
{% step %}
### 2. Locate the delete button
Within the connection settings, **scroll to the bottom of the page**. The button **Delete**.
{% endstep %}
{% step %}
### 3. Confirm the deletion
Because this is a permanent action, the system asks for an extra confirmation.
**3.1.** When clicking **Delete**, the system will display a **confirmation keyword** on the screen.
**3.2.** Type the requested keyword exactly into the indicated field.
**3.3.** Click the confirmation button to complete the deletion, as shown in the GIF below:
{% hint style="info" %}
This keyword exists precisely to prevent accidental deletions. If you type something different, the confirmation button will not be enabled.
{% endhint %}
{% endstep %}
{% step %}
### 4. Confirm that the connection has been removed
Go back to **Connections and Integrations** and check whether the channel no longer appears in the Webchat connections list.
If the script is still installed on a website, remember to remove the code snippet from the page or ask whoever has access to the source code to remove it.
{% endstep %}
{% endstepper %}
---
# 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.hablla.com/hablla-docs-en/hablla/settings/connections-and-integrations/webchat/como-excluir-uma-conexao-de-webchat.md?ask=&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.
