Schedule a post
Publish content at a specific future time instead of immediately.
User intents
"Schedule this video for Friday at 6 PM Kyiv time." "Queue this Facebook post for next Monday morning."
Required information
- Everything from Publish now, plus
- A
scheduledAttimestamp in RFC 3339 with a timezone offset (e.g.2026-05-02T18:00:00+03:00).
Preconditions
- An active connection with a valid token.
Tool sequence
Capabilities & channel
get_platform_capabilities and list_connections, as in Publish now.
Create the scheduled assignment
create_assignment with scheduledAt set. Convert the user's wall-clock time + location to a timezone offset before calling.
Verify
get_assignment — confirm status is pending and scheduledAt matches.
Never omit the timezone offset in scheduledAt. "6 PM" without an offset is ambiguous and may publish at the wrong time.
REST alternative
POST /api/v1/assignments with scheduledAt — see the Assignments reference.
Recovery paths
- Wrong time before publish —
update_assignmentto changescheduledAt. - Change of plans — Cancel a scheduled post.
- Billing / token errors — same recovery as Publish now.
Example prompt → result
"Schedule https://cdn.example.com/ep12.mp4 (opens in a new tab) to 'Tech Reviews' for 2026-05-02 at 18:00 Kyiv, public."
Result: a pending assignment with scheduledAt = 2026-05-02T18:00:00+03:00 that auto-publishes at that moment.
Common mistakes
- Timezone-less or past
scheduledAt. - Trying to edit a post after it published — use Update published content instead of
update_assignment.