Release notes are already structured the moment an engineer writes them — a title, a summary, a category — which makes changelog-to-social-post one of the more natural fits for automation, if you filter it well.
The chain
Trigger — a timer polling your changelog or release feed, or a webhook-style check against your docs tool's API if it exposes recent entries.
HTTP Request — pulling the latest entry's title, summary, and category (feature, fix, improvement) from whatever system holds your release notes.
If node — filtering to releases actually worth announcing publicly. Not every patch needs a post; see If node branching recipes for structuring a "is this major enough" gate.
Custom Agent node (optional) — turning terse, engineer-written release text into a caption a general audience would actually read, rather than posting raw changelog language verbatim. See prompting the Custom Agent node for getting tone right here specifically.
Apply Template — binding the release title and rewritten summary into your saved design.
Post — publishes to Instagram; see the exact node setup.
Why the filter matters more here than in most formats
A SaaS product can ship dozens of small changes a month that are genuinely important to build but not remotely interesting to a general audience — "fixed a rare race condition" is real engineering work and a bad public post. The If node's job is separating "shipped" from "worth telling people about," and getting that filter wrong in either direction either floods the account with technical noise or means real, exciting features never get announced because the automation was too conservative.
Where a Custom Agent node earns its place
Changelog text is written for engineers reading a changelog, not for someone scrolling Instagram — the raw phrasing rarely works as a caption unmodified. A Custom Agent node with a prompt aimed at translating "what changed" into "why you'd care" is doing real work here, not a cosmetic step, which is different from formats where the raw data is already caption-ready.
The honest limit
This works well for releases that map cleanly onto "new feature" or "notable fix" — it works less well for the kind of nuanced, multi-part release that genuinely needs a person to decide what's worth leading with. For those, manual is the more honest choice than forcing a complex release into a template built for simpler ones.