Build n8n Workflows Without Leaving Your IDE with Etienne Lescot

🎁 Download the n8n plugin repo → https://go.n8n.io/n8n-ide-plugin
Stop switching between your IDE and n8n. Build workflows without ever leaving your coding environment.

n8n as Code brings n8n directly into Cursor, VS Code, Claude Code, and Open Claude — so you can prompt, build, and iterate on workflows without leaving your editor.

In this episode, I sit down with Etienne Lescot, the developer behind n8n as Code, for a fully live demo. We watch him build real workflows inside Claude Code, Open Claude, and Cursor — including a two-way sync where edits in n8n automatically update your local TypeScript files, and vice versa. Zero hallucinations, runs on tiny, cheap LLMs.

–––––––––––––––––––––––
⏱ TIMESTAMPS
0:00 – Intro
1:05 – Meet Etienne: the man who built n8n as Code
1:54 – Live demo begins: building workflows with Claude Code
2:14 – First prompt: Stripe + Postgres workflow
3:37 – Switching to Open Cloud: support ticket triage workflow
5:38 – How n8n as Code works: built-in tooling & local skills
7:02 – Access to 7,000 community templates
16:14 – Installation walkthrough: GitHub repo & setup
23:13 – Cursor demo: lead nurturing workflow
27:51 – Two-way sync between IDE and n8n
28:59 – Zero hallucinations: runs on tiny, cheap LLMs
–––––––––––––––––––––––
🔗 LINKS
📦 n8n as Code template: https://go.n8n.io/n8n-ide-plugin
–––––––––––––––––––––––
#n8n #AIAutomation #WorkflowAutomation #CursorAI #ClaudeCode #nocode #lowcode

Get 30% Off n8n Cloud Starter or Pro Plans!
Want to get started with n8n? Visit n8n.io/pricing and use code 2025-N8N-PODCAST-729C416E at checkout for 30% off your first month or year.

Transcript

SPEAKER_01 0:00

A lot of people want to stay in their IDA of choice. Some people want to use Cursor or Visual Code Studios and they don't want to hop around from having Cloud Code create the JSONs and then going back and forth.

SPEAKER_00 0:10

Because both ways, if I uh make some modification here saved here, it will be automatically uh synced back to the local uh TypeScript file and then the agent will have the knowledge of uh all this. Always say please to to cloud.

SPEAKER_01 0:25

Yeah, we want to be nice to those robot overloads.

SPEAKER_00 0:28

Today we are learning to build NA10 workflows in uh cursor, cloud code, and open cloud with NA10 as code.

SPEAKER_01 0:36

If you're building with cloud code, cursor, or open clock, chances are you're still jumping over to inatein to build the actual workflows. You prompt in your IDE, switch over to inatein, click around, and then come back. Constantly context switching between two or even three different environments. Inatein as code fixes that. It's a plugin that brings inadein 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 Itchen, the man who built it. We're gonna see him run it live in Cloud Code, OpenClaw, and Cursor, including a two-way sync where you edit it in N8N and then it updates it in your IDE, and vice versa. And because it ships with local knowledge of every NAN node and 7,000 NAN community templates, the agent build 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. Itchin, welcome to the show. So what are we learning today?

SPEAKER_00 1:44

Hi. Today we are learning to build NA10 workflows in uh cursor, cloud code, and open clo with NA10 as code.

SPEAKER_01 1:53

Fantastic. I'd 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.

SPEAKER_00 2:02

So I will share uh my uh cloud code uh command line uh interface, and uh so basically I will just uh pass the prompt in it. Uh so a simple prompt asking uh to uh asking any time as code to create uh workflow uh to uh which will trigger every hour fetch uh 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.

SPEAKER_01 2:36

I was gonna say so so it looks like we're going into Stripe and we're gonna fetch transactions in Stripe and uh put it into Postgres.

SPEAKER_00 2:44

It's quite a random uh workflow. I mean uh the goal is is to show how the workflow is built by itself. Um the workflow in itself is not uh really uh uh something. Uh but yeah, so you you can see that Claude starts to ask uh questions, so I will just allow him to read uh whatever he needs to read, and uh he will do his uh job.

SPEAKER_01 3:08

Asking for credentials, so you have to give it your API key as well as your your your website. So I give him my uh URL.

