Skip to main content
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.

​
Connect your agent to real users

In the Console, Connect 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
This is the step that turns your agent from “configured” into “live”.

​
1) Channels

Use Channels when you want users to talk to your agent directly from chat surfaces.

​
External Chat (fastest launch)

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

Go to Connect > Channels

Open your agent and navigate to the Connect page.
2

Open External Chat

Select the External Chat channel card.
3

Copy the public URL

Click the share option and copy the generated link.
4

Test as an end user

Open the link in an incognito window and run a few real use-case questions.

​
Web Bubble (embed in your website)

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

Open Bubble channel

In Connect > Channels, open the Bubble card.
2

Generate credentials/snippets

The Console provides the snippet and keys needed for embedding.
3

Add snippet to your website

Paste the script where your implementation team manages site code.
4

Customize appearance

Configure brand settings like launcher style and welcome behavior.

​
External providers (WhatsApp and others)

The same Connect flow also supports external providers through integration-driven channels.
For channel-specific setup details, use the dedicated guides in channels/en/*.

​
2) Integrations

Use Integrations to connect external systems your organization depends on (for example, messaging providers, CRM/helpdesk, or custom operational services). From the user perspective:
  • You enable the integration once for your organization.
  • Then you configure channels per agent.
  • Optional addons can be enabled per channel when available.
This follows the backend integration model (organization integration -> agent channel -> optional addon), but the Console keeps it in a guided UI flow.

​
3) API

Use API when your own backend or app needs to send messages to the agent programmatically. In Connect > API you can create API channels and use the API reference shown in the Console. Typical flow:
1

Create an API channel

In Connect, click Create API Channel.
2

Copy required identifiers

Get the agent_id, channel identifier, and your API key.
3

Send a request

Call the chat endpoint from your backend with user context and message payload.
4

Handle the response

Store conversation identifiers and render the assistant response in your interface.
Keep API keys on your server side only. Do not expose secrets in public frontend code.
  1. Launch with External Chat for quick validation.
  2. Add Web Bubble to your main web property.
  3. Add external provider integrations for your operational channels.
  4. Move to API when you need custom product experiences.