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
Open it from the Campaigns tab
Add at least two posts
Note
Set the cadence and start it
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
Note
Tip
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.
- 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
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.