Buffer-style weekly slot grids with AI in the loop. Drop drafts into the queue tail and Aidelly assigns each one to the next free slot, recycling evergreens when the tail runs dry. Time-zone aware, cooldown-respecting, calendar-visible.
Pick days × times — Aidelly resolves the next free slot for every new queue item.
When the tail runs dry, re-queue published posts in first-out order with a min-gap.
Run a 9am-EST and a 9am-CET queue side by side. DST-correct.
Slot resolver skips windows your per-account cooldown rules forbid.
Re-order the upcoming items randomly for evergreen variety.
Freeze a queue and resume later — slot history is preserved.
Every queue-scheduled post shows its source queue on the event card.
"Add to queue" available on every draft, repurpose output, and chat message.
Queues is the default Automation tab. Click "New queue".
Pick days of the week and times per day. e.g. Mon/Wed/Fri at 9am, 12pm, 4pm.
Add drafts, generated content, or repurpose output to the queue tail. One-click "Add to queue" from any draft.
A cron every 5 min assigns the next free slot. Toggle recycle on if you want it to never go dry.
A scheduled post has one specific publish time. A queue is a repeating slot grid — say "every weekday at 9am, 1pm, and 5pm UTC" — that you drop posts into. Aidelly assigns the next available slot to each item and keeps dripping forever. No more picking times one at a time.
When a queue runs out of fresh items, recycle re-queues your published evergreen posts in the same slots — first-published-first-recycled, with a configurable minimum gap. Perfect for evergreen libraries that keep working without manual top-ups.
Each queue has its own time zone. Slots are evaluated in that zone, so a 9am-EST queue and a 9am-CET queue can co-exist in the same workspace and Aidelly resolves slot times correctly when DST rolls over.
The slot resolver is cooldown-aware. If a queue wants to fire a slot inside a per-account cooldown window, it nudges the publish to the next free slot and logs the skip — so your cooldown rules always win.
Yes — shuffle re-orders the queue tail randomly (great for evergreen rotation), pause freezes the whole queue without losing slot history, and skip removes a single item without disturbing the rest of the queue.
On the calendar with a queue badge per event card, in the activity log with queue/slot context, and on the queue detail page itself — drag-to-reorder the upcoming items.
Drop in posts. Aidelly drips them out forever.