Build n8n Workflows Without Leaving Your IDE

A lot of people want to stay in their ID of choice. Some people want to use cursor or visual studios and they don't want to hop around from having cloud code create the JSONs and then going back and forth because both ways if I make some modification it's saved here it will be automatically synced back to the local uh TypeScript file and then the agent will have the knowledge of uh all this. Always say please to cl — yeah we want to be nice to those robot overlords. Today we are learning to build NA workflows in cursor cloud code and open claw with n10 as code. If you're building with cloud code, cursor or openclaw, chances are you're still jumping over to inadin to build the actual workflows. You prompting your IDE switch over to inadin, click around and then come back constantly context switching between two or even three different environments. inadin as code fixes that. It's a plugin that brings in directly into your coding environment so you can prompt, build, and iterate on your workflows without ever leaving your IDE. Today, I'm joined by the man who

built it. We're going to see him run it live in Cloud Code, OpenClaw, and Cursor, including a two-way sync where you edit it in N8 and then it updates it in your IDE and vice versa. And because it ships with local knowledge of every NA node and 7,000 NA community templates, the agent builds correctly without hallucinating nodes that don't exist. You can run the whole thing on tiny cheap LLMs. No MCPS needed and installed in two commands. Link in the description. Let's get into it. En welcome to the show. So, what are we learning today? Hi, today we are learning to build N810 workflows in cursor cloud code and open CL with N810 as code. — Fantastic. I would love for you to share

your screen. Let's dive into it. I know this is the new modern way AI engineers build by just chatting with it. So I'm excited to see what you've built. — Sure. So I will share uh my uh cloud code uh command line uh interface and uh so basically I will just uh pass a prompt in it. Uh so a simple prompt

asking uh to uh asking any code to create a workflow uh to uh which will trigger every hour fetch transactions and uh do some stuff you know uh and then we'll see what's uh what is the result. So I just hit enter. I was going to say so it looks like we're going into stripe and we're gonna fetch transactions from stripe and uh put it into Postgress. It's quite a random uh workflow. I mean the goal is to show how the workflow is built by itself. Um the workflow in itself is not really uh something uh but yeah so you can see that cloud start to ask questions. So I will just allow him to read whatever he needs to read and uh he will do his job — asking for credentials. So you have to give it your API key as well as your your websites. So I give him my uh URL. So the it's a local uh N8 instance. Then I can fast my AP key. Don't worry I will crush it later. It's just a local AP key. Okay. And while is uh working um we

could switch to open claw and uh do something uh similar. So we are right now in a in open close. So it's another tab and uh we'll give it another prompt to uh to do another workflow. So now we will create a support ticket. Um so again it's not the workflow that is important but okay we are telling it to have a web book with from zenesk use openai node classify the ticket and so on. So, — got it. Uh, typical support automation that helps us triage use cases of uh basically requests coming in for support that we can then send into Zenesk and then rate them positive, negative, neutral, which I'm sure you could always do additional things on top of it, but it's a big use case for time. — Yeah. Afterwards you can um ask a code or open code to uh to add some nodes to fix some nodes but right now we will just see what it give us uh on the first uh attempt. Um so it's running it's sinking. um what we can do. So here you can see that it got some error so it will autofix um using NA10 ascode ontology. Uh so uh if uh for whatever reason it create a workflow that is wrong with a wrong node or a wrong sha or so on uh it will fix by itself by querying data. — Great. And did you feed it any like inate in skills at all? I know there's innate in skills that are floating around in the marketplace. Have you given it any thoughts? — Uh it's in fact it's a skill in itself

