Same Nodes.
Same Logic.
Different Domain.

Gray showed you what AI does for one creative brief. I want to show you what happens when you have to do that brief fifty times — and what stops being optional.

Why Automate?

Before the tools. Before the canvas. Before any code.
The honest argument for orchestration.

Your Pipeline Has a Tax.
You Just Don't See It.

Every time you open Tool A, do the thing, save the file, open Tool B, do the next thing — you are running a manual orchestrator in your head.

It's invisible because it never shows up in a timesheet. But it's the difference between a studio that scales and one that hires its way out of growth.

€10,000.
Per Person. Per Year.

It does not show up in the P&L. It shows up in burnout. Or in the headcount you keep adding to keep up with growth that should have been absorbed by the system.

A first workflow costs roughly half a day to build. Pays for itself in week three.

The Bottleneck Is Not
the Model Anymore.

Five years ago: "can the AI even do this?" — that was the bottleneck.

Today: the AI does it in two seconds. The bottleneck is everything around the AI call.

Validation. Retry. Multi-format. Cost tracking. Error handling. Delivery. That is where the work moved.

This is not "AI replaces creatives." This is creatives moving up the abstraction ladder, the same way 3D artists did when they stopped painting every frame by hand.

What Is n8n?

A workflow tool, yes. But more usefully: a node graph for anything that has an API.

The tool changes. The abstraction does not.

The structure is identical. Inputs flow in. Nodes transform. Outputs go downstream. You chain logic.

n8n is a visual workflow editor.
Open source. Self-hostable.
500+ pre-built integrations + a Code node.

Trigger → Nodes → Connections → Output

That is the entire mental model. Everything else is variations on those primitives.

Triggers Are Surfaces.

Where your team already lives is where your workflow should listen.

For studio work, "your data, your creds" is the moment n8n stops being a curiosity and starts being the obvious choice.

Your Workflows Become
Agent Tools.

MCP — Model Context Protocol. Anthropic's open standard for letting any LLM call any tool through a uniform interface. n8n is going MCP-native: every workflow you build becomes automatically callable by Claude, ChatGPT, Cursor, any MCP-aware agent.

The workflow you build today becomes a tool an agent uses tomorrow. Same JSON. Same nodes. New caller.

What You Could Build.

The point of this talk is not what I built.
It is the idea of what can be built.

None of these are sci-fi. Every one is a 4-to-15 node workflow. Built once. Runs forever.

Five Patterns Cover
~90 % of What Studios Build.

Once you recognise these five, most studio operations decompose into a list of these workflows.

Same Idea, Four Shapes.

Pick the stage that matches the actual need. Not every workflow needs Stage 4. Most need Stage 3 plus a domain expert. Knowing which one is the consultancy.

What You Should Not Automate.

Automate what you can describe. Stay where you cannot.

A studio that automates everything stops being a studio. The art is knowing where the system stops and the human picks up.

Now Let's See It.

Five live demos. None of them are the goal — they are existence proofs. If this can be done, your version can be done.

Take Gray's three pipelines.
Make them runnable from a phone.
Every week.

5 creative tasks (voice, avatar, lipsync, video, 2D-to-3D). One Telegram bot. n8n in the middle. Same as Gray's tools — Weavy, ElevenLabs, HeyGen, Meshy — wired into a system instead of opened by hand.

This brief is generic on purpose. Replace "creative pipelines" with "your pipelines" and the talk still works.

That message hits a Telegram Trigger node, dispatches to a workflow, calls Together.ai, returns the URL, sends back a photo. Six nodes between your finger and a real provider.

This is the chat-driven pattern from earlier — concrete.

No tutorial. No SDK. Drag, configure, save. Same vocabulary as a shader graph.

I curl the SAME pipeline at clean and at enterprise. Compare the responses. 239 bytes vs ~2 KB. The extra bytes are everything you need to operate at scale.

Never Let the User
Wonder.

In the canvas: provider node red. Error branch green. Notify ran. Respond 502 ran. Workflow finished cleanly even when it failed. This is the moment a structured layer earns its name.

Cloudflare times out at ~100 seconds. Meshy needs three minutes. Submit, poll inside the workflow, deliver the binary when ready. Same pattern works for any slow provider — image diffusers, video gen, batch LLMs, render farms.

Upper layers tell you what is broken, on protocol, in shape. Lower layers vanish. This is the direct argument for going up the ladder.

* clean/quick return 200 with empty body when the provider fails. Structured/enterprise correctly produce a 502 with the upstream error attached.

What You Take
Home.

Find One Manual Loop.

Tomorrow morning, write down a thing in your studio someone does more than once a week. Same shape, same tools, slightly different inputs.

That is your first workflow. Sketch it as nodes on a piece of paper. Webhook → Set → HTTP → Respond. Build it Saturday afternoon. By Monday it runs itself.

You do not need 24 workflows. You need one that you stop doing by hand.

An AI workflow has the same structure
as a 3D shader network.

Moving from artist tools to orchestration tools
is not a career change.

It's a tab change.

The Stack

~30 €/month VPS + provider credits. A typical client demo runs under 5 € in upstream API spend.

Davide Lancini

Software Engineer & Tech Lead
Cuadro Group

cuadrogroup.com
linkedin.com/in/davidelancini
@ddd_ai_notify_bot

If you are about to build a pipeline like this and you want a second pair of eyes, find me at the break or on LinkedIn.

Thank You.

Questions?