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.

Works with Claude, ChatGPT, OpenClaw ClaudeChatGPTOpenClaw

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.

How the workflow runs

Connect the account, validate the post, then publish.

01

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.

02

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.

03

Inspect account capabilities and settings

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

04

Validate before apply

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

05

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.

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

Current limitations

A few practical limits to keep in mind.

Related routes

Related integrations and use cases.

What builders are saying

Real quotes from Reddit, G2, Trustpilot, and Instagram.

Works with every major platform

Connect once, then schedule and publish everywhere from the same workspace.

Frequently Asked Questions

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.

Run the Discord publishing API workflow in SocialClaw

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

Supported social platforms
Schedule to social media Works with Claude ChatGPT Codex OpenClaw
Start free