SocialClaw
Schedule content

Schedule YouTube channel uploads with validation before apply.

SocialClaw supports YouTube channel uploads with one video per post, privacy controls, native upload during publish, and inspectable run state after apply.

Account type YouTube channel One video per post
Best fit Developer tools YouTube requires one video per post.

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Account target YouTube channel The route uses a connected YouTube channel inside the SocialClaw workspace.
Media rule One video per post YouTube requires one video asset and SocialClaw uploads the video natively during publish.
Settings privacyStatus, notifySubscribers, madeForKids Inspect YouTube settings before applying the upload.
Inspection Validate, apply, inspect The workflow can inspect run status, post details, and analytics snapshots after publish.

What the payload needs

The main fields and constraints to account for.

  • youtube:channel:<id> target in the workspace
  • One public video URL or SocialClaw-hosted video URL
  • Title and description for the upload
  • Optional privacyStatus, notifySubscribers, and madeForKids settings

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Connect the channel

Start the hosted YouTube OAuth flow and keep the connected channel in the same workspace used by the CLI and API.

Step 2

Upload the video or reuse a hosted URL

Upload the video to SocialClaw or point the payload at a public video URL that the workspace can use for native upload.

Step 3

Validate the schedule

Validation confirms the one-video publish envelope and the current settings shape before apply.

Step 4

Apply the upload

Create the scheduled YouTube post through apply, then inspect the resulting run or post detail.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow Schedule videos on YouTube
socialclaw accounts connect --provider youtube --open
socialclaw assets upload --file ./video.mp4 --json
socialclaw validate -f youtube-video-schedule.json --json
socialclaw apply -f youtube-video-schedule.json --idempotency-key youtube_launch_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":"youtube"}' \
  "https://getsocialclaw.com/v1/connections/start"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -F "file=@./video.mp4" \
  "https://getsocialclaw.com/v1/assets/upload"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @youtube-video-schedule.json \
  "https://getsocialclaw.com/v1/posts/validate"

Current limitations

A few practical limits to keep in mind.

  • YouTube requires one video per post.
  • Community posts, Shorts-specific workflows, playlists, and live-stream flows are not supported.
  • Non-post interaction steps are not implemented.

Related routes

Related integrations and use cases.

Frequently asked questions

What media shape does the YouTube scheduling route require?

The route requires one video asset per post and uploads the video natively to YouTube during publish.

Which settings matter for scheduled YouTube uploads?

Use privacyStatus, notifySubscribers, and madeForKids when the upload needs those controls.

What YouTube workflows are still out of scope?

Community posts, Shorts-specific flows, playlists, live-stream flows, and non-post interaction steps are not supported.

Run the Schedule videos on YouTube workflow in SocialClaw

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