because [snorts] um so NATS code is bundled with some uh tooling in fact uh which is NAC. Uh it's a common line tooling to request whatever you need to know about uh nodes shimmer. uh you can list all available nodes, you can request the shima specific shea on a specific node. So for example, if you want to get the exact scheme of uh Gmail node. So you can just ask uh via the command line interface and uh the agent the AI agent will iterate uh with this tool. uh so it's really uh in fact local skills so everything is in local and uh so cloud the code has access to all the knowledge uh without uh um the need of an NCP mc mcp or to go search on internet uh everything is local uh except if he wants to get some examples so uh for that nc compile uh I set uh 7,000 I think 7,000

templates uh community templates uh so here it's a list and if you want to get inspiration from one template or another it will just download it and uh get the nodes get the the scheme the the flow and try to do something uh similar. — Got it. So, — so you have access to the template library of 7,000 templates that we have available. So, then it can look up one of those templates and then be able to pull that for inspiration. Is that correct? Uh [snorts] it's in fact um it's using a GitHub repo — that is uh already uh um building stacking a list of community workflows and anything as code rely on this particular uh GitHub — got it — as a dependency. Uh so I see that it did uh create a workflow but it did not give me the URL. So I will ask it up. Give me the URL. Please always say please to code. — Yeah. We want to be nice to those robot overlords. — Yeah. Sure. Of course. — Sure. — All right. So now I will have to stop the screen sharing to switch. — Sure. As you share the new screen. So then what you're doing right now is you have a GitHub repo that is up to date with all of the templates from the template gallery. And so it's accessing that GitHub repo that it can then pull down any of those for inspirations or references. — Yeah. Uh okay, let's share the tab. It will be cleaner. And just so people know the init code is a package that you've made for cursor visual studios and for claude and openclaw uh to be able to access code. — Exactly. — So here we just uh saw the cloud plug-in uh that you can install in two command lines um and here is the workflow that has been generated. So it's a very simple workflow for the demo but it's a completely depend of the prompt. Uh you can uh build a very complex prompt and it will uh build in what one attempt it will build whatever workflow you need. So here it's very simple. So it's a trigger. Get stripe transactions like we saw. Check if the customer exist in the posgree database. Insert new customer in the posgree and then log the result. — Great. And I'm assuming with that you probably have some sort of pre-prompting ahead of time where you maybe put your Stripe APIs inside of Aen ENV so that it has access to be able to use your Stripe account. Is that correct? Uh, no not really because in fact [snorts] um I think that it's better for a average user to use NA10 uh UI uh to do all that kind of stuff. So the thing is you will use N8 as code to build uh your workflow to correct your workflow to uh but as soon as you need some credentials uh for tears for Gmail whatever uh the easiest way is to go and uh in NA10 instance whether it's a cloud instance uh in which you will already have all bunch of credentials So um the easiest way is that so you will click on the node and setup credentials and uh it's um it's wanted that the user uh rely on the strength of N8 uh and I think that the biggest one of the big strength is you have already uh infrastructure and credentials vault uh so Yeah, — safe place of server credentials is inside in that makes a ton of sense. — Yeah. Yeah, exactly. Um, okay. So, uh we'll see what uh open claw did. So, I will switch my screen again. — I think then claw just right now or claude code right there was able to — open claw. Yeah. Let's see what uh what open claw finally uh did. Okay. So I will share this screen again. So okay uh open cl manage also to uh build the workflow that was requested. So he build a zenesk trigger sentiment analysis AI agent a sentiment switch and an action. So let's see the result — and openclaw actually gave you the URL. It was great. — Yeah by himself. uh close the code. I had to ask him. Yeah. Okay. So, let me share the results screen. So, you have the Zenesk trigger, the sentiment analysis agent uh open AI model. So to answer your question for credentials it's much simpler to go there and to uh select your uh pre uh saved credentials and uh here you go the warning just disappear uh the same for the desk and so on. So here you have a complete uh completely fine working uh workflow with a switch uh slack alert log the togree uh database uh here you are. — Mhm. And then are you able to then send a new prompt to openclaw or cloud code to say this is great but I also wanted to send a email via Gmail. [snorts] — Sure. Let's do this. Okay, I will switch my screen again. Okay, so uh let's see what I can do. Uh okay, so for example, just uh we'll add a simple Gmail node after the Slack alert if it's okay for you. — Sure. — Okay, so let's ask him that. Uh thank you for the workflow. Uh let's add a Gmail node right after the Slack uh node. Great. And you're using Whisper Flow for that to speak it right into it. — I'm using uh Hendy. — Okay. — Handy. Yeah. It's it rely on Whisper in the background, but it's not Whisper Flow. It's running. It's uh it will uh check the workflow and uh add this node. Uh do you want me to show uh you cursor? Yeah, it' be good to get that inside there. And um what I'd like to do too is once we go through cursor, I'd love to show people, you know, how exactly do they get in as code on claw or claude code or cursor. So if they wanted to be able to access this, you know, what are the steps of them being able to get this implemented into their own system and infrastructure? — Okay, so this is very simple. I will share you my screen uh again. So, and as you're getting that ready, yeah, it was funny because the way that I came across you is uh you had the in code inside of Visual Studios and I thought it was amazing, but I wanted to use cursor. So I just uh vibe coded a solution for cursor uh because your code wasn't available then put into market — and then you — yeah you brought yours over and it was great because uh to be totally honest uh I missed the thing I I forgot to uh in my CI you know in my GitHub action CI I forgot to uh trigger the open VS6 uh delivery. [snorts] Uh so you uh you just fill the gap and when I realized that it was lacking cursor extension I saw your so it was — funny once you did that I was like cool I'll take mine off you go ahead and take it go run with it. It was just it was a stop gap because I wanted yours. I just wanted in a different environment which is great. You've ported it over to cursor and openclaw since so it's great. — No, thank you for filling the gap way. — Uh okay. So uh do you see my uh GitHub tab? So the project is NA10 as code

