# n8n or Claude Code: compare the maintenance of one real workflow

Map what the automation does, where its instructions live and how you would change it before choosing a different tool.

[HTML](https://lukejbyrne.com/library/guides/80-czoke7ls/)
Content language: en
Author: Luke Byrne
Video published: 2026-02-17
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=80-cZOKE7Ls)
Video language: English

## Locate the manual work in the workflow

The February video is an explanation of Luke’s preference after using n8n for AI automations. It argues that manual box-filling becomes a bottleneck when technical creators want AI to help change the whole workflow. The title’s “everyone” is framing, not evidence of a measured community-wide migration.

The manual-box discussion starts at 1:15. Use it to inspect a workflow you already understand: its inputs, individual steps and useful output. Identify where you spend time maintaining configuration, rather than counting nodes and assuming a large graph is necessarily inefficient.

1. Choose one existing automation with an observable result.
2. List the manual configuration and edits it regularly needs.
3. Separate the workflow’s essential behaviour from the particular visual layout used to represent it.

## Compare a code-first representation of the same job

At 2:30 the video discusses creators becoming more technical; at 4:00 it turns to MCP servers. The argument is that code-first tools can offer flexibility and hosting choices while connecting agents to external services. That is a workflow-design argument, not a working migration script supplied by the description.

Ask what a code-first version would need to preserve: inputs, service connections, ordering and failure handling. A shorter prompt is useful only if the resulting workflow still performs the intended task and remains understandable when something goes wrong.

1. Describe the same job as a sequence of actions and expected outputs.
2. Identify which service connections would be provided through MCP or other code.
3. Compare the effort to change and inspect each representation of the task.

## Keep the reasons to retain n8n visible

The final section at 5:10 explicitly addresses when n8n still makes sense. Include that part before making a decision. A familiar visual workflow may remain useful when its operation and maintenance fit the person responsible for it.

The description favours code-first work for SaaS products and flexibility, but supplies no controlled benchmark, customer-sales study or exhaustive feature comparison. The retained scripting resource is https://ailuke.short.gy/80-cZOKE7Ls2. Decide from the specific workflow’s behaviour and maintenance needs rather than treating the title as a universal instruction to replace a tool.

## The takeaway

Compare the same automation’s behaviour and maintenance in both approaches, including the source’s reasons for keeping n8n.

## Workflow resources

- [ailuke.short.gy](https://ailuke.short.gy/80-cZOKE7Ls1)
- [ailuke.short.gy](https://ailuke.short.gy/80-cZOKE7Ls2)

## Chapters

- [0:00 Why I Never Went All-In](https://www.youtube.com/watch?v=80-cZOKE7Ls&t=0s)
- [1:15 The Manual Box Problem](https://www.youtube.com/watch?v=80-cZOKE7Ls&t=75s)
- [2:30 Non-Technical Became Technical](https://www.youtube.com/watch?v=80-cZOKE7Ls&t=150s)
- [4:00 MCP Servers Changed Everything](https://www.youtube.com/watch?v=80-cZOKE7Ls&t=240s)
- [5:10 When N8N Still Makes Sense](https://www.youtube.com/watch?v=80-cZOKE7Ls&t=310s)

## Sources and limitations

Written companion prepared 2 November 2026 from this exact published video description and its chapter sequence. The full recording was not independently watched or transcribed for this article, and the products and reported results were not retested. Checklists are editorial adaptations of the documented workflow. Model availability, interfaces, prices and offers may have changed since publication; use the retained original resources for current requirements.

[Original video](https://www.youtube.com/watch?v=80-cZOKE7Ls)