SPEAKER_00 3:20

So the it's a local uh NA10 uh instance, then I can pass my API key. Don't worry, I will uh crush uh it later, it's just a local API key. Okay, and while it's uh working, uh we could switch to open claw and uh do something uh similar. So we are right now in uh in open claw, so it's another another tab, and uh we'll give it uh another prompt to uh to uh to do another workflow. So now we will create a support uh ticket uh triage. Um so again it's not uh the workflow that is important, but uh okay, we are telling it uh to uh uh have a web book with uh from ZenDesk, uh use OpenAI node, uh classify the ticket, and so on.

SPEAKER_01 4:14

So got it. Uh typical support automation that helps us triage use cases of uh uh basically requests coming in for support that we can then send into Zendesk and then rate them positive, negative, neutral, which I'm sure we could always do additional things on top of it, but it's a big use case for time.

SPEAKER_00 4:35

Yeah, afterwise uh you can uh um ask a cloud or open cloud to uh to add some nodes, to to fix some nodes, uh but uh right now we will just uh see what it gives us uh on the first uh attempt. Um so it's running, it's uh syncing. Um what we can do so here here you can see that it got some error, so it will auto-fix um using uh NA10 uh as code uh ontology. Uh so uh if uh for whatever reason it creates a workflow that is wrong with uh a wrong node or a wrong schema or so on, uh it will fix uh by itself by uh uh querying uh data.

SPEAKER_01 5:26

Great. And did you feed it any like innate in skills at all? I know there's N8N skills that are floating around in the marketplace. Have you given it any tools?

SPEAKER_00 5:36

Uh it's in fact it's uh a skill in itself uh because um so N8NS code is uh bundled with uh some uh tooling, in fact, uh which is uh N80 AC. Uh it's a common line uh tooling to request whatever uh you need to know about uh nodes schema. Uh you can list all available nodes, you can request a schema, specific schema on a specific uh node. So, for example, if you if you want to get the exact uh scheme of uh uh Gmail node, so you can just ask uh via the command line interface, and uh the 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 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 uh uh NAKNAC compile uh uh I uh set uh 7000, I think 7000 templates, uh community templates. Uh so here it's a list, and if you want to get inspiration from one template or another, he will just download it and uh get uh get the nodes, get the sh the the scheme, the the the flow, and uh uh try to to do something uh uh similar.

SPEAKER_01 7:25

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?

SPEAKER_00 7:37

Uh it's in fact um it's using uh uh GitHub repo that is uh already uh um building stacking a list of uh community uh workflows, and uh anything as code rely on this particular uh uh GitHub uh as a as a uh 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 to give me the URL to please always say please to to Claude.

SPEAKER_01 8:20

Yeah, yeah, we want to be nice to those robot overlords, yeah. Sure.

SPEAKER_00 8:24

Of course, sure. All right, and you can so now I will have to stop the screen sharing to switch. Sure.

SPEAKER_01 8:36

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.

SPEAKER_00 8:51

Yeah. Uh okay, let's share the the tab. It will be cleaner.

SPEAKER_01 8:56

And just so people know, the innateness code is a package that you've made for cursor, Visual Studios, and for Claude and OpenClaw to be able to access in this code.

SPEAKER_00 9:08

Yeah, exactly. So here we just we just uh saw the cloud plugin uh that you can install in the two command lines. Um and uh here is the workflow that has been uh generated. So it's a very simple uh workflow for the for the demo, but uh it's uh completely depend of the prompt. Uh you can uh build a very complex prompt and it will uh build in the what one one attempt, it will build whatever workflow you you need. So here it's very simple. Uh so it's uh a trigger, uh, get stripe uh transactions like we saw. Uh check uh if the customer exists in a Postgre uh database, insert new customer in the Postgre and then log the result.

SPEAKER_01 9:54

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 a.ing env so that it has access to be able to use your Stripe account. Is that correct?

SPEAKER_00 10:10

