Is n8n Dead?

Is NADN dead? This has been the biggest question that I've been getting over the past couple weeks. Almost 24 hours ago, I made this post in my plus community just basically talking about, are you ready to switch from NAND to cloud code? And I go on about the way that I think about these two different tools. And really, I think that they're just fundamentally different. This post got some really good engagement. So, I went ahead and I read through what everyone's saying. And I wanted to just address this on YouTube and make a really quick video about it. So a little over a year ago when I started making YouTube videos about NINN, it was in hyperrowth mode and it was blowing up and videos were going viral left and right about NAND AI agents. And over the past couple months, myself and tons of other NIN creators have noticed that the NIN video views have been going down. And there is this weird association online with views and value and they're not, you know, one to one. And what you can see right here is over the past 3 months when you compare Claude and Naden on Google Trends, they had been relatively the same. And cloud code came out about a year ago. Naden came out obviously a long time ago. But in the past really year is when it's blown up. But they've been kind of handinand. And all of a sudden lately cloud code has been kind of surpassing NIN when it comes to search interest and YouTube views and stuff like that. But is Naden dead? No. I don't think that Naden will ever fundamentally be dead. They've carved out a really nice corner in the AI automation market and I think that they've built a really good community and their tool is really, you know, solid. The other question I'm getting is I'm a beginner. I'm getting into AI. Which one do I go for? I still think that as a beginner, you want to start with nitn. It's a lot clearer. It's a lot more simple. It's a lot more visual. And even myself a couple months ago when I first started using cloud code, I was pretty confused. But I would consider myself someone who's pretty nen savvy and pretty technically savvy, but I was pretty confused jumping into cloud code and trying to understand, okay, I've got these Python scripts. Now, how do they actually work on a schedule or on a web hook? So my conclusion is NAN will always be a relevant tool. It will always be a leader when it comes to workflow automation and it's going to be highly adopted because of how low the barrier to entry is in order to go build your first workflow or your first AI agent. But the days of any videos on YouTube or on X going viral, those days are over, I think. And as I've been dropping more content, expanding my tool set a little bit, that's caused a little bit of panic in my communities is what I've seen as far as like should I not be learning NAT anymore? Like what should I be doing? And so basically my promise to you guys is that I don't know where the AI space is going. No one does. Even the experts are scared. They don't know how to keep up. There's so much going on. But my promise is I'm going to try to stay as close to it as possible and bring you guys what I think is relevant. So don't think of this as me switching from any to cloud code. They're different. Think of this as me expanding my tool set and hopefully expanding your guys' skills and knowledge onto different tools as well. The real friction point for me and that I'm seeing with a lot of people is deploying. It's super easy to get into cloud code, brainstorm with it, have it do things for you, have it spin up Python scripts, but then when you actually go to deploy it and maintain it over time, that's where it gets a little bit more ambiguous. It's a little bit harder to look at the execution data and figure out exactly what's going wrong. It's a little bit harder to maintain all this kind of stuff. At least where I'm at right now with my understanding compared to Eniden where it's so easy to, you know, instantly just hit publish on a workflow when you're done and you have all these native web hooks coming in and you have all these native triggers and you can see the execution logs and you can store everything in a Google sheet super super easily. It's way more visual versus the codebased mental models which sometimes for me it's harder to contextualize like what's really going on here. And what I've been doing is using cloud code as a teacher. So not every time I'm in cloud code am I building things. Sometimes I'm just setting up these projects where I've got files and it understands me and my business and I'm just using it to help me understand concepts at a deeper level. I love that because I can see what it's doing. I can see what it's thinking about and I can read its trail. And if there's anything it's doing that I'm confused about, I just ask it, "What did you just do there? What happens if you didn't do that?" But right now, I still have a lot of automations running right there in NAND. And I probably just won't switch those over because I can pay, you know, 10 bucks a month or whatever it is for my VPS and just have those automations running and I know they work and I know exactly how they work. Just like how a lot of people that have been using Zapier for years when Nitn comes out, they've been, you know, using Nitnen still, but they still have tons of zaps and they still have those and they're just going to leave them there. Now, I'm not really saying like that's right or that's wrong, but I'm saying like Naden is not dying. So, my 10-minute rule is basically if I have a use case and I could build it in 10 minutes or less in Nit, I'm just going to do it there because I can do it super quickly, I don't have to think as much because at this point it's like muscle memory. And then when I'm done, I just publish it and I'm good. I've already got my error workflow set up. I've already got tracking set up. I'm good. So anyways, I didn't want to make this one too long. I just felt like I had to get this off my chest because I know that a lot of you guys are thinking about this kind of stuff. So anyways, if you enjoyed the video or you learned something new, please give a like. Definitely helps me out a ton. And as always, I appreciate you guys making it to the end of the video. I'll see you in the next one. Thanks guys.