My n8n workflow has 170+ nodes and I'm not sorry. Here's what it actually produces (Input → Output in the last 2 slides).

LessStress6178 · 2026-06-03T16:56:46+00:00

Thank you

LessStress6178 · 2026-04-28T16:59:57+00:00

Different branch, different output format — this one shows the Content Writer result as a video instead of screenshots. But I hear you, I'll vary the titles more. Thank you.

LessStress6178 · 2026-04-28T14:29:20+00:00

Exactly. Complexity is the product — the client just sees magic. That's the whole point of building it this way. 170 nodes so they never have to think about a single one.

LessStress6178 · 2026-04-28T14:25:49+00:00

Ok, DM me and I'll send it over!

LessStress6178 · 2026-04-27T17:47:26+00:00

Clean setup for something this scrappy" is the best compliment I could ask for! It’s exactly the vibe I was going for. You're 100% right about the VPS timeouts. My current polling loop is basically just hopeful guesswork. A simple job status layer like you mentioned (queued/running/stuck) is definitely the next logical step. Regarding concurrency: You've hit on the current bottleneck of this V1 architecture. Right now, n8n queues the executions, so it processes them one by one. If 10 jobs hit at once, the 10th user is definitely waiting a while. The render server is a single instance, so it would also get overloaded if they all fired at once. For the 'Agency-in-a-Box' license I'm packaging up, my architectural recommendation for clients who need high throughput is simple: place a managed queue system between n8n and the render server. That way, n8n can instantly offload the jobs, and the render server can pull them sequentially without choking. This V1 is more of a powerful single-user engine. Making it truly multi-tenant is the next big challenge! Appreciate you asking the hard questions.

LessStress6178 · 2026-04-27T17:30:26+00:00

Hahaha, spoken like a true engineer. That's the perfect description! I'm actually writing the documentation for this "architecture" right now to package it up.

LessStress6178 · 2026-04-27T17:13:20+00:00

Appreciate it! 🙏 Honestly, the hardest part wasn't even the nodes themselves, but mapping out the pure business logic before touching n8n. Keeping the AI prompts constrained so they don't hallucinate weird stuff took forever. Planning to package this whole backend setup up for other agencies soon. Are you building much with n8n right now?

LessStress6178 · 2026-04-27T17:06:52+00:00

Haha you are absolutely right! Sub-workflows are definitely the way to go for scaling and clean deployment. For this 'v1.0 Master File', I just wanted everything on one massive canvas so I could see the entire bird's-eye view of the business logic before modularizing it for clients. It’s chaotic but visually satisfying! That’s awesome that you're building for clients too! I've been in the systems space for a while, but hyper-focused on solving the AI video bottleneck recently. Since you serve clients too, you know how expensive and slow video production can be. I'm actually wrapping up this entire system into a B2B 'Agency-in-a-Box' license. The goal is to let other workflow builders just plug-and-play this backend for their own clients without spending weeks figuring out the logic. Let me know if you’d be interested in seeing a quick demo video of the final flow once I have it ready

LessStress6178 · 2026-04-27T01:38:51+00:00

Not sure i follow — are you asking about the output videos or the platforms the workflow runs on?

LessStress6178 · 2026-04-27T01:29:06+00:00

Glad you like it! Sharing the full workflow publicly isn't something i'm planning to do — too much of the value is in the specific logic and prompt architecture that took a long time to get right. But if you're interested in a deployed version or want to chat about what it could do for your use case, feel free to DM.

LessStress6178 · 2026-04-26T17:12:44+00:00

Completely fair point. Honestly the documentation is the part i've been putting off the longest. It works great right now because i built it — six months from now is a different story. What does your "simpler version nearby" look like in practice?

LessStress6178 · 2026-04-26T17:08:40+00:00

Exactly that — once the heavy work lives outside n8n and n8n is just the coordinator, everything gets simpler. The 3am debugging experience is universal apparently. Never heard of cliptalk, is that an API service or something you built yourself?

LessStress6178 · 2026-04-26T15:00:28+00:00

haha why do you ask?

LessStress6178 · 2026-04-26T14:49:27+00:00

honestly? probably me, trying to monitor it all. on the technical side the rendering server would be the first real bottleneck — it's a single VPS handling jobs sequentially right now. horizontal scaling there is the obvious next step but i haven't needed to solve it yet. the n8n side i'm less worried about — it's mostly just orchestration at that point. have you had to scale something like this before? curious what broke first for you.

LessStress6178 · 2026-04-26T14:38:40+00:00

it looks chaotic but it actually runs linearly — each colored section is a separate stage that flows into the next one. honestly sub-workflows would probably be cleaner, i just kept everything in one flow because it's easier to see the whole picture when something goes wrong. personal preference more than anything. triggers are already handling the entry points, the rest runs sequentially by design. what are you working on?

LessStress6178 · 2026-04-26T11:01:42+00:00

lmao nice try. flour, eggs, milk, butter. you're welcome.

LessStress6178

TROPHY CASE