on GitHub. Um the installation is very simple. uh you just have to pick [clears throat] um four u one of the four method of installation. So you can install it directly in VS code or cursor. So for that it's uh you just have to go to the VS code store or open VS6 store and type NA10 as code and uh install the uh the the extension. Uh so very simple and uh then uh I will I show you how it's working in cursor. Uh clude code is simple also when uh when include uh code you just uh add plug-in marketplace and plug-in install and uh the next steps are the ones that we s we saw earlier. — Mhm. Uh same for open claw. It's a plug it's a plug-in install in fact and then you have a setup wizard. So basically it's it run in three lines of uh of code in your client. And then after you're ready to prompt uh really like we did earlier. Uh the only part that you did not see here is those three lines uh of setup. Um, so I don't know if you want to see a setup. I can show you a setup uh wizard if you want. — No, it's okay. I mean, just so people can know. I mean, it seems pretty straightforward that what you need to do is you just copy those commands and then you paste inside the relative thing. So whether it's — there open claw, just copy those pages. So just people know, go to the GitHub, go to that section, copy and paste those commands, hit enter, and then I'm sure it's just going to onboard you through that process. — Yeah. Yeah. It's an on it's on boarding. So, it's really a wizard. Uh it's telling you what to do uh if you have already NAN instance or not. Uh and so on. So, it's really easy to install. — Yeah. And we'll make this GitHub repo available. So, if you're watching this, if you go down in the description into the YouTube video, you'll see the GitHub repo uh from it in here. And then we'll be able to uh make that available. So, you can just get up and running. Just follow these steps. you'll get started. Fantastic. So then let's transition over to cursor. — Yeah, sure. Okay. So, uh I just launched it. Uh so in fact, we'll not go to cursor right now. We'll go to the result of open claw. Uh you remember we asked it for a Gmail um node. Uh let's see if it manage. — It jump from screen to screen. There's a lot of ground covering it. — Yeah. Exactly. So, uh here you go. Uh it just added the send mail after Slack alert. Uh so, exactly as we requested to him. So, those example are very simple. Of course, it would be quicker to do it manually. But when um you are new to NA10, maybe you don't know the name of the node, what what are the options. So it can really save times to beginners also. Um for example, if you don't know how to send mail or so on, it will provide you list. So yeah, are you with this real quick before you go to cursor, are you able to analyze and debug if something breaks? Uh for example, if there's a if you run it and it executes and there's an error, are you able to use cloud code or open claw to be able to do that? Yeah, sure. uh you can just uh copy past u the error message for example and uh it will fix the node. So if you trigger if you launch a trigger and you see that an agent I don't know for example an agent is failing because it do not have aruct structured JSON output for example it often happens uh so you will just tell that uh please fix this agent it it's constantly failing um even if it's a bug that is not uh occurring each uh you just tell it this node is not okay and it will add for example a JSON structured output in the tooling of the agend. Got it. But when you're saying that are you saying we need to copy and paste the JSON from naden into say openclaw or cloud code and say hey here's the JSON can you fix this JSON or does it because there's a thing called hooks. It's not web hooks, but actual hooks — and so the hooks will actually give you the executional history of something. So we'll go inside there. So I don't know which one of those you're doing if you're copy and pasting or it's actually able to go in and grab the hook data. — Okay. Uh right now NA10 ascode is more uh on the build side. So it's much aner to build your workflow and it's not at the time we are speaking uh really into execution. So uh we are implementing uh some stuff there is a PR right now with some stuff on the execution side but um we need to have something strong before merging all of this. So right now it's all about building. So it's a dev tool to build workflows uh for the execution. It's not uh really do done for that uh from the scratch from scratch. — Sure. — Yeah. So I mean that's something people can do. I had a previous podcast guest on uh who built a enterprise dashboard and we're using the hooks to grab the executional history of it to see what was going on. Uh so that GitHub is a repo available as well. So uh whether you or anybody else is listening maybe wants to grab that repo and this repo and you know merge some things together so that you can get not only be able to build be able to edit and adjust that is I could see as an iteration as time goes on but as we know uh there you know really these things become powerful the more you iterate. So power of the community power of iteration is really what starts to make these things start to become like a one-stop shop for all of your developing and automation needs. So great. Amazing. I was just curious about that. Fantastic. So let's go into

