2h • General Discussion 💬
When you reuse an n8n stack for a new client… what changes?
Genuine question for agency owners building with n8n + Claude Code right now:
When you clone a workflow for a new client…
What actually changes?
-The API keys?
-The prompts?
-The data source?
-The logic?
All of the above?
Most of us are:
* Building a stack
* Getting it working for one client
* Duplicating it
* Tweaking it
* Shipping
Which is smart.
But here’s the quiet question:
As those tweaks pile up…
Do you actually know what’s different between Client A and Client B?
If Claude’s behavior shifts…
If you refine a prompt…
If you adjust a node to fix one edge case…
Are you upgrading the “template”?
Or just patching one clone?
I’m building in the same ecosystem.
Just noticing that everyone’s focused on getting agents working…
Very few are thinking about how reusable systems evolve or get versioned over time.
Curious how you’re handling versioning across client stacks right now.
I tweak it manually for each client
I maintain one “master” template and update that
Each client version slowly becomes its own thing
Honestly… I don’t really track the differences
We have clear version control across client stacks
0
0 comments
When you reuse an n8n stack for a new client… what changes?
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
1
🔥
+3711
2
🔥
+1338
3
+1192
4
+733
5
🔥
+588
Powered by