Posting time slots

A slot is a time of the week your channels normally post at: “09:00 on Monday, Wednesday and Friday”, “18:30 every day”. Together, the slots make a queue: instead of picking a date, you ask for “the next free slot”.

Setting the slots

Settings → Publishing, first block “Posting slots”: a grid with one row per time and one column per day, Monday to Sunday.

• Add a time opens an hour + minutes picker; the new row has every day checked.
• Unchecking a box removes that day at that time; the cross at the start of a row removes the whole time.
• The text under the title counts the slots of the week (one checked box = one slot).
• Save only shows when something changed; Cancel goes back to what is saved.

The grid is the one of the workspace of the current scope (a picker at the top of the block when you have several): saving writes the same grid on every channel of the workspace. When the channels of a workspace do not all have the same slots (set earlier, or channel by channel through the API), the page says so, shows the first channel’s, and saving aligns them.

Note

Editing the schedule moves no post already scheduled: only the next slot lookups take it into account.

What uses them

Slots are a convenience, not a restriction: you can always schedule a post at a time that is not a slot.

• Create Post asks for the next free slot before opening the composer, so a new post lands on a sensible time instead of now. Schedule on a content card with no planned date does the same.
• The agent (chat or MCP): “put it in the next free slot” → findSlotTool, then it schedules at that date. scheduleSlotsTool reads and sets the slots of a channel or a workspace.
• The Public API: find-slot and posting-times.

The next free slot is the first upcoming slot, in chronological order and only on its checked days, at which no post is already scheduled to the minute. A channel with no slot (or no day checked) has no next slot: Create Post then falls back to a plain time.

Timezones

The grid shows in the workspace’s time zone picked at its top (your browser’s when it has none), in your account’s 12 h or 24 h format. Slots are stored in UTC: a 09:00 slot in Paris in summer is 07:00 UTC, and both the API and the MCP speak UTC; the app converts. See Scheduling and publishing.