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

# The schedule keeps running after your agent disconnects.

Your agent hands off finished videos and exact UTC times once. Postdom holds the queue, applies your saved rules, and returns what happened.

If execution starts more than 15 minutes late, Postdom stops the post instead of publishing late.

## One handoff replaces daily posting.

The caller does not need to stay awake, keep a tab open, or return at publish time. Scheduled work remains in the workspace until it runs or returns a clear state.

1. **The agent plans.** It selects connected account IDs, finished media, a caption, and an exact UTC time.
2. **Postdom records.** The request becomes scheduled work inside the workspace rather than a timer inside the agent session.
3. **The rules apply.** Account authority, plan bounds, connection state, and pause are checked before provider handoff.
4. **The outcome returns.** The agent reads the post and each destination instead of treating request acceptance as publication.

## Give the schedule a UTC target.

publish_video accepts an optional publish_at value in RFC 3339 UTC ending in Z. Omit it, and Postdom does not claim an exact scheduled time.

```text
publish_video({
  account_ids: [
    "acct_instagram",
    "acct_youtube",
    "acct_tiktok"
  ],
  media_handle: "pd_media_11111111-1111-4111-8111-111111111111",
  caption: "Three moves that changed our launch",
  publish_at: "2026-09-03T09:00:00Z",
  plan_id: "22222222-2222-4222-8222-222222222222",
  intent: "Publish the approved launch post"
})
```

- publish_video: https://postdom.com/docs/tools/publish-video.md
- Schedules and plans: https://postdom.com/docs/schedules-and-plans.md

## The rules travel with the work.

Every selected account keeps a human-set operating mode. For a multi-account request, the strictest destination governs the whole request; Postdom does not split it into partially authorized publishes.

- Human authority: https://postdom.com/docs/human-authority.md
- Policy overview: https://postdom.com/product/policy.md

## Late work stops.

No approval by the due time becomes missed_approval. Authorized execution that starts more than 15 minutes late becomes missed_schedule. Neither state silently publishes stale work.

- **Due · missed_approval:** No authority. If required approval never arrived, the post stops before provider handoff.
- **+15 min · execution window:** Execution window. Authorized work may begin only while it is no more than 15 minutes late.
- **>15 min · missed_schedule:** Human decision. Postdom stops and returns the exact state instead of silently publishing stale work.

A human chooses publish now, reschedule, or cancel.

## One time. Every selected destination.

The same scheduled request can target multiple connected accounts. Each destination keeps its own publication answer after the due time passes.

The current destination contract covers TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads, and Bluesky. Every destination keeps its own queued, sent, published, or failed answer.

## Schedule from the live contract.

Call get_workspace_status first, inspect the connected schema, use exact account IDs, and provide publish_at only when the human or plan supplied an explicit UTC time.

**Warning:** Never guess a timezone, widen authority, rename a returned state, or claim an exact schedule when publish_at was omitted.

## Scheduling questions

### Can an AI agent schedule social media posts automatically?

Yes. A connected agent can submit finished short-form video with selected account IDs and an optional exact UTC publish_at value. Postdom stores the scheduled work and executes it inside the workspace's saved authority.

### Does the agent need to stay online until the post publishes?

No. The scheduled post remains in the Postdom workspace after the calling agent disconnects. The agent can return later and read the exact post and destination states.

### What happens if approval is not complete by the scheduled time?

Postdom enters missed_approval and does not create a late provider handoff. A human can publish now, reschedule, or cancel.

### What happens if Postdom cannot start an authorized post on time?

If authorized execution starts more than 15 minutes after the stored time, Postdom enters missed_schedule instead of publishing late. A human then chooses publish now, reschedule, or cancel.

### Does every selected account need the same authority level?

No. Each connected account keeps its own human-set mode. When one request targets several accounts, the strictest selected mode governs the whole request; Postdom does not split it into partially authorized publishes.

### Do scheduled posts always need an approved plan?

No. The required authority path depends on the selected accounts' configured modes. Some requests require manual or per-post review, some use an approved plan, and bounded account policy can authorize eligible work.

### Which short-form destinations can an agent schedule through Postdom?

The current destination contract covers TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads, and Bluesky. Provider requirements and measurement availability remain specific to each destination.

## Let the agent plan. Let Postdom keep time.

Create a workspace, connect the accounts, and give your agent a durable place to put the schedule.