Title: Telegram publishing support - OpenPost Description: See how OpenPost handles Telegram formats, setup needs, limits, and live-test notes. Canonical: https://openpo.st/platforms/telegram Source: [https://openpo.st/platforms/telegram](https://openpo.st/platforms/telegram) [All platforms](https://openpo.st/platforms) Telegram Instance-owned bot; publicly unavailable # Telegram bot mode remains behind the provider readiness gate. Telegram bot mode is not publicly available in OpenPost. It remains blocked until the exact bot configuration and operations have current live certification. This page is for people deciding whether OpenPost fits their Telegram publishing workflow. **Implemented:** Bot paths exist; public connections are intentionally unavailable **Hosted service certification:** No Hosted service provider-format certification claim is current. [Platform guide](https://docs.openpo.st/providers/telegram) Formats and limits ## Different formats, different rules. OpenPost checks the text and media rules for the format you choose. | Format | Text | Media | | --- | --- | --- | | Public availability | Unavailable | Unavailable | ### Provider limits and scope - Every bot operation has an independent readiness gate - Public Hosted availability requires current exact-subject live evidence - No Telegram bot operation is advertised as available today Connect and test ## Set up Telegram in three checks. 1. Operators may configure the instance bot only for controlled development or certification work. 1. Keep public connection, publishing, observation, and analytics operations disabled without current evidence. 1. Use the provider readiness ledger before changing any public availability statement. Known limits ## What can still block a post. - Bot credentials are instance-owned and never belong in workspace data. - An implementation path or configured token is not a readiness claim. - OpenPost exposes no public Telegram bot claim without a current certification projection. **Account requirement:** An instance-owned Telegram bot with a secret webhook and current live evidence for each enabled operation. **Verification:** Do not connect the bot to public accounts until every intended operation passes its readiness gate with current live evidence. ## Use the current callback address, permissions, and media setup. Social network developer pages change. The OpenPost guide lists the settings and checks you need now. [Read the Telegram guide](https://docs.openpo.st/providers/telegram)