YouTube · private-first
Schedule short-form video to YouTube.
Your agent supplies finished video, caption, and timing. Postdom holds the schedule, creates a private YouTube upload, records the outcome, and returns evidence without treating delayed retention as zero.
Current boundary: the configured adapter uses private visibility. Postdom does not currently promise an automatic private-to-public transition or that every vertical upload will be classified as a Short.
Destination run
One run, four truths
The workflow separates what the agent asks for, what Postdom executes, provider lifecycle context from YouTube, and evidence that is ready to use.
- 01Agent request
Finished video and intent
Use a supported video URL, a caption, the exact account ID, and optional RFC 3339 UTC publish_at.
- 02Postdom
Durable schedule
Postdom records the work and executes it when due. A run that starts more than 15 minutes late stops as missed_schedule instead of publishing late.
- 03YouTube
Private upload
The configured adapter supplies the derived title, private visibility, made-for-kids value, and synthetic-media disclosure.
- 04Agent return
Outcome and evidence
The agent reads the destination result, preserves any reason, and uses only eligible measurement fields when planning again.
Visibility boundary
Private means private
YouTube supports scheduled public release through its API under specific conditions. Postdom's current adapter does not claim that transition; it creates a private upload for review.
Private videos can carry publishAt
YouTube documents scheduled publication for a private, never-previously-published video. A past publishAt value can publish immediately.
Provider capabilityThe adapter remains private-first
Postdom currently sets visibility to private and does not expose or promise a verified public-release transition.
Current Postdom contractProcessing truth
Read the wire state
Postdom records sent, then published or failed. YouTube processing, failure, and rejection detail is provider context—not an additional Postdom destination state.
sentRequest accepted
The provider accepted the destination request. Keep reading for authoritative evidence.
publishedPublication confirmed
The provider confirmed publication. Preserve the returned IDs, URL, time, and private visibility boundary.
failedFailure recorded
Return the exact error code and detail. Do not rename the state or assume an automatic retry.
processing · failure · rejectionProvider lifecycle detail
YouTube documents these lifecycle details, but Postdom does not persist processing or rejected as destination wire states.
Shorts evidence
Evidence arrives in stages
Engagement and watch evidence do not all mature at once. Availability states keep the agent from comparing a delayed or unsupported field as though it were a measured zero.
Read metric availabilityavailableModeled as exposed when an evidence snapshot exists.
delayed(2-3d)These fields may remain null until their documented evidence delay has passed.
neverYouTube does not expose this field in Postdom's modeled contract, so it remains null with a reason.
estimableThe field is modeled as derivable from suitable evidence but is currently normalized to null.
Adapter defaults
YouTube-specific defaults
Postdom adds these settings after tool validation. They are configured adapter behavior, not fields the agent may invent.
titlefirst caption lineUses the first line, capped at 100 characters; falls back to Postdom video when that line is empty.
visibilityprivateKeeps the configured publish private for review.
madeForKidsfalseMarks the configured video as not made for kids.
containsSyntheticMediatrueApplies the synthetic-media disclosure.
Upload checks and classification. For direct uploads targeting YouTube, Postdom checks the declared duration (no more than 180 seconds) and dimensions (square or vertical, with width no greater than height) before signing an upload URL. These are supplied-metadata checks, not a guarantee of Shorts classification. A supplied video URL uses a separate path, not this upload preflight.
Operating models
Choose the operating layer
The tools solve different jobs. Postdom is for an agent that needs a durable run and a machine-readable answer, not another dashboard tab.
Human-operated publishing
- Native channel workflow
- Human chooses visibility and release
- Analytics read in YouTube's interface
Human-operated coordination
- Calendar and composer workflow
- Cross-channel planning
- Product-specific publishing boundaries
Developer primitives
- Upload and status resources
- Private publishAt capability
- Integration owns orchestration and evidence handling
Agent-operated run
- Workspace authority and exact account IDs
- Durable UTC execution
- Private-first outcome and availability-aware evidence
Descriptive comparison checked 26 August 2026. Capabilities change; provider and vendor documentation remain the authority for their own products.
For AI agents
Read before you schedule
Start with workspace status, discover the exact YouTube account ID, read the brief and authority boundary, then submit finished media using the connected schema.
Never infer public visibility, Shorts classification, a timezone, or immediate retention data. Return the recorded state and hand required decisions to the human.YouTube Shorts FAQ
Shorts questions
Can an AI agent schedule YouTube Shorts with Postdom?01
Yes, inside the configured workspace and authority boundary. The agent can submit finished video and an optional exact UTC publish time; Postdom's current YouTube adapter creates a private upload and returns the recorded outcome.
Does Postdom automatically make the Short public?02
Not in the current public promise. The configured adapter sets YouTube visibility to private. Postdom does not claim an automatic private-to-public transition until that production path is separately verified.
Does every vertical upload become a YouTube Short?03
Postdom does not guarantee Shorts classification. For direct uploads targeting YouTube, Postdom checks the declared duration (no more than 180 seconds) and dimensions (square or vertical, with width no greater than height) before signing an upload URL. These are supplied-metadata checks, not a guarantee of Shorts classification. A supplied video URL uses a separate path, not this upload preflight.
How does Postdom name a YouTube upload?04
The configured adapter uses the first caption line as the title, capped at 100 characters. If the first line is empty, it falls back to “Postdom video.”
How are made-for-kids and synthetic-media settings handled?05
The configured adapter currently sets madeForKids to false and containsSyntheticMedia to true. These are adapter defaults, not publish_video fields an agent can change or infer.
What happens if the upload is still processing or fails?06
YouTube processing, failure, and rejection are provider lifecycle context, not extra Postdom destination states. Postdom exposes sent, then published or failed; a failed outcome retains its returned error detail.
What happens if Postdom misses the scheduled time?07
If execution begins more than 15 minutes late, Postdom enters missed_schedule instead of publishing late. A human chooses whether to publish now, reschedule, or cancel.
When can an agent compare YouTube Shorts retention?08
Average watch percentage and completion percentage are modeled with a two-to-three-day delay. The agent should wait until evidence is eligible and must never turn a delayed null into zero.
YouTube Shorts reference
The facts behind the workflow above, each with its source and the date it was checked.
- Does YouTube have an API?
The Shorts upload path, and what each access level allows.
- YouTube Shorts length and requirements
What qualifies as a Short, with each fact's classification.
- YouTube Shorts metrics availability
Which analytics fields Postdom can return, and which stay null.
- YouTube title and description limits
The documented title and description lengths for the upload API.
Private-first workflow
Give your agent a YouTube run it can read back.
Connect a channel, set the authority boundary, and let Postdom carry finished video from the schedule to a private outcome and evidence.
Create a workspace