SocialClaw
Schedule content

Schedule Discord webhook posts with one workspace-stored webhook target.

SocialClaw supports Discord channel posting through a webhook URL. The current route supports text-only messages or text plus one image or one video, with SocialClaw uploading the media file to the webhook.

Account type Discord webhook target Text-only, text plus one image, or text plus one video
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 webhook URL Discord is connected manually with a channel webhook URL stored in the workspace.
Media rule One image or one video SocialClaw fetches the media URL and uploads the file directly to the Discord webhook.
Settings tts and suppressEmbeds Inspect the current webhook settings surface before applying the schedule.
Inspection Validate before apply Capabilities and validation help the workflow confirm that the stored webhook target is still publishable.

What the payload needs

The main fields and constraints to account for.

  • discord:webhook:<id> target in the workspace
  • Message text with zero or one asset
  • Optional tts and suppressEmbeds settings
  • Validation before apply

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Store the webhook target in the workspace

Connect Discord manually with the channel webhook URL so later runs do not need the webhook re-entered.

Step 2

Prepare message text and one optional asset

The current route supports text-only messages or one image or one video with message text.

Step 3

Validate the message shape

Validation confirms the webhook target, the one-asset limit, and any current settings such as suppressEmbeds.

Step 4

Apply and inspect the run

Create the scheduled Discord post and inspect the resulting post or run after publish.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow Schedule posts on Discord
socialclaw accounts connect --provider discord --webhook-url <discord-webhook-url> --json
socialclaw validate -f discord-schedule.json --json
socialclaw apply -f discord-schedule.json --idempotency-key discord_ops_1 --json
socialclaw posts get --post-id <post-id> --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 \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @discord-schedule.json \
  "https://getsocialclaw.com/v1/posts/validate"

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.

Frequently asked questions

How does the Discord route connect the target channel?

Discord is connected manually with a channel webhook URL, and that target is stored inside the workspace.

How many media assets can one Discord post include?

The current route supports message text plus one image or one video.

What Discord features are still out of scope?

Thread targeting, rich embeds, polls, and reconciliation are not implemented.

Run the Schedule posts on Discord workflow in SocialClaw

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