Uh no, not really, because in fact um I think that it's a better for a uh uh average user to use NA10 uh uh UI uh to do all that kind of stuff. So the thing is you will use NA10 as code to build uh your workflow, to correct uh your workflow, to uh but as as soon as you need some credentials uh for tiers, uh for a Gmail, uh whatever, uh the easiest way is to go and uh in uh NA10 uh instance, whether it's a cloud instance, uh in which you will already have a whole bunch of uh credentials. So um the easiest way is is that so you you will click on the node and uh set up credentials, and uh it's um it's uh it's wanted that the user uh uh rely on the strengths uh of N80. Uh and I think that's the biggest uh one of the big strengths is you have already uh infrastructure and uh credentials vault. Uh so uh yeah.

SPEAKER_01 11:22

Safe place to store the credentials is inside N80. That makes a ton of sense.

SPEAKER_00 11:25

Yeah, yeah, exactly. Um okay, so uh we'll see what uh OpenCloud did. So I will switch my screen again. Uh OpenClaw, yeah, yeah. Let's let's see what uh what uh OpenClo finally uh did. Okay, so I will share this screen again. So okay, uh OpenClaw manage uh also to uh build the workflow that uh was uh requested. So he built a Zen desk trigger, uh sentiment analysis AI agent, a sentiment switch, and an action. So let's see the result.

SPEAKER_01 12:12

And open claw actually gave you the URL, it's great.

SPEAKER_00 12:16

Yeah, by himself. Uh claw the code. Uh I had to ask him uh yeah, okay. So let me share the result screen. So you have the ZenDesk trigger, the sentiment uh analysis uh agent, uh OpenAI model. So to answer your question, uh for credentials, it's much simpler to go there and to uh select your uh pre-uh uh saved uh credentials, and uh here you go, the the warning just disappear. Uh the same for Zindesk and so on. So here you have a complete uh completely fine working uh uh workflow with a switch, uh Slack alert, uh log the to Postgre uh uh database. Uh here you are.

SPEAKER_01 13:12

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 an email via Gmail.

SPEAKER_00 13:23

Sure. Sure. Let's do this. Okay, I will switch my screen again. Okay, so uh let's uh 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 uh 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.

SPEAKER_01 13:56

Okay. And you're using Whisperflow for that to speak it right into it?

SPEAKER_00 14:01

I'm using uh handy.

SPEAKER_01 14:04

Handy.

SPEAKER_00 14:05

Okay. Handy, yeah. And it's it's uh it's rely on uh whisper in the background, uh, but it's not uh it's not whisper flow. It's it's running, it's uh it will uh check the workflow and uh uh add this uh this uh node. Uh do you want me to show uh you cursor?

SPEAKER_01 14:24

Yeah, it'd be good to get 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 how exactly do they get in it in as code on OpenClaw 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?

SPEAKER_00 14:46

Okay, so this is very simple. I will share you my screen uh again.

SPEAKER_01 14:52

So and as you're getting that ready, yeah, it was it was funny because the way that I came across you is uh you had the NNS code inside of Visual Studios. I thought it was amazing, but I wanted to use cursor. So I just uh uh vibe coded a solution for cursor uh because your your code wasn't available and put into part. Yeah, and and then you yeah, you brought yours over.

SPEAKER_00 15:17

And it was great because uh to be uh totally honest, uh I missed the I missed uh the thing. I I I forgot to uh uh in my CI, you know, in my GitHub Action uh CI, uh I forgot to uh trigger uh uh the open vs6 uh delivery. Uh it so uh you uh you just uh fill the gap. And when I uh realized that it was a lacking uh cursor extension, I saw your uh so it was uh once you did that, I was like, cool, I'll take mine off.

SPEAKER_01 15:53

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 it in a different environment, which is great. You've ported it over to cursor and open clock since so it's great.

SPEAKER_00 16:03

No, no, thank you for uh filling the gap while I was uh uh okay. So uh do you see my uh GitHub tab? So the pro the project is uh N80 as code on uh GitHub. Um the installation is very very simple. Uh you just have to pick uh four uh uh one of the four methods of installation. So you can install it directly in VS Code or Cursor. So for that it's uh you just have uh to go to the VS Code store or OpenVSX store and type uh na10 as code and uh install the uh the the the extension. Uh so very simple and uh then uh I'll we'll show you uh how it's working in cursor. Uh cloud code is uh simple also. When uh when in code include uh code you just uh add a plugin marketplace and uh plugin install, and uh the next steps are the ones that uh we saw we saw earlier. Uh same for open cloud it's uh plug it's a plugin and install, in fact, and then we you have a uh setup wizard. So basically it's it runs in three lines of uh of code in your uh client, and then after you're ready to prompt uh really like we uh we did earlier. Uh the only part that uh you did not see here is uh those those uh three lines uh of uh of setup. Um so I don't know if you want to see a setup. I I can show you uh setup uh wizard if you if you want. No, it's okay.

