hermosodocs

Scheduling: queues, approval, evergreen and bulk

Every post here is an ordinary scheduled post. It shows on the calendar, it can be moved or cancelled on its own, it goes through every check a hand-scheduled post goes through, and it can never go out twice. None of this costs credits.

Posting queues

A queue is a set of posting times. Default is the brand's posting times, the ones "Next free slot" and "just queue it" have always used. You can add named queues beside it, each with its own times, its own days and its own channels: a "Weekday mornings" queue for LinkedIn and X, a "Weekend" queue for Instagram.

FieldWhat it is
slotsEvery-day times, 24-hour HH:MM, up to 24.
daysPer-weekday times that replace the every-day ones on that day, for example {"sat": [], "sun": ["11:00"]}. An empty list means no posts that day. Days are read on the queue's own calendar.
timezoneAn IANA name such as Europe/London. A named queue with none follows the brand's.
channelsNamed queues only. A post put in the queue goes to these channels when it names none, and a channel outside the set is refused.

schedule_post with useQueue: "Weekend" takes that queue's next free slot (useQueue: true is the Default queue). set_post_refill with queue points autopilot at a queue's times, and its postingTimes then change that queue. Manage queues with manage_post_queues (list, save, delete), GET/PUT /api/schedule/queues and DELETE /api/schedule/queues/:id, or in the app under Schedule > More > Posting queues. The Default queue cannot be renamed or deleted, and a queue autopilot posts in cannot be deleted until autopilot is pointed elsewhere.

Approval before publishing

With approval on, a scheduled post waits in Needs approval until an admin of the brand approves it. Admins are the account owner and teammates whose role is admin (Team & access). A post that is not approved never goes out: when its time comes it stays in the queue and nothing is sent, and once it is approved it goes out at its time, or right away if that time has passed. A post nobody decides on within a week of its time is marked not posted.

SettingWhat it does
modeall (every channel), channels (only the ones listed) or off.
whoeveryone (the default: admins' own posts wait too) or members (admins' own posts go straight to the queue).
applyToQueuedSwitching approval on also holds posts already scheduled on those channels, and says how many. Pass false to leave them as they are.

Switching approval off never publishes what is already waiting: those posts still need an approve or a reject. A member who edits an approved post sends it back for approval. A rejected post is not published, its reason is shown to the author, and editing it sends it back for approval.

Tools: set_post_approval, list_pending_approvals, approve_post, reject_post. Routes: GET/PUT /api/schedule/approval, GET /api/schedule/approvals, POST /api/schedule/:id/approve, POST /api/schedule/:id/reject. In the app, posts waiting for approval are under Automations > Needs review and on the calendar, and the setting is under Schedule > More > Approval. A new post waiting for approval is sent to the brand's Slack, Discord and webhook alerts (the approvals group, event approval.awaiting).

Evergreen posts

make_evergreen posts something again on a repeat: every N days, weeks or months, up to maxRepeats times. The source is a published post (fromPost, an id from list_published_posts), a Library item (libraryId), or channels with a caption and media. Each repost is its own scheduled post, placed one at a time: the next one is queued after the one before it goes out, so the calendar always shows what goes out next. A repeat keeps its local time across clock changes, and a monthly one from the 31st moves to the last day of a shorter month.

Caption variation is off by default, so a repost uses the original caption. captionVariants is a list of captions used in turn. X refuses the same text twice in a row, so an evergreen post that includes X needs at least two different variants, none of them the original caption, and X cannot keep a fixed caption of its own in the series. A series that is refused at one of its turns (a channel disconnected, a plan limit) pauses and says why. manage_evergreen lists, pauses, resumes and stops series; stopping one also removes its next queued repost unless you pass keepQueued. Routes: GET/POST /api/schedule/evergreen, POST /api/schedule/evergreen/:id/stop|pause|resume.

A different time per channel

schedule_post takes atByChannel: a time for some or all of the channels, for example {"x": "2026-12-01T09:00", "linkedin": "2026-12-01T14:00"}. Channels not named use at or useQueue. Channels that share a time stay one post. Every part is checked before any is queued, so a refusal on one channel queues nothing. The answer lists each post's id and time in posts. In the app, open "Different time per channel" in the composer.

Import from a CSV

import_posts_csv schedules one post per row. Pass the file's link (from upload_file) in url, or its text in csv. The default is a dry run: every row is checked and each problem is listed with its row number, and nothing is created. Run it again with dryRun: false to create the posts. If any row is refused nothing is created, unless you pass skipInvalid: true. Sending the same file again within a day creates nothing a second time. Up to 500 rows and 2 MB per file.

ColumnWhat it holds
textThe caption.
mediaLinks or Library ids, separated by |: one video, or one or more images.
channelsChannels separated by commas.
time or queueWhen it goes out, or the name of a posting queue to take the next free slot in.
timezone, link, titleAs on schedule_post.
text_<channel>, time_<channel>One channel's own caption or time, for example text_x or time_linkedin.

A column Hermoso does not read is refused by name rather than ignored, so nothing in the file is dropped. Values are never rewritten: a row that does not fit a channel is refused with the rule. In the app: Schedule > More > Import from CSV. The route is POST /api/schedule/import.

When Instagram restricts an account for suspected spam

Instagram can restrict posting from an account it suspects of spam. It answers every publish with the same refusal (Meta code 4, subcode 2207051: "We restrict certain activity to protect our community. Tell us if you think we made a mistake.") and waiting does not clear it. When Instagram refuses two posts in a row from the same account this way, Hermoso holds that account's scheduled Instagram posts instead of sending them into the restriction:

Tool: instagram_posting_hold (action: "status" or "resume", optionally account: the Instagram id or @handle). Routes: GET /api/instagram/posting-hold and POST /api/instagram/posting-hold/resume. list_scheduled marks held posts and names the held account. Free.