Skip to main content

​
Chat channels

Fased connects to the chat apps you already use through the gateway. Text works everywhere; media, reactions, threads, voice, and advanced actions depend on the channel. For normal browser setup, open Agents, select the Agent, then use Agent > Channels. That page owns channel credentials, QR/login flows, account status, routing to the selected Agent, DM access, allowlists, and restart-required notices. The Control UI Channels tab is split into:
  • Accounts: grouped channel cards and the Connect modal for required fields.
  • Behavior: reply behavior, reactions, group mention behavior, and TTS.
  • Access: command and native-tool access for channel users.
  • Sessions: channel-to-session binding and reset rules.
  • Gateway: web and gateway settings for channel delivery.
Account cards are grouped as Major, Enterprise, Self-hosted/protocol, and Optional/plugin so first-run setup stays focused on the common channels. Every integration page uses one delivery label:

​
Channel map

Common Setup

Start here for WhatsApp, Telegram, Discord, Slack, Signal, or BlueBubbles. These are the fastest practical routes to DMs, groups, and team chat.

Team And Enterprise

Use Google Chat, Feishu, Microsoft Teams, LINE, Zalo, or Zalo Personal for company, regional, or business chat surfaces.

Self-Hosted And Protocol

Use IRC, Mattermost, Matrix, Nextcloud Talk, Synology Chat, Nostr, or Tlon for self-hosted, protocol-native, or private collaboration routes.

Optional And Legacy

Use Twitch for live chat. Use iMessage only for established imsg setups; new iMessage-style setups should start with BlueBubbles.
Common setup: Team and enterprise: Self-hosted and protocol: Optional and legacy:

​
Runtime status

  • Agent > Channels shows available channels, including official add-ons that are not downloaded yet.
  • Telegram, WhatsApp, Discord, Slack, Feishu, and Google Chat show Install on a fresh core install. The Control UI downloads the matching official npm package.
  • Saving credentials enables that channel for the selected Agent.
  • Installed channel add-ons need a Gateway restart before their credential and login flow becomes active.
  • The onboarding wizard and fased channels add can install the same official add-ons before configuration.

​
Good first choices

  • Telegram for fastest public bot setup.
  • WhatsApp for a familiar personal or group assistant.
  • Discord or Slack for team spaces.
  • BlueBubbles for new iMessage-style setups.
  • Matrix or Nextcloud Talk for self-hosted collaboration.

​
Notes

  • multiple channels can run at the same time
  • Telegram, WhatsApp, Discord, Slack, Feishu, and Google Chat are official add-ons; install only the channels you use
  • source-only channels never show an npm Install action; follow their channel page from Open docs
  • external-prerequisite channels require the named app or system tool before Connect can succeed
  • if a channel shows restart required, restart the Gateway before testing live messages
  • routing is deterministic per peer and per channel; see Channel Routing
  • group behavior is documented separately in Groups
  • DM pairing and allowlists are part of the security model; see Security and Pairing
  • fast failure triage starts at Channel Troubleshooting
  • the full core/add-on boundary is in Core And Optional Components