When several new blog posts appear in our RSS feed at once, I want each one scheduled as a ContentStudio social post a few hours apart (e.g. 10:00, 13:00, 16:00) instead of all at the same time.
What is the problem?
My scenario is RSS → Watch RSS feed items → ContentStudio → Create Social Post. It works fine for a single article, but when we publish several at once [e.g. “3–4 on Monday mornings”], every bundle gets the same schedule time, so the posts go out back to back. There are no errors; the scenario runs successfully, but the output bundles all show the same time.
What have you tried so far?
I tried [e.g. using addHours(now; 3) in the schedule time field], but every bundle still gets the same value. [Add anything else you tried.] I’m not sure of the cleanest approach: using the bundle position, an incrementing counter, or a data store that tracks the last scheduled time.
Create public scenario page
In your scenario, use Make’s share option to create a public scenario page and paste the link here. Before sharing, open the page and check that no API keys, workspace names, or private data are visible.
I’m not sure I follow the full logic of the posting schedule here, but it could make sense to add the items from the RSS feed to a Data Store. Then, set up a different scenario on the actual posting schedule you want to use, read the data store items, and post the first item in the queue.
The key question is whether the spacing should continue across separate RSS runs.
For one batch, I’d suggest a fixed start time plus an increasing offset: first article at 10:00, second at 13:00, third at 16:00. Adding the same three-hour offset to every item doesn’t allocate different slots.
If another batch arrives before those posts publish, I’d instead keep a persistent “next available slot” and allocate from that, so the new batch doesn’t reuse existing times.
Do you want posts spaced continuously every three hours, or restricted to particular daily slots? That determines which approach I’d choose.
This way, each bundle arriving into the RSS feed could be triggered Daily at specific times. This setting is in the top-right corner and allows you to control when the scenario runs, even if you receive bundles in real-time.
For spacing bundles within a single run, the bundle position approach is the cleanest — every bundle already carries a built-in Bundle order position value (1 for the first article, 2 for the second, and so on), so you don’t need a counter or a data store for this part.
The reason addHours(now; 3) gave every post the same time is that now is evaluated once per run — every bundle in that run sees the exact same value. Instead, multiply the offset by the bundle’s position:
addHours(now; 3 * (bundleOrderPosition - 1))
That schedules the first article at +3h, the second at +6h, the third at +9h, and so on. If you want fixed slots like 10:00 / 13:00 / 16:00, anchor to a base time first — e.g. setHours(now; 10; 0; 0; 0) — and add 3 hours × (position − 1) to that.
One caveat, building on @Ayub_Shah’s point: bundle positions reset on every run, so this only spaces articles within one batch. If you need the spacing to continue across separate RSS runs, the persistent “next available slot” data store he described is the right tool for that part.