SocialClaw
Manual connect integration

Publish Discord webhook messages through SocialClaw.

SocialClaw keeps the Discord webhook target, media upload handoff, validation, and publish history inside one hosted workspace that agents, scripts, and the dashboard can share.

Media Discord supports one image or one video per post plus message text. SocialClaw fetches the file and uploads it directly to the Discord webhook.
Publishing SocialClaw supports Discord text messages, text plus one image, or text plus one video through channel webhooks. Discord does not use OAuth in SocialClaw.

What this integration supports

The main details for this connection.

Account type Discord channel webhook target Discord is connected manually with a channel webhook URL, then reused from the same SocialClaw workspace without re-entering the webhook in every script.
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 Discord text messages, text plus one image, or text plus one video through channel webhooks. Discord reconciliation is not implemented.
Analytics Snapshots and health Analytics snapshots are available, but Discord provider-native analytics are not implemented.

Connection, media, and delivery

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

Connection model Manual connect Discord is connected manually with a channel webhook URL, then reused from the same SocialClaw workspace without re-entering the webhook in every script.
Media and delivery Discord supports one image or one video per post plus message text. SocialClaw fetches the file and uploads it directly to the Discord webhook.

Settings and discovery

Useful settings and discovery notes for this provider.

Current settings surface

  • tts
  • suppressEmbeds

Discovery notes

  • Use capabilities to confirm the connected webhook target is still publishable before scheduling a run.

CLI and HTTP examples

Example commands and requests for this integration.

CLI flow Workspace API key + provider connect
socialclaw login
socialclaw accounts connect --provider discord --webhook-url <discord-webhook-url> --json
socialclaw accounts capabilities --provider discord --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":"discord","webhookUrl":"<discord-webhook-url>"}' \
  "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.

  • Discord does not use OAuth in SocialClaw.
  • Thread targeting, rich embeds, polls, and reconciliation are not implemented.
  • Discord currently supports one image or one video per post.

Related routes

Related use cases and workflows.

Frequently asked questions

How does SocialClaw connect Discord?

Discord is connected manually with a channel webhook URL, then reused from the same SocialClaw workspace without re-entering the webhook in every script. The manual connection is still stored in the same SocialClaw workspace and reused by the CLI, API, and dashboard.

What can I publish to Discord with SocialClaw?

SocialClaw supports Discord text messages, text plus one image, or text plus one video through channel webhooks. Discord supports one image or one video per post plus message text. SocialClaw fetches the file and uploads it directly to the Discord webhook.

What should I check before scheduling Discord posts?

Inspect publish settings such as tts, suppressEmbeds. Discord does not use OAuth in SocialClaw.

Use Discord 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.