SocialClaw
GitHub Dashboard
Publishing API

Discord publishing API with one SocialClaw workspace.

Discord is connected manually with a channel webhook URL, then reused from the same SocialClaw workspace without re-entering the webhook in every script. SocialClaw supports Discord text messages, text plus one image, or text plus one video through channel webhooks.

Try the CLI Open dashboard
Account type Discord channel webhook target Discord supports one image or one video per post plus message text.
Best fit AI agents Discord does not use OAuth in SocialClaw.

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Account target Discord channel webhook target SocialClaw supports Discord text messages, text plus one image, or text plus one video through channel webhooks.
Auth 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 envelope Discord supports one image or one video per post plus message text. SocialClaw fetches the file and uploads it directly to the Discord webhook.
Inspection Validate, apply, inspect Analytics snapshots are available, but Discord provider-native analytics are not implemented. Discord reconciliation is not implemented.

What the payload needs

The main fields and constraints to account for.

  • Discord channel webhook target stored in the SocialClaw workspace
  • Discord supports one image or one video per post plus message text.
  • Provider-specific settings such as tts, suppressEmbeds
  • Workspace API key auth and post or run inspection after apply

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Authenticate the workspace

Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.

Step 2

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.

Step 3

Inspect account capabilities and settings

Read the current settings surface, including tts, suppressEmbeds, before generating the final payload.

Step 4

Validate before apply

Validation should happen before create-run or apply. Discord supports one image or one video per post plus message text.

Step 5

Inspect the resulting run or post

Discord reconciliation is not implemented. Analytics snapshots are available, but Discord provider-native analytics are not implemented.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow Discord publishing API 
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider discord --webhook-url <discord-webhook-url> --json
socialclaw accounts capabilities --provider discord --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json
HTTP API flow Hosted SocialClaw endpoints 
curl -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":"discord","webhookUrl":"<discord-webhook-url>"}' \
  "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"

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

Integration
Discord 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.
Use case
AI agents Use one SocialClaw workspace for AI-agent account connection, hosted media handoff, validation, apply, and publish inspection.
Product
Pricing Trial and plan details for CLI or API execution
Product
AI agents overview Main SocialClaw page for AI-agent publishing

Frequently asked questions

What account type does the Discord publishing API route use?

Discord uses the Discord channel webhook target route in SocialClaw. Discord is connected manually with a channel webhook URL, then reused from the same SocialClaw workspace without re-entering the webhook in every script.

What media rules apply to the Discord publishing API route?

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 the workflow inspect before applying Discord posts?

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

Run the Discord publishing API workflow in SocialClaw

Connect the account once, validate before publish, and keep everything in one workspace.

Try the CLI Open dashboard