let's take a look at the cursor and let's see how we code and cursor. — Okay. So uh the prompt uh is here on the top left of the screen. So create a lead nurturing uh workflow. Uh the trigger is a type form submission. Uh there is an arrange enrangement uh email with clear bit um and some conditions and the mailchimp list um pretty simple. So cursor just uh went through all the N8 steps to uh check node existence validate the workflows. So it took uh I think it took like one or two minute for this uh workflow for example. So we can see the workflow here in Typescript and uh on the right uh we have the integration in web view of N8. So uh the workflow you so with the cursor or VS code extensions um the strength of this uh is that you have you all have in the same IDE uh so it's pretty it's practical uh so on the left on the right sorry you will have the your all your workflows so uh you can see the workflows that are on your N8 instance and are not local And this one on the top is the one we just created. So when you click this button, so you can see uh the workflow. Um and uh here it is. So uh now we can uh continue prompting cursor to improve the workflow and uh it will uh automatically refresh uh once the model push some modification. So we can basically uh do the same modification at the Gmail. — And as you type that in, what I like about this is that a lot of people want to stay in their ID of choice. Some people want to use cursor or visual studios and they don't want to hop around from having cloud code create the JSONs in and then going back and forth. And what's great about this is this AI has this wraparound that allows it to be able to use Nadin with this AI inside of this IDE so that you have the power of the AI model with all the context of inadin plus the files and the folders and all that. So I think this is great and I love being able to stay inside of one IDE to be able to produce this and then visually see it — with NAD which I think is the power of Nadin. can see what's going on with the code and not just see folders and files being created on the side panel. — Yeah, sure. And the perfect example, it's easier for me to show. I don't have to switch uh tabs and screen sharing. So, the same for developers and users. Um but yeah um open CL code uh will be more for power users that are used to uh command line inter interface and um uh VS code and um cursor will be much more average user friendly. — Mhm. — Yeah. So it depends on whatever your IDE of choice is, you know, whether you're in the open CL cloud code or Visual Studios, you can really bring in it in with you and then have that power of that visual interface which allows us to be able to see things that you know and understand exactly what's happening and if something breaks, why it broke and what you can do about it. — Sure. If you're more a no code uh user, I think that cursor is a perfect uh tool. — Yeah. It's funny how cursor became a no coder choice of tools even though it's designed for you know a coding environment. — Yeah. So you can see right now the screen just refreshed uh automatically. So I asked him a Gmail uh um node um he worked on it uh and uh once it was pushed it just refreshed so it's it's all automatic and it goes both ways

