Telegram uses the Bot-connected channel, group, supergroup, or chat route in SocialClaw. Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.
Viral video generator
AI-edited UGC promo videos from your app
Scheduler
Plan and queue posts across 11 networks
AI scheduler
Let an agent pick the slots and write the copy
Management
Accounts, assets, and approvals in one workspace
Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use. SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets.
Works with Claude, ChatGPT, OpenClaw
A quick overview of what this workflow supports.
The main fields and constraints to account for.
Connect the account, validate the post, then publish.
Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.
Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.
Read the current settings surface, including parseMode, disableNotification, protectContent, disableLinkPreview, before generating the final payload.
Validation should happen before create-run or apply. Telegram supports text-only posts or one image or one video per post.
Telegram reconciliation is not implemented yet. Analytics snapshots are available, but Telegram provider-native analytics are not implemented.
Example commands and requests for this route.
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider telegram --bot-token <bot-token> --chat-id @yourchannel --json
socialclaw accounts capabilities --provider telegram --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --jsoncurl -sS \
-H "Authorization: Bearer $SC_API_KEY" \
"https://getsocialclaw.com/v1/keys/validate"
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 @schedule.json \
"https://getsocialclaw.com/v1/posts/validate"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @schedule.json \
"https://getsocialclaw.com/v1/posts/apply"A few practical limits to keep in mind.
Related integrations and use cases.
Real quotes from Reddit, G2, Trustpilot, and Instagram.
“I can prepare the content once and let SocialClaw handle the distribution.”
Instagram
“If SocialClaw sees this just know you changed my entire workflow girl.”
r/mcp
“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”
r/socialmedia
“Most schedulers still feel like old calendar tools with an AI caption button added on top. SocialClaw feels more built around the newer AI era.”
r/automation
“SocialClaw if you want to schedule posts to social media.”
“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”
r/SocialMediaManagers
“I used to use stuff like Buffer etc, but I use SocialClaw with my AI agent. I just tell it to schedule like 100 videos for the next month.”
r/AI_Agents
“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”
r/openclaw
“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”
Connect once, then schedule and publish everywhere from the same workspace.
Telegram uses the Bot-connected channel, group, supergroup, or chat route in SocialClaw. Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.
Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.
Inspect settings such as parseMode, disableNotification, protectContent, disableLinkPreview and capabilities. Telegram does not use OAuth in SocialClaw.
Connect the account once, validate before publish, and keep everything in one workspace.
