Publishing Queues in Agorapulse are designed to automate your content distribution so you can maintain a consistent presence without manually scheduling every post. Think of a queue as a lineup of posts that will be published automatically according to the timeslots you define.
Queues are especially helpful when you want to:
Keep a regular flow of content across multiple channels
Organize posts by campaign, theme, or client
Reduce the effort of scheduling posts individually
Free up time to focus on engagement and performance
In this article, we will outline:
Please Note: Queues are available to users on an Advanced or Custom subscription plan.
How to access the Queues feature
In order to access the Queues feature:
Click the Publishing icon in the left-hand navigation bar
Click Library
Click Queues in the left-hand menu
How do queues work in Agorapulse?
A queue works by combining content and timeslots. You add posts to a queue, then set the days and times when that queue should publish. Agorapulse automatically cycles through the content and publishes at the scheduled times.
To understand how queues fit into your publishing strategy, here is the step-by-step flow:
Create a queue: A queue is tied to a specific profile, with rules such as position, skip, and recurrence
Configure timeslots: The queue has defined publishing slots (for example, weekdays at 10 a.m.)
Add content to a queue: Posts are drafted in the Composer, added from the Content Library, or imported in bulk via CSV
Queue order applied: Posts line up according to your settings (manual order, shuffle, or position at top/bottom)
Publishing triggered: At the next available timeslot, Agorapulse selects the top post in the queue
Recurrence or skip rule applied:
If recurrence is enabled, the post re-enters the queue according to its repeat settings.
If a skip rule applies (e.g., “do not publish again within 7 days”), the post waits until it is eligible
Content published: The post is published to the selected profile at the scheduled time
Queue updated: The post either leaves the queue (if one-time) or repositions according to recurrence settings
Queues Best Practices
Segment strategically: Create queues based on content types, campaigns, or audience goals so each one has a clear purpose
Balance cadence: Use timeslots to build predictable publishing rhythms, such as daily tips or weekly announcements
Keep content fresh: Apply skip rules and shuffle to avoid repetition and maintain variety
Pause instead of delete: Use pause when you need to temporarily stop publishing while preserving your content and setup
Leverage duplication: Duplicate queues to reuse scheduling structures for new campaigns or seasonal strategies
Queues Limitations
A queue can contain a maximum of 1,000 posts
A queue can support a maximum of 1,000 timeslots
Recurrence is restricted on X (Twitter) due to their Terms of Service
Queues cannot be scheduled to begin publishing more than one week in the future. They must be initiated with timeslots set by calendar week
Posts cannot be moved between queues belonging to different profiles
Exporting queued content as a CSV is not available