so if I make some modification here for example with credentials uh which I will do uh then it's saved here and uh it will be automatically synced uh sync back to the local TypeScript file and then the agent will have the knowledge of uh all this and if there is a conflict between uh the local files and the actual workflow on N8 uh the agent the II agent will be able to resolve it uh by itself. — Great. I love that two-way sync back and forth. And so you can see all of your workflows on the right hand side. Those are the ones in red. The one that just got sunk up is the one at the very top that looks like it's in light blue. And then you can go back and forth chatting with your favorite model, you know, whether it's Opus 4. 6 or, you know, — Sure. — And uh yeah, sure. And one point that is important I think it's with uh the help of uh N8 as code um the agent

is really on rails so he really had to have a great knowledge of N810 so it has zero elucination and you can use a very tiny uh model uh you don't you are not you don't have to choose a last frontier model that will cost you hundreds in tokens for just doing a uh a workflow. uh it will be very effective with tiny models uh such as the flash mini uh whatever the brands but you know all brands are making flash mini turbo uh all that kind of models that are really cheap and it works really well and uh even better than biggest models that will overink the thing and — that's great. So since it's on Rails and since it has, you know, access to the data, then you don't have to use such a giant model, you can use Kimmy K or whatever else is out there to be able to — Yeah, — exactly. — Great. All right. — It's not using MCP, so it's much more light uh than uh MCP based solution. — Sure. Yeah, that makes sense. I mean, so this is great. So now we we've seen uh you know how to install it on openclaw, cloud code and ver uh visual studios and cursor. This is how you get this in here. up and running with it. So if anybody wants to be able to uh develop and iterate, you know, with the latest and greatest of these different types of environments along with Nadin, uh they can just download your GitHub package, install them with simple couple command lines, and then they're up and running. Is there anything else you'd like to let people know about this? — Uh no, I think we are we um we pretty much uh see uh the wall package. Um could simply show you the uh extension uh since we are in cursor uh you are just looking for N8 as code. So uh just you just have to install uh click on the install button and you're done. Uh since uh we saw previously uh the command lines uh here in this case it's even simpler. Just install and you're done. — Yep. Go to the marketplace icon inside a cursor or VS Studios — and then you're off the races. Fantastic. And if people want to find out more about what you're doing, updates with these packages that you're creating, how do they do that? as you can follow me on GitHub. So I guess uh there will be a link uh to the N8 ascode repo. Uh so uh just follow me on GitHub and you will be uh updated with all uh release uh next release of NAS code uh and there will be a plenty I think. — Fantastic. And for anybody watching this, if there's any ideas or iterations, if there's things that you're seeing that we're not seeing, and you said, "Oh my god, it would be incredible if it could do X, Y, and Z. " Comment down below because chances are we're going to see these comments, and you know, we may or may not Itch and might take that and prioritize it and turn it into an awesome new feature so that everybody can get the benefits of init. So with that, thank you all so much. Itching, it's been an honor and a pleasure, my friend. Much love and I'll see you all on the other side.