Verified compatibility
Linkrium Supported Messaging Networks
This page is generated from the same environment configuration that controls Linkrium’s public channel claims and indexable integration pages.
- Publication date
- Updated
- Reading time
- 1 min read
- Author
- Linkrium Product Team
On this page4 sections
Current public availability#
| Network | Public availability | Connection method |
|---|---|---|
| Linkrium | Not publicly available | Built in — no external account to connect |
| Available | Phone pairing through the configured WhatsApp bridge | |
| SMS | Not publicly available | Device pairing with Google Messages through the configured bridge |
| Available | OAuth connection to a supported mailbox provider | |
| Available | Browser-session handoff to the configured Instagram bridge | |
| Messenger | Not publicly available | Browser-session handoff to the configured Messenger bridge |
| Available | Browser-session handoff to the configured LinkedIn bridge | |
| Microsoft Teams | Available | Microsoft OAuth authorization for one-to-one Teams chats |
| Telegram | Available | Phone verification and Telegram account authorization |
| iMessage | Not publicly available | Direct connection to a BlueBubbles server on your own Mac, signed in to your Apple ID |
| Slack | Not publicly available | Workspace OAuth authorization |
| Discord | Not publicly available | Server OAuth authorization |
An “available” label means the environment is configured to offer that connection publicly. It does not mean every provider feature, account type, country, history range, or attachment format is supported.
How this page is kept accurate#
Linkrium uses a build-time public channel registry. A channel-specific landing page is generated only when its required connection is marked available. This prevents search engines from indexing commercial pages for integrations that a new user cannot complete.
Availability can still change when a provider updates its terms, login process, API, or account restrictions. Check this page immediately before connecting an account.
Common limitations#
- History depth depends on the provider and connection settings.
- Native calls and provider-specific administration may remain in the original app.
- Attachments can be limited by size, format, or provider access.
- A provider outage or expired authorization can pause synchronization.
- Connected account and workspace limits can depend on the active plan.
Networks not marked available#
Linkrium does not claim public support for a network simply because its name or icon appears in development code. A network becomes public only after production credentials, end-to-end connection testing, incoming synchronization, outgoing delivery, disconnection handling, and account removal have been verified.
