SocialClaw
Manual connect integration

Publish Telegram channels and chats through SocialClaw.

SocialClaw keeps Telegram bot connection, schedule validation, media delivery, and publishing state in one workspace instead of requiring the bot token in every script.

Media Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.
Publishing SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets. Telegram does not use OAuth in SocialClaw.

What this integration supports

The main details for this connection.

Account type Bot-connected channel, group, supergroup, or chat 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.
Auth model Manual connect The manual connection is stored in the same workspace used by the dashboard, API, and CLI.
Scheduling Validate, draft, apply, inspect SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets. Telegram reconciliation is not implemented yet.
Analytics Snapshots and health Analytics snapshots are available, but Telegram provider-native analytics are not implemented.

Connection, media, and delivery

How accounts connect, what media works, and how publishing behaves.

Connection model Manual connect 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.
Media and delivery Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.

Settings and discovery

Useful settings and discovery notes for this provider.

Current settings surface

  • parseMode
  • disableNotification
  • protectContent
  • disableLinkPreview

Discovery notes

  • Use capabilities to confirm the connected Telegram target is publishable and has the expected chat target.

CLI and HTTP examples

Example commands and requests for this integration.

CLI flow Workspace API key + provider connect
socialclaw login
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
HTTP API flow Hosted SocialClaw endpoints
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 \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/accounts"

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 use cases and workflows.

Frequently asked questions

How does SocialClaw connect Telegram?

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. The manual connection is still stored in the same SocialClaw workspace and reused by the CLI, API, and dashboard.

What can I publish to Telegram with SocialClaw?

SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets. Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.

What should I check before scheduling Telegram posts?

Inspect publish settings such as parseMode, disableNotification, protectContent, disableLinkPreview. Telegram does not use OAuth in SocialClaw.

Use Telegram through one hosted SocialClaw workspace

Connect the account once, validate before apply, and keep post plus run inspection in the same workspace used by the dashboard, API, and CLI.