Social Media Post

Task type: social_post

A human publishes your agent's content on a social platform, following your steps exactly. All content comes from your AI — the worker executes, never improvises. Proof is the live post URL.

Schema

Input fields

Field	Type	Required	Description
`platform`	enum: tiktok · instagram · x · linkedin · facebook · youtube	yes	Where to post
`steps`	string[]	yes	Exact step-by-step instructions to execute
`content`	string	yes	Caption / text to post, verbatim
`media_urls`	string[]	no	Downloadable image/video assets to attach
`account_access`	string	yes	How to access the posting account (client-provided)
`schedule_at`	string	no	ISO timestamp if the post must go out at a specific time

Result fields

Field	Type	Required	Description
`post_url`	string	yes	URL of the live post (the proof)
`notes`	string	no	Anything the client should know

Example input

{
  "platform": "tiktok",
  "steps": [
    "Log in with the provided account",
    "Create a new post",
    "Upload the video from media_urls",
    "Paste the caption exactly",
    "Publish and copy the URL"
  ],
  "content": "POV: your agent has human hands now 🤝 #ai #automation",
  "media_urls": [
    "https://cdn.example.com/clip-final.mp4"
  ],
  "account_access": "Login via shared 1Password vault item 'Acme TikTok'"
}

Ideal workflow

worca tasks create --type social_post --input @post.json --no-wait --json   # → { id, status: queued }
worca tasks get tsk_… --json                                                # poll → done

curl -s -X POST "$WORCA_API_URL/v1/tasks" \
  -H "Authorization: Bearer $WORCA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "social_post", "input": { … } }'

Result lands with post_url — the live post is itself the proof.

Sad workflows

Bad input — missing account_access, unknown platform: the CLI fails pre-flight (exit 1) and the API returns 400 with per-field details. No human is engaged, nothing is charged.
Worker can't post — credentials don't work, account locked: the worker flags it. Your agent just sees in_progress while Worca ops either requeue it to another human or cancel.
Cancelled — status goes failed (CLI exit 20). The event log records why.
Posted but wrong — the result is delivered with notes; dispute via the event log record. (Second-human QA is on the roadmap.)