Hi everyone!
About a week ago, I shared my AI-powered Distribution Engine built with n8n. Since then, I’ve made good progress, so I wanted to share a quick update.
New improvements:
• Automated YouTube publishing is now running reliably.
• Every uploaded video now includes a Product Hub link in the description.
• WordPress SEO articles are published automatically.
• Product Hub has become the central destination for all workflows.
• Analytics are helping me measure views, clicks, and user behavior across channels.
Current workflow:
AI → n8n → Google Drive → YouTube
AI → n8n → WordPress
YouTube / WordPress / X → Product Hub
The goal is simple:
Create once, distribute everywhere automatically.
I’m continuing to improve the workflow and reduce manual work step by step.
I’d love to hear your feedback or ideas for future improvements.
Thanks!
2 curtidas
create once, distribute everywhere is the right instinct. what matters more as this scales is that product hub is now a dependency every other node routes through.
two things to stress test:
- what happens to the youtube and wordpress steps if product hub is down when they run, right now that single point probably blocks the whole chain
-
- cross channel analytics, most people underbuild that piece and are back in spreadsheets within a month
- on the distribution layer, decide which platforms genuinely need the full custom treatment and which can just reuse the same asset. thats where a tool like blotato earns its keep, one api call per platform with its own title and privacy settings instead of a custom node per platform inside n8n
1 curtida
Thanks for the thoughtful feedback. I especially agree on cross-channel analytics. That’s the next layer I’m focusing on now: understanding which channels actually drive Product Hub visits and conversions before adding more complexity.
Your point about keeping the distribution layer simple and reusable is also very helpful. I’ll keep that in mind as I expand the workflow.