Skip to main content

Automations: recycling and RSS

Two automations keep your queue full without manual work. Both create ordinary posts, so they show up in the calendar and the queue like any other post. Neither ever publishes immediately: copies and feed posts are queued at a free slot or saved as drafts.

Evergreen recycling​

A recycling rule copies a post every interval_days:

curl -X POST "https://postboost.co/app/api/$WORKSPACE/posts/$POST_UUID/recycle" \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-d '{"interval_days": 30, "max_runs": 6}'
  • Placement: queue (default) takes each account's next free queue slot; same_time schedules at the original post's time of day; draft only saves a draft.
  • Tag pools: POST /recycling-rules with "type": "tag_pool" and a tag_uuid recycles the published post with that tag that was recycled least recently, skipping posts younger than the interval.
  • Pause and resume: PUT /recycling-rules/{uuid} with "active": false or true. A rule stops by itself after max_runs copies.
  • Run log: GET /recycling-rules/{uuid}/runs lists every copy and every skipped run with its reason.

Copies go through the same guardrails as posts you create through the API: a copy that would repeat a post from the last 24 hours, exceed an account's daily cap, go to a disconnected account or exceed the X allowance is not created, and the run is logged as skipped with the guard's code. X accounts are left out of copies, because X rejects repeated text.

RSS auto-post​

Add a feed and each new item becomes a post for the accounts you choose:

curl -X POST "https://postboost.co/app/api/$WORKSPACE/rss-feeds" \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-d '{"url": "https://blog.example.com/feed", "account_ids": [12], "template": "New on the blog: {title} {link}"}'
  • Feeds are checked every 30 minutes; POST /rss-feeds/{uuid}/poll checks one now.
  • Only items published after you add the feed become posts, each one at most once.
  • mode: draft (default) saves drafts for review; mode: queue places them in the queue.
  • Template placeholders: {title}, {link}, {summary}.
  • Limits: max_items_per_run (1 to 5) per check and 20 posts per workspace per day. After 5 failed checks in a row a feed is retried every 6 hours; last_error says why.
  • RSS 2.0 and Atom are supported. Feeds must be on a public http(s) address.

With a scoped API key, rules and queue-mode feeds need the publish ability; draft-mode feeds need write.