SPEAKER_01 17:53

I mean, just so people can know. I mean, it seems pretty straightforward that what you need to do is you just copy those those commands and then you paste inside the relative thing. So whether it's yeah, 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 gonna onboard you through that process.

SPEAKER_00 18:13

Yeah, yeah, it's an on it's onboarding, so it's really a wizard. Uh, it's telling you what to do, uh if you have uh already uh NA10 instance or not, uh, and so on. So it's uh really easy to install.

SPEAKER_01 18:29

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 Itchin 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.

SPEAKER_00 18:48

Yeah, sure. Okay, so uh I just uh launched it. Uh so in fact, we'll not go to cursor right now, we'll go to the uh result of uh open claw. Uh you remember we asked it for a Gmail uh um node. Uh let's let's see if it managed.

SPEAKER_01 19:12

A lot of ground recovery now.

SPEAKER_00 19:13

Yeah, yeah, exactly. So uh here you go. Uh it just added the send mail uh after uh Slack uh alert, uh so exactly as we requested uh to him. So those examples are very, very simple. Of course, uh it would be uh quicker to do it manually, but when um you are new to Na10, maybe you don't know uh the name of the of the node, maybe you don't know what uh what what are the options, so it can really save time to beginners also. Um for example, if you don't know uh how to send mail or or so on, it will uh provide you lists. So yeah.

SPEAKER_01 19:57

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 is 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?

SPEAKER_00 20:15

Yeah, sure, sure. Uh you can just uh copy past uh the error message, for example, and uh it will uh it will fix uh the the node. So if you trigger, if you if you launch a trigger and you see that uh an agent, uh I don't know, for example, an agent is failing because uh it do not have a structured JSON output, for example, it uh often uh happens. Uh so you will just tell that uh please uh fix this agent, uh it's uh it's constantly uh failing. Um even even if it's a uh a bug that is not uh occurring each time, uh you just tell it uh this this node is not okay, and uh it will add, for example, uh JSON structured uh output in the tooling of the agent.

SPEAKER_01 21:08

Got it. But when you're saying that, are you saying you we need to copy and paste the JSON from N8N into say OpenClaw or Claude Code and say, hey, here's the 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 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 copying and pasting, or if it's actually able to go in and grab the hook data.

SPEAKER_00 21:38

Okay. Uh right now, right now, NA10 as code is more uh on the build uh side, so it's much an helper 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 uh stuff there is a PR right now with some uh stuff on the execution side, but um we need to have something strong before uh merging uh all of this. So right now it's all about building, so uh 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.

SPEAKER_01 22:25

Sure. Yeah. So I mean that's something people can do. I had um a previous podcast guest on uh who built an 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 sure I could see as an iteration as time goes on. But as we know, uh the 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 know in this code and cursor.

SPEAKER_00 23:18

Okay, so uh the prompt uh uh is uh here on the top uh left of the screen. So create a lead uh nurturing uh uh uh workflow. Uh the trigger is a type form submission. Uh there is an arrangement enrichment uh email with clear bit um and some conditions and the mail chimp list um pretty uh simple. So a cursor just uh went through all the NATO AC steps to uh check uh node existence, validate the workflows. So it took uh I think it took like uh one or two minutes for uh for this uh workflow, for example. So we can see the workflow here in uh TypeScript. And uh on the right uh we have the integration in WebView of uh NA10. So uh the workflow you so with the cursor or VS Code uh extensions. Um the strength of this uh uh is that uh you have you all have in the same uh 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 NA10 instance and are not local. And this one on the top is the one we just uh created. So when you click this button, so you you can see uh the workflow. Um and uh here it is. So uh now we can uh continue prompting uh cursor to improve uh the workflow, and uh it will uh um automatically refresh uh once the model push uh uh some modification. So we we can uh basically uh uh do the same uh modification. Uh add the Gmail.

SPEAKER_01 25:24

