A restock or a drop is one of the cleaner auto-posting cases: the underlying data — is this SKU in stock, has this listing gone live — is usually something your store platform already tracks, which means it's already reachable over an API instead of something a person has to notice and report.
The chain
Trigger — a timer polling your inventory or product feed at an interval that matches how fast stock actually moves for you; a flash-restock item needs tighter polling than a slow-moving one.
HTTP Request — your store platform's inventory or product API, checked for the specific state change (a SKU crossing from zero stock to available, or a new listing appearing).
If node — the filter deciding whether this specific change is worth a post. Not every stock update is a drop worth announcing — see If node branching recipes for structuring this kind of "is this actually notable" gate.
Apply Template — binds the product name, price, and image into your saved template, so the post reflects the actual item rather than a generic restock graphic.
Post — publishes to Instagram; see the exact node setup if you haven't built this chain before.
The filtering decision that matters most here
Ecommerce inventory changes constantly, and not all of it is a "drop" in the sense your audience cares about — a single unit coming back into stock on a staple item is a different event than a genuinely new release. Deciding what counts as post-worthy before wiring the If node saves you from an account that posts every minor stock fluctuation, which trains followers to tune out rather than pay attention. This is the same discipline that makes threshold-based price alerts work instead of becoming noise.
Where this differs from a manual "just post it when it happens" habit
The honest case for automating this specifically over doing it by hand is timing, not effort — a person checking inventory once a day misses same-day restocks that sell out before anyone posted about them. A workflow polling every few minutes catches the window a manual process structurally can't, which is the actual argument for building this one even at a small catalog size.
Start narrow
If you carry hundreds of SKUs, don't wire the whole catalog into one automation on day one — pick the handful of products where restock timing genuinely drives sales, get that working and trusted on manual trigger first, then expand. That's the same starting-small logic that applies to any first workflow, ecommerce or not.