Integrations / Telegram

Telegram is not offered

CloudyBot on cloudybot.ai does not ship a Telegram messaging channel. You cannot link a Telegram bot or chat ID in the hosted dashboard, and scheduled duties do not deliver results to Telegram on this product. If you searched for a Telegram connector, this page is the authoritative answer so you do not waste time hunting settings that do not exist.

For the same class of workflows — chat from your phone, proactive alerts, and scheduled summaries — use WhatsApp on eligible paid plans, or stay in the dashboard and email delivery paths documented under scheduled tasks.

Why Telegram is not on the hosted product

CloudyBot’s public integrations focus on channels we operate end-to-end with billing, consent, and support (Twilio WhatsApp, native API skills, and the cloud browser). Telegram appears in some self-hosted OpenClaw gateway setups, but that stack is separate from the SaaS at cloudybot.ai. The integrations hub lists only connectors available to hosted workspaces; Telegram is called out there as not available.

Internal engineering docs may still mention telegram in delivery preference schemas for gateway deployments. Those fields do not surface as a user-facing Telegram link on cloudybot.ai.

What to use instead

• Mobile messaging: WhatsApp (Twilio) — inbound chat from your phone, proactive sends with opt-out compliance, and plan-based monthly caps. Not included on Free; see pricing.
• Primary workspace: Dashboard chat — full assistant, Specialists, skills, and thread memory without a phone channel.
• Scheduled delivery: Cron and Specialist duties can post back to the dashboard thread, send email, or push to WhatsApp where configured. See scheduled tasks docs and targeting a thread for delivery options on hosted accounts.
• Team notifications: Slack and other skills use the Connect + enable pattern under skills docs — distinct from Telegram DMs.

Telegram vs WhatsApp on CloudyBot

Both channels are common in personal automation communities, but only WhatsApp is wired into the hosted product today.

• Hosted signup → phone chat: WhatsApp yes (paid tiers); Telegram no.
• Proactive scheduled pings: WhatsApp yes, subject to opt-out and plan limits; Telegram no on cloudybot.ai.
• Same agent as dashboard: WhatsApp inbound uses the same assistant stack; dashboard remains the canonical UI for all users.
• Self-hosted OpenClaw: Operators running their own gateway may enable Telegram plugins; that path is outside this marketing site and is not a substitute for a cloudybot.ai account feature.

FAQ