Social Media

Keep posting with an evergreen queue

A pool of posts worth repeating — service times, a welcome, the giving link — that Hubl cycles through on a cadence you set.

Some posts are worth making once and sending many times: what time your services are, where to park, how to give, what a first visit is like. An evergreen queue holds those in a pool and works through them on a cadence, so your Page keeps a pulse between the events you actually promote.

Build the queue

1

Open it from the Campaigns tab

In the , open Campaigns and choose Create a queue (or Manage queue if one already exists). Give it a name you will recognise later, like “Welcome & info”.
2

Add at least two posts

Add a post opens the normal composer, minus the date and time — a pool entry has no clock of its own. Choose Facebook, Instagram, or both. Choosing both makes one shared entry: edit its wording, tags or dates once and both networks get the change.

Note

An entry can carry up to ten photos and videos, the same as any other post, and more than one makes a carousel. Any entry going to Instagram needs at least a photo or a video, and a carousel with a video in it can only go to Instagram.
3

Set the cadence and start it

Choose how often the queue posts and at what time of day, then choose Start the queue. The status next to its name reads Running. Each network works through its own share of the pool independently, so the cadence means “how often this network posts”, not a combined rate.
The pool in order. A post going to both networks is one entry; moving it moves it for both.

Tell Hubl when a post is allowed to run

Rotation details inside a pool entry is where you say more than “post this sometimes”.

  • Tags — comma-separated labels such as welcome, giving, vbs, saved in lowercase. They do nothing on their own; the sequencing rules below read them.
  • Start and end dates — limit an entry to a period, both dates included.
  • Recurring months — for content that comes back every year. February through May for VBS, say. Leave the dates blank and pick All year for a post that is always eligible.

Date and month limits both apply when both are set, and both are read in your organization’s timezone.

Keep it from sounding like a loop

Settings on the queue holds the rules that stop the rotation reading like a rotation:

  • Sequencing — avoid consecutive posts carrying the same tag, or set a minimum number of days between them. Rules are measured against each network’s own published history.
  • Spacing — skip to the next occurrence when another post is already going out too close to this one on the same network. Include event and campaign posts, and those get priority.
  • Blackout dates — ranges the queue sits out without advancing its rotation.

Note

If every eligible post would break a sequencing rule, the queue relaxes that rule rather than going silent, and marks the post Sequencing relaxed. It never relaxes date or month limits: a seasonal pool with nothing currently eligible stays active and simply waits.

Note

A post the rotation passes over, because it is out of season or a sequencing rule held it back, is not dropped. It goes out at the first slot it can, ahead of the rest of the rotation. The same goes for a scheduled copy you delete from the Social Hub timeline: its post takes the next slot instead of waiting for the next time around.

Tip

Existing queues have no spacing, sequencing or blackout rules until you add them. If your queue has been running a while and feels repetitive, this is the first place to look.

Check what it is about to do

Coming up shows the next runs, one row per day, with each network's post on its own line.

A post marked Scheduled is already committed. The rest are Hubl's best guess at what comes next.
  • Scheduled — already saved, and it will publish as shown. Editing the pool entry does not rewrite a snapshot that has already been taken.
  • No label — what the queue would pick next, assuming everything publishes and neither the pool nor the schedule changes. Treat it as a forecast.

Tip

One network showing the same post over and over in the projection usually means only one entry is currently eligible for it. Check the month and date limits on the rest — a VBS post restricted to February through May is invisible in September.

Pausing, stopping and failures

Pause holds the rotation; Stop ends the queue and cancels anything it had already scheduled. The pool itself survives both, so restarting does not mean rewriting your posts.

Anyone following the queue hears when one of its posts fails, when an empty queue pauses itself, and when nothing in it is in season. Whoever creates a queue follows it by email and push; use the bell on the queue to follow it yourself, or to change or stop those alerts. If nobody follows it, the organization's administrators get an in-app alert instead, so a failure is never silent. Retry a failed post from the Social Hub timeline, the same as any other — see When a post fails or the account disconnects.

Ready to get your church online?

Start free and add more when you need it.