20 · data
Cap how many items continue — first N only.
When to use it
Anytime a upstream node can return hundreds of items and you only want a sample or a leaderboard.
Writeup
Cap how many items continue — first N only. Anytime a upstream node can return hundreds of items and you only want a sample or a leaderboard.
Step by step — how to wire it
01
Read or receive many items
Sheets / HTTP list upstream.
02
Add Limit
Set max items to 5–10 while testing.
03
Do expensive work after
Limit → HTTP/CRM so you don’t hammer APIs during builds.
04
Raise or remove for prod
When logic is proven, increase N or delete Limit.
How it functions
Max items
Keeps the first N items; drops the rest for this branch.
Cheap guardrail
Put Limit right after reads while developing.
Used for
Used for 1
Safe testing against huge Sheet reads
Used for 2
Top-N digests (first 10 leads)
Used for 3
Preventing accidental fan-out storms
Tips
Limit is not random sampling — it’s first N. Sort first if you need “top” by score.
Combine with Split In Batches when production volume is real but paced.