Every guide to advanced automation patterns assumes you've already built a first workflow — this one is for before that. If you've never built one, here's the actual starting point, stripped of every advanced pattern that doesn't matter yet.
Start with one format, not a system
The instinct with automation is to imagine the whole system at once — multiple templates, multiple sources, branching logic. Don't. Pick the single format you already post most often, and build a workflow for just that one. Everything else in this guide assumes you've done this first, building one real workflow rather than sketching an ambitious one.
Pick a data source you can actually check
Before opening the automation canvas, know exactly what data this workflow runs on and how you'd check it by hand — your own account's stats, a price, a weekly total. If you can't describe in one sentence what the source returns, you're not ready to wire an HTTP Request node to it yet. (Full field reference once you are: the HTTP Request node guide.)
Build the shortest possible chain
For a first workflow, resist adding an If node, a Code node, or a second data source — those are real, valuable patterns, but they're not where you start. The minimum real automation is: Trigger (manual) → HTTP Request → Apply Template → Post. Get this four-node chain working end to end before adding anything else.
Design the template before the automation
A workflow with nowhere good to put its data isn't ready. Build the template first — placeholders named clearly, your brand kit applied — the same way you'd design anything by hand (see how template placeholders work). The automation's whole job is filling something that already looks right on its own.
Run it manually, more than once
Keep the Trigger on manual and run the chain a few times against real data, not the same example repeatedly. Look at the actual generated post each time, not just whether the node turned green (see reading the canvas's warning signals). Your bar for "ready" is simple: would you be comfortable if this exact output published without you looking at it first?
Only then, add one thing
Once the basic chain is reliable, add exactly one improvement — a Code node to format a number better, an If node to skip low-value runs, a second template for variety. Adding one thing at a time, and re-testing after each, is what keeps a growing workflow debuggable; adding five things at once is how a first automation turns into a confusing mess before it's even earned your trust.
What comes after this
Once you have one reliable workflow, the patterns in the rest of this series stop being abstract — multi-template fan-out, joining multiple data sources, and 15 ideas for what to automate next all assume the muscle you just built here: source, template, review, publish. The advanced version of automation is this same loop, repeated with more moving parts — not a different skill.