Channels are the surfaces your Qor uses to reach users. Telegram, WhatsApp, Slack DM, Discord DM, email, SMS — each is a channel. Qorven supports 20+ out of the box, with consistent setup and a shared unified-chat model.
The catalog
Web UI
The dashboard at
https://your-host. Chat, tools, memory, all in one.TUI
Terminal UI with
/commands. For SSH sessions and keyboard lovers.Telegram
BotFather token. DMs and groups.
Meta Cloud API. Personal + business accounts.
Slack
Slack app + DM + in-channel mentions.
Discord
Discord bot. DMs, servers, slash commands.
Microsoft Teams
M365 bot framework integration.
LINE
Japan / Taiwan / Thailand. LINE Developers.
Signal
Via signal-cli. End-to-end encrypted.
iMessage
Via Blue Bubbles server on a Mac.
Facebook Messenger
Meta Cloud API.
Matrix
Federated, self-hostable.
Mattermost
Self-hosted alternative to Slack.
Feishu / Lark
Asia / Indonesia enterprise chat.
DingTalk
Mainland China enterprise.
WeCom (WeChat Work)
WeChat’s B2B sibling.
Zalo
Vietnam.
Embeddable webchat
Drop a
<script> on any page for an instant Qor chat.IMAP / SMTP. Threaded, subject lines, attachments.
SMS
Twilio.
GitHub
Issues, PRs, comments, check runs.
Generic webhook
Any HTTP client. Custom integrations.
Channel families
Qorven treats channels differently based on family:Chat-family (merges into canonical chat)
web, tui, webchat, telegram, whatsapp, slack DM, discord DM, teams, line, signal, imessage, facebook, matrix, mattermost, feishu, dingtalk, wecom, zalo.Every message lands in the Qor’s single canonical chat, tagged by channel. The web/TUI sees everything; each channel sees only its own slice.Unified chat model →
Non-chat (own sessions)
email, sms, github, webhook.These are genuinely different mediums — email has threads and subject lines, GitHub has issues and PRs, webhooks can be any shape. They get their own sessions and their own rendering.
Core concepts
Unified chat
How chat-family channels merge into one thread per (user, Qor).
Groups vs DMs
How group chats get their own sessions and memory scope.
Routing & overrides
Send VIPs to a different Qor. Route by keyword. Approval-gate by group.
Debounce
How rapid-fire messages get batched so your Qor doesn’t spam replies.
Quotas
Per-tenant and per-channel rate limits. How to raise them.
Setup at a glance
The setup flow is the same for every channel:Get credentials from the provider
Telegram needs a bot token from
@BotFather. WhatsApp needs a Meta app. Slack needs an OAuth app. Email needs IMAP + SMTP credentials. Per-channel pages walk you through each.Add the channel in the UI
Settings → Channels → Add channel. Pick the provider, paste credentials. Qorven encrypts them immediately.
Point the webhook at Qorven
For providers that push events, set the webhook URL to
https://your-qorven/v1/webhooks/<channel>. Use Cloudflare Tunnel or ngrok for dev.Where next
Unified chat deep-dive
Why there’s one Qor and one chat, not many.
Channel routing
Rules for picking which Qor gets which message.
qorven channels CLI
Scripted add / remove / status / test.
Email setup
The most common non-chat channel. Worth its own deep-dive.