Queues & time slots
Set posting windows per channel
A queueis a set of recurring time slots on a channel. Instead of picking a time for every post, you set the slots once and drop content into “next slot.” This is the fastest way to keep a regular cadence going.
When to use queues
Create a queue
Open the channel's queue settings
Connections → pick a channel → Queue tab.
Add a slot
Click + Add slotand pick a day of the week and a time. OpenPost shows your queue as a weekly grid — add as many slots as you like.
Set the timezone (if different)
Queue timezone defaults to your workspace timezone. Change per-queue when your audience is elsewhere — e.g., a US channel timed for EU mornings.
Save
Changes save automatically. New “next slot” requests use the updated queue immediately.
Next-slot resolution
When you ask for schedule: "next_slot"in the API or pick “Next slot” in the composer, OpenPost runs this algorithm:
- Get all future slots in the queue, sorted by time.
- Remove slots that already have posts scheduled for that channel within ±5 minutes.
- Return the first remaining slot.
- If no slot in the next 14 days, return an error.
curl https://api.openpost.so/v1/integrations/int_abc/next-slot \
-H "Authorization: Bearer $OP_KEY"
Returns:
{
"next_slot": "2026-04-22T14:00:00Z"
}
Handy if you want to show the user when their post will land before they submit.
Multi-channel next-slot
When a post targets multiple channels, “next slot” resolves independently per channel. Each channel gets its next open slot in its own queue. This means the same post might publish at 9am on X and 11am on LinkedIn if those are their respective next slots.
If you want every channel to publish at the same moment, use an explicit schedule_at instead of next_slot.
Blocked slots
You can block specific dates (e.g., holidays, press embargoes) from queue scheduling. Go to Settings → Workspace → Blocked dates. Posts scheduled via next-slot will skip blocked dates automatically.
Deleting a queue
Remove all slots from the queue tab. Posts already scheduled into that queue retain their schedule_at— they’ll still publish. New next-slot requests on that channel will error until you add slots back.