05 / Messaging channels
Messaging channels
On this page 4
The same assistant, the same knowledge base, the same model policy — on the channel the question came in on. WhatsApp and Telegram are optional feature modules. E-mail is part of every installation. Outlook, the desktop app, cloud storage and MCP are under Integrations.
All three are reached from Manage → Channels. Inbound (/channels) lists the WhatsApp numbers and the Telegram card. Email handler (/channels/email) holds the mailboxes. Chat widgets and Live support sit next to them.
| Telegram | ||
|---|---|---|
| Who sets it up | An administrator, once for the installation | An administrator switches the module on. Each person then connects their own bot |
| Account | One WhatsApp Business account, up to 20 numbers | One BotFather bot per Synaplan account |
| Credential | WHATSAPP_ACCESS_TOKEN in the environment |
The bot token, stored encrypted for that user. It is not an environment variable |
WhatsApp#
Connect Synaplan to the WhatsApp Business API (Meta) for AI-powered messaging:
- Bidirectional messaging — the AI answers on the number the message came in on
- Multi-phone-number support (up to 20 numbers)
- Media handling — images, audio, video, documents
- Audio transcription via Whisper
- Anonymous usage — no signup required for people writing in; verified numbers get higher limits
- An assistant per number — pick the published assistant that answers on WhatsApp, or keep the usual chat routing
Setup in short: create a WhatsApp business account in Meta Business Suite, get an access token from the API settings, set WHATSAPP_ENABLED and the token, and point Meta's webhook at your instance. WhatsApp is a feature module: without the keys the Inbound page shows a needs setup notice and the webhook answers 404.
Full setup guide (tokens, webhook verification, user tiers, troubleshooting): WhatsApp channel here, and docs/WHATSAPP.md in the main repository.
Telegram#
Connect a bot you created in BotFather. The assistant answers in that private chat, and the thread shows up in your Synaplan history.
- Your bot, your account — one bot per person. Anyone else gets one sentence, and nothing is saved
- Text, photos, files, voice messages, videos, locations and polls — replies, created files and received files stay in Synaplan too
- Commands —
/helpin Telegram's menu;/pic,/vid,/tts,/searchand/docstyped in the chat - Disconnect on the same card — the bot stops replying. The chat history stays
Setup in short: an administrator sets TELEGRAM_ENABLED and a public https address (your APP_URL, or TELEGRAM_WEBHOOK_BASE_URL when that differs) and restarts backend and worker. Each user pastes the BotFather token under Inbound → Telegram, opens the pairing link, and taps Start. Without the module the card is absent — there is no placeholder.
Full setup guide (environment, pairing link, commands, troubleshooting): Telegram channel.
Email#
Send an email to Synaplan and get an AI response, with smart context management:
- General inbox — e.g.
[email protected]on the hosted instance - Topic-specific addresses —
[email protected]; the+keywordbecomes a dedicated chat context, keeping related conversations together - Threading — replies stay in the same conversation
- Live mailbox search — in addition to the inbound channel, chat can search any IMAP inbox you connect under Manage → Channels → Email handler, merged with Microsoft 365 results from Connected apps
- Attachments become files — attachments on inbound mail are stored as files on the conversation, so the assistant can read and answer about them
Full setup guide (inbound processing, SMTP for outgoing mail, spam protection): docs/EMAIL.md in the main repository.
More ways to connect#
| Channel | Where |
|---|---|
| Outlook add-in | Synamail |
| Desktop app | Synaplan Desktop |
| Website chat | Widget Integration |
| iPhone and Android apps | Mobile Apps |
| Nextcloud / OpenCloud / ownCloud.online | Plugins & Integrations · Linked platforms |
| MCP clients & servers | MCP Server & Client — Manage → Connections → MCP Servers |
| Claude Code / Anthropic API | Claude Code — Manage → Developer & devices → Coding clients |
| Voice output | Text-to-Speech |
| Microsoft 365, Dropbox, WebDAV, CalDAV, Jira / Confluence | Manage → Connections → Connected apps — Connections guide (main repo) |
| Custom HTTP / OpenAPI tools | Tools & approvals — the Custom tools section of Connected apps |
| Approvals inbox | Tools & approvals — Manage → Automations → Approvals |