Channel Guides
Loong currently ships 22 public channel surfaces: 5 runtime-backed surfaces and 17 config-backed outbound surfaces. This hub keeps the full matrix visible while the higher-level chooser pages stay compact. Use Channels when you still need the conceptual model first. Use this hub when you already know the surface and want the exact config, command, and support boundary for that one channel. Keep Channel Recipes for representative rollout patterns rather than the full channel inventory.Quick Picks
Use this short list when you want a practical starting point before scanning the full surface matrix below.| If you want… | Start here | Why |
|---|---|---|
| a primary team-chat runtime | Feishu/Lark | webhook and websocket paths are both documented on the shipped runtime family |
| the lightest reply-loop bot | Telegram | it remains the smallest runtime-backed setup path |
| a Cloud API plus webhook runtime | send and serve are both shipped on the same surface | |
| the official enterprise AIBot lane | WeCom | the public docs keep the long-connection contract explicit |
| one-way governed delivery | Webhook or Email | outbound-only delivery stays visible without being marketed as a reply-loop runtime |
Runtime-Backed Surfaces
These are the shipped send plus serve lanes.| Surface | Transport | Send | Serve |
|---|---|---|---|
| Feishu/Lark | feishu_openapi_webhook_or_websocket | feishu-send | feishu-serve |
| Telegram | telegram_bot_api_polling | telegram-send | telegram-serve |
| Matrix | matrix_client_server_sync | matrix-send | matrix-serve |
| whatsapp_cloud_api | whatsapp-send | whatsapp-serve | |
| WeCom | wecom_aibot_long_connection | wecom-send | wecom-serve |
Config-Backed Outbound Surfaces
These surfaces ship direct sends today and keep serve in the catalog without overclaiming a reply-loop runtime.| Surface | Transport | Send | Serve status |
|---|---|---|---|
| Discord | discord_http_api | discord-send | outbound-only |
| Slack | slack_web_api | slack-send | outbound-only |
| LINE | line_messaging_api | line-send | outbound-only |
| DingTalk | dingtalk_custom_robot_webhook | dingtalk-send | outbound-only |
| smtp_imap | email-send | outbound-only | |
| Webhook | generic_webhook | webhook-send | outbound-only |
| Google Chat | google_chat_incoming_webhook | google-chat-send | outbound-only |
| Signal | signal_cli_rest_api | signal-send | outbound-only |
| Twitch | twitch_chat_api | twitch-send | outbound-only |
| Microsoft Teams | microsoft_teams_incoming_webhook | teams-send | outbound-only |
| Mattermost | mattermost_rest_api | mattermost-send | outbound-only |
| Nextcloud Talk | nextcloud_talk_bot_api | nextcloud-talk-send | outbound-only |
| Synology Chat | synology_chat_outgoing_incoming_webhooks | synology-chat-send | outbound-only |
| IRC | irc_socket | irc-send | outbound-only |
| iMessage | imessage_bridge_api | imessage-send | outbound-only |
| Nostr | nostr_relays | nostr-send | outbound-only |
| Tlon | tlon_urbit_ship_api | tlon-send | outbound-only |
Reading Rule
- Start with Channels when you still need to choose between runtime-backed and outbound-only delivery.
- Use an individual guide page when the surface is already decided and you need the exact config and smoke-test path.
- Keep Channel Recipes for representative rollout paths instead of the full surface inventory.
- Keep Gateway And Supervision open whenever the chosen surface is runtime-backed and needs long-lived ownership.