And as you type that in, what I like about this is that a lot of people want to stay in their IDE 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, then it 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 in8in with this AI inside of this IDE so that you have the power of the AI model with all the context of in8in 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 inadein, which I think is the power of in itin. You can see what's going on with the code and not just see folders and files being created on the side panel.

SPEAKER_00 26:12

Yeah, sure, sure. And the perfect example, it's uh it's it's easier for me to show. I don't have to switch uh uh tabs and uh screen sharing. So uh the same for our developers and users. Um but yeah, um open cloud, cloud code uh will be more for power users that uh are used to uh uh command line uh interface interface, and uh uh VS Code and uh um cursor will be much more uh average user-friendly.

SPEAKER_01 26:48

Yeah, so it depends on whatever your IDE of choice is, you know, whether you're in the open 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 what you can do about it.

SPEAKER_00 27:09

Sure. Uh, if you're more a no-code uh user, uh I think that cursor is a perfect uh uh tool.

SPEAKER_01 27:20

Yeah, it's funny how cursor became a no-coder choice of tools, even though it's it's designed for you know a coding environment.

SPEAKER_00 27:28

Yeah, yeah, yeah. So you can see right now the the screen just refreshed uh automatically. So I asked him uh Gmail uh um node, um he worked on it, uh and uh once it was pushed, it just refreshed. So it's uh it's all automatic and it goes both ways. So if if I uh make some modification here, for example, with the credentials uh which I will do, uh then it's saved here and uh it will be automatically uh synced, uh synced back uh to uh to the local uh TypeScript file, and then the the agent will have the knowledge of uh all this. And uh, if uh there is a conflict between uh the local files and uh the actual workflow on the N80, uh the agent, the AI agent, will be able to resolve it uh by itself.

SPEAKER_01 28:30

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.

SPEAKER_00 28:49

And uh yeah, sure. And one point that is uh important, I think, it's uh with uh the help of uh NA10 as code, um the agent is uh really on uh rails, uh so it really had to have a great uh knowledge of NA10. So yeah, it has zero hallucination, and you can use a very tiny uh model. Uh you don't you are not you don't have to choose the last frontier model uh that will cost you uh hundreds in tokens for just uh doing uh uh uh a workflow. Uh it will be be very effective with with tiny models, uh such as the flash mini, uh whatever the brand, but uh you know all our brands are um are making uh flash mini uh turbo uh all that kind of models that are really really cheap and it works really well and uh even better than biggest models that will overthink the uh the thing. And um that's great.

SPEAKER_01 29:52

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 you know Kimmy K or whatever else is out there to be able to do it.

SPEAKER_00 30:02

Yeah, exactly.

SPEAKER_01 30:03

Great. All right.

SPEAKER_00 30:06

It's not uh using uh MCP, so it's much more light uh than uh MCP-based uh solution.

SPEAKER_01 30:14

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 open claw, cloud code, and Visual Studios and Cursor. This is how you get this in here. This is how you get 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 in itin, uh they can just download your GitHub package, install them with a simple couple command lines, and then they're up and running. Is is there anything else you'd like to let people know about this?

SPEAKER_00 30:47

Uh no, I think we are we um we pretty much uh see uh uh the wall uh package. Um could uh simply show you the uh extension uh uh since we are in cursor. Uh you are just looking for n80 as code, so uh just you just have to install uh click on the install button and uh you're done. Uh since uh we saw uh previously uh the command lines. Uh here in this case it's even simpler, just install and uh you're you're you're done.

SPEAKER_01 31:24

Yep, go to the marketplace icon inside a cursor via studios, yeah. Um and then you're off the races. Fantastic. And if 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?

SPEAKER_00 31:37

Uh, they can follow me on uh GitHub. So I guess uh there will be a link uh uh to the NATNS code repo. Uh so uh just follow me on uh GitHub and you will be uh updated with uh all uh uh release, uh next release of NATAN S Code. Uh and there will be uh plenty, I think.

SPEAKER_01 31:58

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 gonna see these comments, and you know, we may or may not. Itchin might take that and prioritize it and turn it into an awesome new feature so that everybody can get the benefits of in it in his code. So, with that, thank you all so much. Itchin, it's been an honor and a pleasure, my friend. Much love, and I'll see you all on the other side. Bye now.