The difference between a workflow you build for yourself and one you hand to a client (or sell as a template) is not the logic. It is how many places the next person has to touch to make it theirs. The answer should be one.
The pattern
Second node in every workflow, right after the trigger: a Set node named CONFIG - Edit Me. It holds every buyer-specific value as named fields:
owner_emailsheet_idsheet_tab-
reply_subject,reply_body - API keys, URLs, timing values
Every downstream node references them: {{ $('CONFIG - Edit Me').item.json.sheet_id }}. Nothing is hardcoded anywhere else on the canvas.
Why it works
For clients: you screen-share once, fill in one node together, and they feel ownership instead of confusion. Support tickets drop because there is exactly one place to look.
For templates: the buyer setup becomes "edit this node, add your credentials, done" instead of a scavenger hunt across 30 nodes.
For you in six months: you open an old workflow and immediately see every assumption it makes, in one place, with labels.
Implementation notes
Use the Set node in manual mode with merge behavior (keep incoming fields, add config fields). Prefix names to avoid collisions with trigger data: cfg_sheet_id beats sheet_id when a webhook might also send a field called sheet_id.
For secrets like API keys, CONFIG is fine for templates (the buyer pastes their own key), but for client work prefer n8n credentials where the node supports them. CONFIG is for values, credentials are for secrets.
Pair it with a sticky note titled BUYER SETUP listing numbered steps: what to fill in CONFIG, which credential each node needs, how to test. The sticky note is the documentation most people will actually read.
What not to do
Do not split config across five Set nodes "for organization." Do not hide config inside expressions. Do not name it "Set1." Future you is a stranger; write for strangers.
All five workflows in my automation template pack use this pattern, which is why buyers can set each one up in about 10 minutes. Here it is if you want to see it in production workflows.
