Scheduling posts
You can queue LinkedIn posts for future publishing and manage the whole queue through Crispy.
Scheduling a post
Pass schedule_at to create_post with an ISO 8601 datetime, for example '2026-03-10T09:00:00Z'. The post is stored as 'pending' and publishes automatically at that time. Datetimes in the past are rejected, so an agent cannot accidentally schedule into yesterday.
Viewing the queue
list_scheduled_posts returns your scheduled posts with their status and scheduled times, 1 to 100 at a time. Every scheduled post is in one of four states:
- pending: waiting to publish
- published: went live successfully
- failed: publishing did not succeed
- cancelled: you cancelled it before it published
Filter by status to see just what is waiting, or just what failed.
Cancelling
cancel_scheduled_post cancels a pending post using its UUID from list_scheduled_posts. Only pending posts can be cancelled; the call fails if the post already published, failed, or was previously cancelled, so you always get an honest answer about what actually happened.
Drafts or scheduling?
Use both. Drafts are for content still being shaped; scheduling is for content that is done and just needs the right moment. A common flow: refine the text in a draft, then put the final version into create_post with schedule_at for a specific slot.
If a scheduled post shows 'failed', it did not go live. Check session health with get_account, reconnect from the dashboard if needed, and schedule it again.