Schedule Telegram bot posts from one workspace-stored bot target.
SocialClaw supports Telegram bot posting into channels, groups, supergroups, and direct chats through one workspace-stored bot target, with text-only or one-image or one-video messages.
What SocialClaw supports for this workflow
A quick overview of what this workflow supports.
What the payload needs
The main fields and constraints to account for.
- telegram:@username or telegram:chat:<id> target in the workspace
- Message text with zero or one image or video asset
- Optional parseMode, disableNotification, protectContent, and disableLinkPreview settings
- Validation before apply
How the workflow runs
Connect the account, validate the post, then publish.
Store the Telegram target in the workspace
Connect Telegram manually with the bot token and chat id or @channelusername so later runs reuse the stored target.
Prepare message text and one optional asset
The current route supports text-only messages or message text plus one image or one video.
Validate the publish shape
Validation confirms the bot target, the current settings envelope, and the one-asset limit before apply.
Apply and inspect the run
Create the scheduled Telegram post and inspect the resulting post or run after publish.
CLI and HTTP examples
Example commands and requests for this route.
socialclaw accounts connect --provider telegram --bot-token <bot-token> --chat-id @yourchannel --json
socialclaw validate -f telegram-schedule.json --json
socialclaw apply -f telegram-schedule.json --idempotency-key telegram_ops_1 --json
socialclaw runs inspect --run-id <run-id> --json
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"telegram","botToken":"<bot-token>","chatId":"@yourchannel"}' \
"https://getsocialclaw.com/v1/connections/start"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @telegram-schedule.json \
"https://getsocialclaw.com/v1/posts/validate"
Current limitations
A few practical limits to keep in mind.
- Telegram does not use OAuth in SocialClaw.
- Channels require the bot to be an administrator or creator.
- Replies and threaded Telegram interactions are not implemented.
Related routes
Related integrations and use cases.
Frequently asked questions
How is the Telegram target connected?
Telegram is connected manually with a bot token and a chat target such as @channelusername or a numeric chat id.
What post shapes does the Telegram route support?
The current route supports text-only posts or text plus one image or one video.
What Telegram behaviors are still out of scope?
Replies and threaded Telegram interactions are not implemented.
Connect the account once, validate before publish, and keep everything in one workspace.