TL;DR
Use HTML node for readable output
You can turn raw workflow data into clean, human-friendly output directly inside n8n.
Avoid JSON line breaks in final results
Instead of dealing with messy \n formatting, render a pretty template you can read and reuse immediately.
Style output with CSS in <style>
Because the HTML node respects CSS, you can build a beautiful final layout without leaving n8n.
Perfect for manual automations and one-offs
When you need to see results and paste them somewhere else, HTML output gives you ready-to-use content at the end of the workflow.
If you have not been using the HTML node in n8n, you really have to start doing that because it's going to take your workflows to the next level.
Unlock the power of n8n's HTML node
The Problem: JSON Output Looks Ugly (and Isn't Copy-Paste Friendly)
The speaker shows a simple n8n workflow that generates YouTube assets (like a thumbnail), but he also wanted to generate a description with a title, tags, and other metadata. The issue was that the output kept rendering with ugly line breaks (the typical JSON formatting style), which made it hard to read and annoying to reuse.
[image: https://media.giphy.com/media/v1.Y2lkPWRlMThkY2U2bnQwNWNlOGZpbzZxbzVkNzEwc3J1eDdvYmhkZ3BzNXk5MGVxaWVwMCZlcD12MV9naWZzX3NlYXJjaCZjdD1n/y1WDIwAZRSmru/200.gif]
"Angry Hate" via Giphy.
Did You Know?
If your workflow output is meant to be read by a human (or pasted into a tool like YouTube Studio), formatting it as HTML can make it instantly usable without exporting elsewhere.
The Fix: Render a Clean "Document" Inside n8n
After a lot of trial and error (including going back and forth with AI), the speaker landed on using an HTML Template node. Once he did, the output rendered exactly what he wanted, and it looked like a clean, readable document directly inside n8n instead of raw JSON.
[image: https://media.giphy.com/media/v1.Y2lkPWRlMThkY2U2aWltZGsyNmQ3NG5saGdhY2ZnbjJveHMwbG42ZWJ1dnY3czBqbDJwaCZlcD12MV9naWZzX3NlYXJjaCZjdD1n/OK27wINdQS5YQ/200.gif]
"Cosmo Kramer Mind Blown" via Giphy.
Why It Works So Well: HTML + CSS (Yes, CSS)
The "best part," as he describes it, is that it doesn't just render HTML; it also respects CSS, meaning you can include a style tag and still get a polished, visually structured output.
Real-World Demo: Copy from n8n, Paste into YouTube Studio
He then copies the formatted output (video titles, descriptions, and tags) and pastes it directly into YouTube Studio. The formatting holds up, so he can remove extra tags if needed and drop the full description right where it belongs — copy, paste and there you go.
Warning
If you paste rich output into external tools, always double-check length limits (for example, YouTube tags) and trim anything that's a little too long before publishing.
When to Use This in n8n
He frames this as especially useful for manual automations and one-off workflows where you want a final output you can immediately use, rather than "set it and forget it." In those cases, having a formatted output inside n8n is the whole point.
Key Terms Mentioned
- n8n: workflow automation platform built around connected nodes
- HTML: markup used to format readable output
- CSS: styling language (can be embedded via a <style> tag)
- JSON: common data format that often displays messy line breaks when viewed raw
Conclusion + CTA
In conclusion, he strongly recommends using the HTML node in n8n because it can produce clean, elegant results you can copy and paste anywhere without dealing with JSON formatting artifacts.
Then he wraps with the usual outro: if you enjoyed it, hit the like, hit the sub, and thanks for watching. 👋🤙
Sources and References
Do you ever struggle with ugly outputs from your automation tools, waste time reformatting, and feel frustrated by clunky designs? 😩