> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt

# 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.

### YouTube · conceptual

**Private-first**

Agent submits: **Launch week · 09:00 UTC** — finished media · caption · account ID.

- **Agent input · `media + publish_at`:** Finished video and exact UTC
- **Postdom wire · `sent`:** Provider accepted the request
- **Postdom wire · `published | failed`:** Exact destination outcome

YouTube visibility remains private · Evidence eligibility varies.

- [Create a workspace](https://app.postdom.com/signup)
- [Read the YouTube contract](https://postdom.com/docs/destinations/youtube-shorts)

## 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.

1. **Agent request · Finished video and intent:** Use a supported video URL, a caption, the exact account ID, and optional RFC 3339 UTC publish_at.
2. **Postdom · 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.
3. **YouTube · Private upload:** The configured adapter supplies the derived title, private visibility, made-for-kids value, and synthetic-media disclosure.
4. **Agent return · Outcome and evidence:** The agent reads the destination result, preserves any reason, and uses only eligible measurement fields when planning again.

## The channel stays yours

A human connects the YouTube account and chooses the operating boundary. The agent works inside that workspace without seeing the channel password or expanding its own authority.

- **Human OAuth:** A human completes Google's authorization flow and selects the channel. Credentials stay out of agent chat.
- **Workspace boundary:** The human sets account trust, plan requirements, limits, quiet hours, and pause state.
- **Agent execution:** The agent uses exact workspace IDs and acts only inside the approved plan or account policy.
- **Human exceptions:** Approval, missed_schedule, policy, connection, and visibility decisions return to a human.

## 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.

### YouTube platform capability: Private videos can carry publishAt

YouTube documents scheduled publication for a private, never-previously-published video. A past publishAt value can publish immediately.

### Postdom current behavior: The adapter remains private-first

Postdom currently sets visibility to private and does not expose or promise a verified public-release transition.

Provider capability · Current Postdom contract.

## 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.

- **Postdom wire · `sent` · Request accepted:** The provider accepted the destination request. Keep reading for authoritative evidence.
- **Postdom wire · `published` · Publication confirmed:** The provider confirmed publication. Preserve the returned IDs, URL, time, and private visibility boundary.
- **Postdom wire · `failed` · Failure recorded:** Return the exact error code and detail. Do not rename the state or assume an automatic retry.
- **YouTube provider context · `processing · failure · rejection` · Provider lifecycle detail:** YouTube documents these lifecycle details, but Postdom does not persist processing or rejected as destination wire states.

## 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.

**Measurement group · Agent use**

- **`available` · Available baseline:** Views · likes · comments · shares · watch time. Modeled as exposed when an evidence snapshot exists.
- **`delayed(2-3d)` · Wait before comparing:** Average watch percentage · completion percentage. These fields may remain null until their documented evidence delay has passed.
- **`never` · Keep out of rankings:** Saves. YouTube does not expose this field in Postdom's modeled contract, so it remains null with a reason.
- **`estimable` · No promised value:** Follower delta. The field is modeled as derivable from suitable evidence but is currently normalized to null.

A null is not a zero. Compare only eligible evidence.

## YouTube-specific defaults

Postdom adds these settings after tool validation. They are configured adapter behavior, not fields the agent may invent.

- **`title` = `first caption line`:** Uses the first line, capped at 100 characters; falls back to Postdom video when that line is empty.
- **`visibility` = `private`:** Keeps the configured publish private for review.
- **`madeForKids` = `false`:** Marks the configured video as not made for kids.
- **`containsSyntheticMedia` = `true`:** Applies 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.

## 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.

### YouTube Studio · Human-operated publishing

- Native channel workflow
- Human chooses visibility and release
- Analytics read in YouTube's interface

### Social scheduler · Human-operated coordination

- Calendar and composer workflow
- Cross-channel planning
- Product-specific publishing boundaries

### YouTube API · Developer primitives

- Upload and status resources
- Private publishAt capability
- Integration owns orchestration and evidence handling

### Postdom · 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.

## 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.

- Read the YouTube contract: https://postdom.com/docs/destinations/youtube-shorts.md
- See the authority model: https://postdom.com/product/policy.md
- Read metric availability: https://postdom.com/docs/destinations/metric-availability.md
- Run states: https://postdom.com/docs/reference/run-states.md
- Measurement: https://postdom.com/docs/measurement.md
- Read this page as Markdown: https://postdom.com/platforms/youtube-shorts.md
- Read the agent contract: https://postdom.com/agent-contract.md

## Shorts questions

### Can an AI agent schedule YouTube Shorts with Postdom?

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?

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?

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?

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?

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?

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?

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?

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.

## 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](https://app.postdom.com/signup)