Manage the Telegram routes already linked to this workspace. Shared bot and customer bot are platform-delivered modes. Terminal direct is stored here as a valid Telegram route, but delivery execution stays terminal-origin rather than platform-origin.
No active Telegram route is currently available for this workspace.
| Workspace ID | 0 |
| Plan code | |
| Shared platform bot | Signalator Notify Bot (@) |
| Connect link expires |
Use this to capture the Telegram user and private chat target for the workspace. It is also the default platform-owned Telegram route when no customer bot overrides it.
This stores the customer bot token in secure_config_json, validates it with Telegram getMe, and reuses the Telegram identity already captured by the shared bot connection.
This stores a terminal-origin Telegram route in notification_channels without any platform bot token. It reuses the Telegram target already captured by the shared bot connection and is treated as a valid fallback route when no active platform-delivered Telegram route is available.
| Shared bot | Platform-owned Telegram route. Good default operational path. |
| Customer bot | Platform-delivered but branded or routed through the client-owned Telegram bot. |
| Terminal direct | Stored as a valid Telegram route, but platform execution is skipped. Intended for terminal-origin delivery. |
| Active route selection | Signalator still prefers an active platform-delivered Telegram channel first. Terminal direct stays fallback-only unless no active platform-delivered Telegram route exists. |
| Privacy note | Full, reduced, and stealth are storage and exposure controls, not just message-length presets. |