> ## Documentation Index
> Fetch the complete documentation index at: https://semantiks.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect

> Deploy your agent through channels, external integrations, and API so users can talk to it wherever they are.

<Info>
  Before connecting your agent, make sure your **Identity**, **Knowledge**, and **Skills** are ready.\
  A well-configured agent gives users better answers from the first conversation.
</Info>

## Connect your agent to real users

The **Connect** page is organized into two tabs:

* **Channels** — connect and manage the channels where your agent talks to users.
* **Messaging Behaviour** — configure how your agent handles messages on each connected channel.

This is the step that turns your agent from "configured" into "live".

***

## Channels tab

The Channels tab is organized in 3 sections:

* **Channels**: publish your agent in owned and external channels (Web Bubble, External Chat, WhatsApp, and others)
* **Integrations**: connect external tools/services used by your operation
* **API**: send and receive messages from your own systems

### External Chat (fastest launch)

**External Chat** gives you a shareable URL you can send in seconds.

<Steps>
  <Step title="Go to Connect > Channels">
    Open your agent and navigate to the Connect page.
  </Step>

  <Step title="Open External Chat">
    Select the External Chat channel card.
  </Step>

  <Step title="Copy the public URL">
    In the **Domain setup** tab, find the **Default URL** card and click the copy button to copy the generated link.
  </Step>

  <Step title="Test as an end user">
    Open the link in an incognito window and run a few real use-case questions.
  </Step>
</Steps>

<Tip>
  You can also connect a **custom domain** so users reach your External Chat at a branded URL like `chat.example.com/ai-agent`. See the [External Chat](/channels/en/web) page for full details on the Domain setup tab.
</Tip>

### Web Bubble (embed in your website)

Use **Web Bubble** when you want the agent inside your own site.

<Steps>
  <Step title="Open Bubble channel">
    In Connect > Channels, open the Bubble card.
  </Step>

  <Step title="Generate credentials/snippets">
    The Console provides the snippet and keys needed for embedding.
  </Step>

  <Step title="Add snippet to your website">
    Paste the script where your implementation team manages site code.
  </Step>

  <Step title="Customize appearance">
    Configure brand settings like launcher style and welcome behavior.
  </Step>
</Steps>

### Meta channels (WhatsApp, Messenger, Instagram)

The Connect page always displays a **Meta** section with three channel cards:

| Channel       | Description                          |
| ------------- | ------------------------------------ |
| **WhatsApp**  | WhatsApp Business channel via Meta   |
| **Messenger** | Facebook Messenger channel via Meta  |
| **Instagram** | Instagram messaging channel via Meta |

Each card shows a **Connect** button that opens the setup flow for that specific channel. You do not need to configure the Meta integration first — the cards are always visible so you can start the connection process at any time.

#### Distribution: Shareable link & Embed bubble

Once a Meta channel is connected, the channel configuration page includes a **Distribution** section titled **"How it works"**. This section lets you share the channel with users in two ways, selectable via a pill toggle at the top:

##### Shareable link

Generate a public URL that opens the same chat flow as the embedded bubble. You can:

* **Add key/value parameters** — use the inline editor on the left to add custom params (e.g. `plan: pro`). Each param is appended to the URL as a query-string parameter and is automatically saved to the end user's `source_params`.
* **Copy the link** — the live URL updates on the right as you add or remove params. Click **Copy** to copy it to your clipboard.
* **Open the link** — click **Open** to test the shareable link in a new tab.
* **Preview source\_params** — when you have at least one param, a preview shows exactly what will be stored on the end user record.

<Tip>
  Use the shareable link in emails, ads, QR codes, or anywhere you want to drive traffic to the chat. Query-string params on the link are captured automatically, so you can tag visitors by campaign, source, or any custom dimension.
</Tip>

##### Embed bubble

Paste a JavaScript snippet into your website to display a floating chat bubble. The snippet is shown in a syntax-highlighted code card on the right. Use the dropdown in the card header to choose between three snippet variants:

| Variant           | Description                                                                                                                                                            |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Static**        | Tag every visitor with fixed key/value params you define in the editor on the left. URL query-string params on the host page are also captured automatically.          |
| **From URL**      | Forward the host page's `?query=string` params automatically. Use the editor to define example params and see a preview of the resulting page URL and `source_params`. |
| **From your app** | Pull values from your own application — user object, dataLayer, etc. The snippet includes placeholder comments you can customize.                                      |

Click **Copy** in the code card header to copy the snippet to your clipboard.

<Note>
  The embed snippet and shareable link always point to the production host (`https://consola.semantiks.com`), so they work correctly even when you're developing locally.
</Note>

<Tip>
  Any parameters you attach — whether via the shareable link, static snippet, or URL forwarding — are saved to the end user's `source_params`. Make sure to add the relevant keys to the **allow-list** in the Source Params card below the Distribution section so they are persisted.
</Tip>