Thirty posts in one run: how bulk processing works
Thirty identical tasks means doing the same thing thirty times, and by the twentieth the mistakes start from sheer monotony. Turning it down feels wasteful: the job is large and it repeats. Below is the block that solves it entirely, and the honest limits of where it applies.
Thirty identical tasks means doing the same thing thirty times, and by the twentieth the mistakes start from sheer monotony. Turning it down feels wasteful: the job is large and it repeats. Below is the block that solves it entirely, and the honest limits of where it applies.
---
Thirty identical tasks means doing the same thing thirty times
A client sends a content plan for the month. Thirty subjects, each needing a carousel.
Or a list of forty products, each needing a listing. Or twenty items, each needing a description and three images.
The work is not difficult. It is identical, and that is the whole problem: repeating one sequence of actions thirty times.
Somebody does that for two days and by the twentieth item starts making mistakes from monotony. And turning a job like that down feels wasteful: it is large and it repeats.
There is a block that solves it entirely.
What an iterator is
A block that runs a section of a chain for every element of a list.
You assemble the scheme once — how one carousel gets made. Then you supply a list of thirty subjects and the iterator runs that scheme thirty times, substituting the next element each time.
One run. Thirty results.
The largest template in the section is built exactly on that: a month of carousels from a content plan — 129 steps. That is not complexity, it is scale: a base scheme multiplied by an iterator.
What can be run as a list
Practically anything done identically.
Content to a plan. A list of subjects in, posts, carousels or clips out.
Product listings. A list of items with photos, sets of images and descriptions out.
Variants for testing. One offer, six to nine creatives with different angles of approach.
Adaptation per platform. One visual, every format: feed, stories, banner. Not stretching but recomposing for each.
Processing an incoming body of material. A list of reviews, enquiries or transcripts, with an analysis of each.
Personalisation. A list of clients, a letter or a proposal for each.
How to build it properly
The order in which this works first time.
Step 1. Debug on one
Do not start with the iterator. Assemble the chain for one element and run it.
Thirty poor results is thirty paid generations wasted. One poor result is one.
Step 2. Find what changes
In the debugged chain, work out what exactly gets substituted from the list: the subject, the product name, the photo, the text.
Usually that is one or two variables. Everything else is constant and stays.
Step 3. Wrap it in the iterator
The repeating section goes inside the block. The list feeds in.
Step 4. Run it on three
Not on thirty. Check on a short list that the substitution works and the results differ as they should.
Step 5. Run the full list
And look at the quote before you run. Thirty runs is thirty costs, and seeing the total in advance is better than seeing it after.
Where bulk breaks
The honest limits, so you are not disappointed.
Sameness of results. Thirty pieces to one scheme can come out indistinguishable. A reader will see one post multiplied thirty times.
How to fix that: build variety into the scheme itself. Different types of hook, different presentations, alternation. The input list has to differ in angle as well as in subject.
Quality at the edges. A scheme debugged on a typical element will stumble on an atypical one. In a list of thirty there will always be two or three that are unusual.
How to fix that: a "condition" block or an AI branch — if an element does not fit the main scenario, it goes down another route.
Checking. Thirty results have to be looked at. That is quick but it is not zero — allow the time.
Cost. Bulk multiplies not only the result but the spend. Do draft runs on cheap models and finals on whichever is needed.
Where the human stays
The rule is the same as everywhere: everything automated except the decision.
An "approval" block goes where your choice is needed: the chain reaches the finished set, stops and waits for confirmation.
Sensible stopping points in bulk processing:
After the first three — to check the scheme works on real data.
Before publishing — if the chain ends by posting to social media.
On atypical elements — if the branch sent something down a different route.
What this changes in money terms
Here is the main practical consequence.
You can take on large jobs. Thirty listings and three are one chain and a different run time. Previously you turned those down or took them and suffered.
Price stops being linear to your time. The client counts by number of units; you spend time on the scheme. The difference is yours.
You gain an offer competitors do not have. Not "I'll make you listings" but "I'll close your whole catalogue in a week". For a seller with a hundred items, that is a fundamentally different conversation.
The price range. By my scrape of 848 listings: marketplace listing images — $245–730 per set, a system or pipeline — $490–1 460, against a $30–75 median for one-off work.
A set and a pipeline are exactly what an iterator produces. Per-item work stays on the bottom line.
And repeatability. A content plan arrives every month; a catalogue grows. A chain assembled once serves a client permanently — and that is a flow rather than a one-off job. In the dataset 20.3% of clients mention a flow explicitly.
What is available on the platform
AI Workflow — an iterator, a loop, a condition, an AI branch, approval. Plus the generation blocks: everything in Gen AI is available as a chain step.
Ready templates with bulk processing: a month of carousels from a content plan — 129 steps, a business package of 13 sections — 86 steps, a film parody — 14, cleaning posts of AI clichés — 10.
Saving in your profile. An assembled scheme stays permanently: open it, substitute a new list, run it.
Nested chains. A debugged production line for one unit becomes a single block inside bulk processing.
The quote before the run and money back for steps not completed. The run continues on the server with the tab closed.
Scheduled runs — the Full plan. If the list gets updated regularly.
Registration is free and opens three days of full Basic access.
Where to start today
One action. Take the last job where you made several identical things and count: how long the first unit took and how long all the rest did.
If the second figure is several times the first, that is exactly the volume an iterator removes.
And from that moment a job for thirty items stops being something you turn down.
---
What the scale looks like in a ready pipeline
The iterator is the mechanic. Here is what it gives on a real example.
The digital department from the automations archive takes subjects from your spreadsheet and runs the full cycle on each: script, hyperrealistic photo, animation into a five-second video, narration, joining with subtitles, publishing.
The scale stated in its description: up to 100 clips a day — simply by filling a spreadsheet with ideas.
The cost is $2.50–3 per clip.
What that changes in your offer to a client. Instead of "I charge $500 for running your account" you offer an unlimited package of short videos. The margin rises because production is not limited by your hours.
And the honest boundary, the same as in the article. A hundred clips identical in scheme will look like a hundred identical clips. Variety gets built into the scheme itself — different types of hook, different angles, alternating formats.
The archive — Make, N8N and Full.
---
What to read next
[Build once, run always](/en/blog/build-once-run-always) — the foundation this gets added to.
[Content gets made while you sleep](/en/blog/content-while-you-sleep) — the next rung of automation.
[Relaunching on a marketplace](/en/blog/marketplace-relaunch) — where bulk is needed most.
[What of this actually sells](/en/blog/what-sells-from-vibecoding) — what volumes you can take on.
[AI agents: what they are and what people pay](/en/blog/ai-agents-guide) — the full guide to agents, with market rates.