WEBVTT 00:00:00.000 --> 00:00:03.379 We've all been there. That feeling, right? You 00:00:03.379 --> 00:00:05.839 dive into some powerful new tool, maybe like 00:00:05.839 --> 00:00:08.480 NAN, and you've got this big vision, all the 00:00:08.480 --> 00:00:10.640 amazing automations you're going to build. But 00:00:10.640 --> 00:00:12.960 then, you know, the tutorials just keep coming. 00:00:13.080 --> 00:00:15.220 The docs seem endless. You're sort of swimming 00:00:15.220 --> 00:00:16.960 in information, but you're not actually building 00:00:16.960 --> 00:00:19.219 anything, anything that creates real value anyway. 00:00:19.440 --> 00:00:21.440 Yeah, you get stuck in what people call tutorial 00:00:21.440 --> 00:00:24.660 hell. It's really common. It is. You spend so 00:00:24.660 --> 00:00:26.260 much time learning about the tool, you kind of 00:00:26.260 --> 00:00:29.940 forget to just... Use it. Right. Exactly. So 00:00:29.940 --> 00:00:32.280 what if we could just bypass all that overwhelm? 00:00:32.399 --> 00:00:34.320 What if instead of feeling like you've got to 00:00:34.320 --> 00:00:37.700 master, what, over a thousand NEN nodes? You 00:00:37.700 --> 00:00:40.579 could just focus on the crucial ones. The essentials. 00:00:40.920 --> 00:00:42.780 Yeah, the essentials. That's what we're exploring 00:00:42.780 --> 00:00:44.759 today. We're going to unpack this 80 -20 approach 00:00:44.759 --> 00:00:46.640 to any and all. We're going to show you that 00:00:46.640 --> 00:00:48.920 really just 14 nodes are pretty much all you 00:00:48.920 --> 00:00:51.079 need for like 80 % of professional automation 00:00:51.079 --> 00:00:54.000 workflows. This is our deep dive into getting 00:00:54.000 --> 00:00:56.679 you out of tutorial hell. Shifting your mindset 00:00:56.679 --> 00:01:00.079 from being this eternal student to actually being 00:01:00.079 --> 00:01:02.469 an effective builder. And this isn't just theory. 00:01:02.950 --> 00:01:05.769 It's a system that's been tested, refined through 00:01:05.769 --> 00:01:08.950 tons of real -world automations. Once you really 00:01:08.950 --> 00:01:13.750 get your head around these core pieces, the possibilities 00:01:13.750 --> 00:01:16.390 just explode. It really opens things up. Okay. 00:01:16.409 --> 00:01:19.090 So to help us navigate this, we've kind of grouped 00:01:19.090 --> 00:01:21.810 these 14 nodes into five main categories. You 00:01:21.810 --> 00:01:24.390 can think of them like fundamental skill trees 00:01:24.390 --> 00:01:26.709 if you want to become a real N8n power user. 00:01:26.930 --> 00:01:28.829 Yeah. Good way to put it. So we'll start with 00:01:28.829 --> 00:01:31.430 the execution essentials. Yeah. the basic physics 00:01:31.430 --> 00:01:34.689 of N8N. So we'll hit the basic triggers, universal 00:01:34.689 --> 00:01:38.030 data processing, how to connect with connectivity 00:01:38.030 --> 00:01:40.569 and APIs, and then finally bringing in some AI. 00:01:40.790 --> 00:01:42.870 Sounds like a plan. All right, let's start right 00:01:42.870 --> 00:01:45.069 at the foundation, what we're calling the laws 00:01:45.069 --> 00:01:47.950 of the N8 universe, the execution essentials. 00:01:48.709 --> 00:01:50.890 Because before you even drag one node out of 00:01:50.890 --> 00:01:52.790 that canvas, you kind of need to understand... 00:01:53.239 --> 00:01:55.900 The basic rules, how ANN actually works. Absolutely. 00:01:56.319 --> 00:01:58.620 Missing these five core ideas, well, that's where 00:01:58.620 --> 00:02:01.640 like 99 % beginner frustration comes from. It's 00:02:01.640 --> 00:02:03.459 like trying to build a skyscraper without understanding 00:02:03.459 --> 00:02:06.500 gravity. That's a great analogy. So the first 00:02:06.500 --> 00:02:08.759 law is what we can call the law of gravity. It's 00:02:08.759 --> 00:02:11.500 all about flow direction and order. Just imagine 00:02:11.500 --> 00:02:15.159 data in ANN is like water. Okay. It always slows 00:02:15.159 --> 00:02:17.419 left to right and top to bottom. Always. It's 00:02:17.419 --> 00:02:20.080 a one -way street. You can't make it go backwards. 00:02:20.340 --> 00:02:23.550 Right. And here's a key thing. If your workflow 00:02:23.550 --> 00:02:26.389 splits into different paths, maybe using an IF 00:02:26.389 --> 00:02:29.569 node or something, the top path always runs completely 00:02:29.569 --> 00:02:32.770 first, start to finish, before the next path 00:02:32.770 --> 00:02:35.810 down even begins. Ah, okay. So that guarantees 00:02:35.810 --> 00:02:38.490 the order even if things look parallel. Exactly. 00:02:38.490 --> 00:02:40.889 It ensures that predictable order, which is super 00:02:40.889 --> 00:02:43.129 important when things get complicated with branching. 00:02:43.169 --> 00:02:45.729 So knowing that flow left to right, top to bottom, 00:02:45.770 --> 00:02:47.750 that really sets the stage. Okay, what's the 00:02:47.750 --> 00:02:50.229 next sort of fundamental law here? Next up is 00:02:50.229 --> 00:02:53.259 the one thing at a time law. Sequential execution. 00:02:53.960 --> 00:02:57.479 Think of your NEN workflow like a super focused 00:02:57.479 --> 00:03:00.659 chef, maybe a chef with only two hands. It prepares 00:03:00.659 --> 00:03:04.180 one dish, one task, one node completely before 00:03:04.180 --> 00:03:07.120 it even thinks about starting the next one. Even 00:03:07.120 --> 00:03:08.919 if you have branches that look like they're side 00:03:08.919 --> 00:03:12.240 by side, node A has to finish its entire job 00:03:12.240 --> 00:03:14.979 before node B kicks off. So it's not really true 00:03:14.979 --> 00:03:17.560 parallel processing then, not in the way some 00:03:17.560 --> 00:03:20.180 might think. Nope. It's very deliberate, very 00:03:20.180 --> 00:03:23.060 sequential. understanding this is key for timing 00:03:23.060 --> 00:03:25.139 you know figuring out how long things will take 00:03:25.139 --> 00:03:28.080 your total workflow time is basically the sum 00:03:28.080 --> 00:03:31.139 of each step one after the other got it sequential 00:03:31.139 --> 00:03:34.300 what's next and then we have the assembly line 00:03:34.300 --> 00:03:36.979 law some call it the one per input rule now this 00:03:36.979 --> 00:03:39.419 one is critical for managing costs especially 00:03:39.419 --> 00:03:41.860 when you're using outside services like AI okay 00:03:42.330 --> 00:03:44.530 Costs. Important. Yeah. Every node is like a 00:03:44.530 --> 00:03:46.590 station on an assembly line. It does its job 00:03:46.590 --> 00:03:48.750 once for every single item that arrives on its 00:03:48.750 --> 00:03:51.650 input. Ones per item. Right. So say you have 00:03:51.650 --> 00:03:54.129 one data object, like a JSON object, and inside 00:03:54.129 --> 00:03:56.870 it there's a list of 500 new leads. If you send 00:03:56.870 --> 00:03:59.789 that single box of leads to an AI node, that 00:03:59.789 --> 00:04:02.689 AI node runs just once. Ah, okay. It sees it 00:04:02.689 --> 00:04:05.750 as one job. Exactly. But if you first split those 00:04:05.750 --> 00:04:09.389 500 leads into 500 separate items and then send 00:04:09.389 --> 00:04:12.110 them to the AI node. Uh -oh. Yeah, that AI node 00:04:12.110 --> 00:04:15.849 runs 500 times. Whoa. Imagine the cost difference 00:04:15.849 --> 00:04:18.670 there. If you accidentally process 500 individual 00:04:18.670 --> 00:04:21.730 items instead of one batch, that's where costs 00:04:21.730 --> 00:04:24.089 could really, really add up fast. That's precisely 00:04:24.089 --> 00:04:26.610 it. Those details matter hugely for the bottom 00:04:26.610 --> 00:04:29.889 line. Okay, law number four, the choose your 00:04:29.889 --> 00:04:32.529 own adventure law. This is all about branching 00:04:32.529 --> 00:04:35.490 with conditions. Making decisions. Exactly. An 00:04:35.490 --> 00:04:38.350 N8N workflow isn't just a straight road. You've 00:04:38.350 --> 00:04:41.230 got nodes like IF and Switch. These are the points 00:04:41.230 --> 00:04:43.290 where your data gets to make choices. They allow 00:04:43.290 --> 00:04:45.850 for that dynamic if this, then that kind of logic. 00:04:46.089 --> 00:04:47.569 Makes sense. So you can build smarter systems 00:04:47.569 --> 00:04:49.870 that react differently. Like maybe if a new customer 00:04:49.870 --> 00:04:53.250 spends over, say, $500, their info goes down 00:04:53.250 --> 00:04:56.370 a special VIP onboarding path. Or maybe a support 00:04:56.370 --> 00:04:58.089 ticket comes in. And if it contains keywords 00:04:58.089 --> 00:05:00.740 like urgent or billing, it gets wrapped. routed 00:05:00.740 --> 00:05:03.279 straight to a specialized team. Right. That branching 00:05:03.279 --> 00:05:05.579 really opens up the customization. Okay. What's 00:05:05.579 --> 00:05:07.939 the last law that kind of ties these basics together? 00:05:08.199 --> 00:05:11.019 The final one is the safety switch law. That's 00:05:11.019 --> 00:05:14.939 the active and active toggle. Every single N8n 00:05:14.939 --> 00:05:17.920 workflow has this crucial switch, usually up 00:05:17.920 --> 00:05:19.819 in the top right corner of the editor. Okay. 00:05:19.939 --> 00:05:23.279 By default, it's set to off inactive. This is 00:05:23.279 --> 00:05:26.060 your safe zone, your development sandbox. The 00:05:26.060 --> 00:05:28.500 workflow will only run if you manually click 00:05:28.500 --> 00:05:30.839 that test workflow button. Right, for building 00:05:30.839 --> 00:05:32.720 and testing. Precisely. But when you're ready, 00:05:32.759 --> 00:05:35.180 you flip that switch to on -on. Now it's active. 00:05:35.240 --> 00:05:37.759 It's live. It'll actually start listening for 00:05:37.759 --> 00:05:40.519 its real -world triggers like that schedule you 00:05:40.519 --> 00:05:43.259 said or an incoming webhook. It's the absolute 00:05:43.259 --> 00:05:45.319 final step before anything goes into production. 00:05:45.439 --> 00:05:47.500 That makes sense. It's the master switch. So 00:05:47.500 --> 00:05:49.579 thinking about all these foundational laws, if 00:05:49.579 --> 00:05:51.519 I'm just starting out, which one should I really 00:05:51.519 --> 00:05:54.360 be most mindful of, especially regarding, say, 00:05:54.500 --> 00:05:57.079 efficiency or cost? Oh, the assembly line law 00:05:57.079 --> 00:05:59.639 for sure. That one directly controls how many 00:05:59.639 --> 00:06:01.879 times your nodes run based on the data items. 00:06:01.980 --> 00:06:04.259 Got it. The assembly line law. Okay, so we've 00:06:04.259 --> 00:06:06.839 got the basic physics down. Now let's talk about 00:06:06.839 --> 00:06:09.769 how these automations actually start. The starting 00:06:09.769 --> 00:06:12.449 pistols, your basic trigger notes. Right. Every 00:06:12.449 --> 00:06:14.610 automation needs a starting point, a kickoff. 00:06:14.949 --> 00:06:17.790 And these three essential triggers, they'll cover 00:06:17.790 --> 00:06:20.069 almost anything you need to build. Okay, what's 00:06:20.069 --> 00:06:23.129 the first one? First is the manual trigger. Think 00:06:23.129 --> 00:06:25.850 of this as the lab switch. This is your absolute 00:06:25.850 --> 00:06:28.050 best friend during development and testing. It's 00:06:28.050 --> 00:06:30.389 like that big red button in a science lab, you 00:06:30.389 --> 00:06:32.939 know. lets you run the experiment whenever you 00:06:32.939 --> 00:06:36.339 want. On demand. Yeah. Its only job is manual 00:06:36.339 --> 00:06:39.379 execution. You click it, it runs, you get instant 00:06:39.379 --> 00:06:42.899 feedback. Vital for checking your logic, seeing 00:06:42.899 --> 00:06:45.540 how data transforms, without waiting for some 00:06:45.540 --> 00:06:48.160 real event to happen. You'll probably click this 00:06:48.160 --> 00:06:51.240 button. hundreds, maybe thousands of times while 00:06:51.240 --> 00:06:53.199 you're building. So it's really about that quick 00:06:53.199 --> 00:06:55.800 iteration, that immediate feedback loop. Exactly 00:06:55.800 --> 00:06:58.300 that. Then you've got the schedule trigger, or 00:06:58.300 --> 00:07:00.180 you could call it the alarm clock. Okay. This 00:07:00.180 --> 00:07:02.459 is your workhorse for any time -based automation. 00:07:02.839 --> 00:07:05.459 Super simple, super powerful. It's basically 00:07:05.459 --> 00:07:07.939 an alarm clock for your workflows. You tell it 00:07:07.939 --> 00:07:11.019 when to run every hour, every day at 8 a .m., 00:07:11.019 --> 00:07:12.819 first Monday of the month, whatever. Perfect 00:07:12.819 --> 00:07:15.529 for routine stuff. Totally. Sending daily reports, 00:07:15.750 --> 00:07:19.029 weekly data backups, processing monthly invoices, 00:07:19.310 --> 00:07:22.050 all that recurring stuff. Makes sense. And what 00:07:22.050 --> 00:07:23.949 about when something happens outside of NAN, 00:07:24.029 --> 00:07:26.569 like in another app, that my workflow needs to 00:07:26.569 --> 00:07:28.689 react to? Ah, that's where app event triggers 00:07:28.689 --> 00:07:31.610 come in. Or the motion detector, if you like. 00:07:32.029 --> 00:07:35.470 These are key for building really smart reactive 00:07:35.470 --> 00:07:38.269 automations. Reactive, okay. Yeah, instead of 00:07:38.269 --> 00:07:40.149 your workflow having to constantly ask another 00:07:40.149 --> 00:07:43.790 app, anything new. Anything new, which is called 00:07:43.790 --> 00:07:45.610 polling, and it's kind of inefficient. Yeah. 00:07:45.689 --> 00:07:47.550 These triggers just sit there and wait patiently. 00:07:47.629 --> 00:07:49.689 They wait for the other app to send a signal 00:07:49.689 --> 00:07:53.449 to NANN. Ah, so the app tells NN. Right. The 00:07:53.449 --> 00:07:55.230 workflow only runs when something has actually 00:07:55.230 --> 00:07:57.230 happened. It's way more efficient. Think like 00:07:57.230 --> 00:08:00.370 a new row gets added to a Google Sheet or a specific 00:08:00.370 --> 00:08:02.649 email lands in your Gmail inbox. That sounds 00:08:02.649 --> 00:08:05.939 much smarter, yeah. Less wasteful. Okay, so for 00:08:05.939 --> 00:08:08.459 someone just starting, which trigger is really 00:08:08.459 --> 00:08:10.399 their best friend? Where should they begin? Oh, 00:08:10.439 --> 00:08:12.519 the manual trigger, definitely. It's your go 00:08:12.519 --> 00:08:15.300 -to for all testing and building. Manual trigger. 00:08:15.480 --> 00:08:17.779 Got it. Okay, now we're getting into a really 00:08:17.779 --> 00:08:20.860 core section, the heavy machinery, universal 00:08:20.860 --> 00:08:24.180 data processing. The factory floor. Right. This 00:08:24.180 --> 00:08:26.100 is really the heart of NEN, isn't it, where the 00:08:26.100 --> 00:08:28.920 actual transformation happens. Mastering these, 00:08:29.100 --> 00:08:32.389 what, seven? heavy machinery nodes this is what 00:08:32.389 --> 00:08:34.789 lets you take that messy raw data and turn it 00:08:34.789 --> 00:08:36.789 into something clean structured and actually 00:08:36.789 --> 00:08:39.669 valuable absolutely first up is the log splitter 00:08:39.669 --> 00:08:42.289 that's the split out log splitter okay it takes 00:08:42.289 --> 00:08:44.769 a single item maybe one that has a list of things 00:08:44.769 --> 00:08:47.450 inside it technically an array and it Breaks 00:08:47.450 --> 00:08:50.789 that list apart into multiple individual items. 00:08:50.850 --> 00:08:53.190 One item for each thing in the original list. 00:08:53.409 --> 00:08:55.529 Why would you do that? Super useful if you need 00:08:55.529 --> 00:08:57.850 to do something with each item individually. 00:08:58.190 --> 00:09:00.330 Like imagine you have a spreadsheet list of people. 00:09:00.629 --> 00:09:03.490 You use split out to get one item per person. 00:09:03.690 --> 00:09:06.190 So you can then send each one a personalized 00:09:06.190 --> 00:09:10.309 email. Process them one by one. And if you need 00:09:10.309 --> 00:09:12.230 to put them back together. That's where the data 00:09:12.230 --> 00:09:14.590 blender comes in the aggregate node. It does 00:09:14.590 --> 00:09:17.519 the exact opposite of split out. It takes a whole 00:09:17.519 --> 00:09:20.320 stream of individual items and combines them 00:09:20.320 --> 00:09:22.980 back into one single item that contains a consolidated 00:09:22.980 --> 00:09:25.039 list of all of them. So they're like a pair? 00:09:25.500 --> 00:09:28.340 Very often, yeah. You split data out, do something 00:09:28.340 --> 00:09:30.840 to each piece, then you aggregate the results 00:09:30.840 --> 00:09:32.940 back together, maybe into a summary report or 00:09:32.940 --> 00:09:35.379 something. Got it. Split and aggregate, like 00:09:35.379 --> 00:09:37.779 breathing in and out with data. Yeah, kind of 00:09:37.779 --> 00:09:41.320 like that. Okay, next is the data janitor. This 00:09:41.320 --> 00:09:43.779 is the edit fields node or sometimes called the 00:09:43.779 --> 00:09:46.799 set node. This one is your absolute workhorse. 00:09:46.879 --> 00:09:49.279 You'll use this constantly. The janitor, huh? 00:09:49.659 --> 00:09:52.379 Cleans things up. Totally. It's for cleaning, 00:09:52.559 --> 00:09:55.159 transforming, reorganizing your data, anything 00:09:55.159 --> 00:09:57.840 really. Combine a first name and last name field 00:09:57.840 --> 00:10:00.620 into a full name. Format dates so they're all 00:10:00.620 --> 00:10:02.879 consistent. Make sure phone numbers look the 00:10:02.879 --> 00:10:05.340 same. Get rid of fields you don't need to keep 00:10:05.340 --> 00:10:07.519 things tidy. Sounds incredibly versatile. Like 00:10:07.519 --> 00:10:09.320 you can really sculpt the data. It really is. 00:10:09.399 --> 00:10:12.350 Okay, next. The bouncer. That's the IF node. 00:10:12.570 --> 00:10:15.370 Like at a club. Sort of. It's for simple binary 00:10:15.370 --> 00:10:18.909 decisions. Yes or no. True or false. It looks 00:10:18.909 --> 00:10:21.289 at each piece of data, checks it against one 00:10:21.289 --> 00:10:23.350 condition you set, and then sends it down one 00:10:23.350 --> 00:10:26.429 of two paths. The true path if it meets the condition, 00:10:26.610 --> 00:10:29.809 the false path if it doesn't. Simple split. True, 00:10:29.870 --> 00:10:33.090 false. Got it. But what if the decision is more 00:10:33.090 --> 00:10:35.960 complex? more than just two options. Right. For 00:10:35.960 --> 00:10:37.879 that, you need the train conductor. That's the 00:10:37.879 --> 00:10:39.759 switch node. Train conductor. Yeah. Think of 00:10:39.759 --> 00:10:42.019 it like the IF node's more powerful sibling. 00:10:42.659 --> 00:10:44.879 It's perfect when you have more than just two 00:10:44.879 --> 00:10:47.720 possible outcomes. It acts like a conductor at 00:10:47.720 --> 00:10:50.659 a big station, looks at a specific value in your 00:10:50.659 --> 00:10:52.899 data, and routes that whole train of data down 00:10:52.899 --> 00:10:55.460 one of many different tracks based on that value. 00:10:56.350 --> 00:10:59.049 Okay, multiple routes. Exactly. Really good for 00:10:59.049 --> 00:11:01.389 things like categorizing support tickets based 00:11:01.389 --> 00:11:03.669 on their type or maybe processing orders differently 00:11:03.669 --> 00:11:05.789 depending on the country they came from. It's 00:11:05.789 --> 00:11:07.909 much cleaner and easier to manage than trying 00:11:07.909 --> 00:11:10.230 to chain a bunch of IF nodes together. Yeah, 00:11:10.289 --> 00:11:12.330 I can see how nested IFs could get messy fast. 00:11:12.629 --> 00:11:15.490 Okay, so IF and switch send data down different 00:11:15.490 --> 00:11:18.330 paths. How do you bring those paths back together? 00:11:18.809 --> 00:11:21.090 Good question. That's where the rail yard switch 00:11:21.090 --> 00:11:23.950 man comes in, the merge node. It's the essential 00:11:23.950 --> 00:11:27.110 partner to IF and switch. If your switch node 00:11:27.110 --> 00:11:29.850 sent trains down three different tracks, the 00:11:29.850 --> 00:11:32.610 merge node sits at the end, patiently waits for 00:11:32.610 --> 00:11:34.429 all three of those branches to finish whatever 00:11:34.429 --> 00:11:37.370 they were doing, and then it combines the data 00:11:37.370 --> 00:11:41.110 from all of them back into a single unified stream 00:11:41.110 --> 00:11:43.350 moving forward. So it waits for everyone and 00:11:43.350 --> 00:11:44.809 brings it all back together, ensures nothing 00:11:44.809 --> 00:11:48.529 gets lost. Exactly, ensures continuity. Okay, 00:11:48.570 --> 00:11:50.730 one more in this section. What about those really 00:11:50.730 --> 00:11:53.610 tricky data transformations? The ones where none 00:11:53.610 --> 00:11:55.789 of the standard nodes seem to quite cut it? Yeah, 00:11:55.850 --> 00:11:58.269 the weird edge cases. For those, you have the 00:11:58.269 --> 00:12:01.149 get -out -of -jail -free card. The code node. 00:12:01.389 --> 00:12:04.429 Uh -oh. Code? Sounds intimidating. It can seem 00:12:04.429 --> 00:12:07.029 that way at first, yeah. But it's your ultimate 00:12:07.029 --> 00:12:09.789 fallback. Your solution for any complex data 00:12:09.789 --> 00:12:11.889 wrangling that the other nodes just can't handle 00:12:11.889 --> 00:12:15.129 easily. But here's the secret. You don't actually 00:12:15.129 --> 00:12:17.169 need to be a programmer to use it effectively 00:12:17.169 --> 00:12:20.769 these days. Really? Well, AI. I mean, I still 00:12:20.769 --> 00:12:22.830 wrestle with prompt drift myself sometimes, you 00:12:22.830 --> 00:12:25.409 know. That's when you're asking an AI to do something 00:12:25.409 --> 00:12:27.850 and its answers start kind of wandering away 00:12:27.850 --> 00:12:29.870 from what you originally wanted. It happens. 00:12:30.129 --> 00:12:33.559 Yeah, I've seen that. Using something like ChatGPT 00:12:33.559 --> 00:12:36.059 to help write the little snippets of JavaScript 00:12:36.059 --> 00:12:38.899 for the code node, it's been a total game changer 00:12:38.899 --> 00:12:41.759 for me and for lots of people. You just describe 00:12:41.759 --> 00:12:44.340 what you need in plain English, maybe give it 00:12:44.340 --> 00:12:46.519 an example of your input data and what you want 00:12:46.519 --> 00:12:48.399 the output to look like. And it writes the code. 00:12:48.620 --> 00:12:51.620 Often, yeah. Or gets you 90 % of the way there. 00:12:51.779 --> 00:12:54.360 You copy it, paste it into the code node, and 00:12:54.360 --> 00:12:55.919 suddenly you've got this custom transformation 00:12:55.919 --> 00:12:58.820 without writing a line of code yourself. Wow, 00:12:58.919 --> 00:13:00.340 that actually makes it sound really accessible. 00:13:00.460 --> 00:13:03.080 That's empowering. Okay, thinking about all these 00:13:03.080 --> 00:13:07.559 data tools, IF, switch, merge, code, which one 00:13:07.559 --> 00:13:11.039 is really the best bet for handling those complex 00:13:11.039 --> 00:13:14.659 decisions with many possible outcomes? Definitely 00:13:14.659 --> 00:13:17.240 the switch node. It's built to efficiently route 00:13:17.240 --> 00:13:19.379 data down many different tracks based on conditions. 00:13:19.759 --> 00:13:23.480 Switch node. Got it. Madrol sponsor Reed Placeholder. 00:13:25.200 --> 00:13:27.820 Welcome back. We've covered the fundamental laws, 00:13:27.980 --> 00:13:29.960 the triggers, the heavy machinery for data processing. 00:13:30.379 --> 00:13:33.500 Now let's get into category four, the gates to 00:13:33.500 --> 00:13:36.519 the world. This is all about connectivity and 00:13:36.519 --> 00:13:39.960 APIs. Connecting N8n to everything else. Right. 00:13:39.960 --> 00:13:41.899 These nodes are basically your passport. They 00:13:41.899 --> 00:13:44.799 let your N8n workflows talk to, send data to, 00:13:44.940 --> 00:13:47.500 receive data from pretty much any other application 00:13:47.500 --> 00:13:49.779 or service on the internet. And top of the list 00:13:49.779 --> 00:13:52.600 here is the librarian on demand. That's the HTTP 00:13:52.600 --> 00:13:56.029 request node. Okay. This one. Honestly, it might 00:13:56.029 --> 00:13:58.309 be the single most powerful node in all of N8n. 00:13:58.429 --> 00:14:00.649 It's your universal connector. Your key to the 00:14:00.649 --> 00:14:02.710 whole digital kingdom, really. High praise. What 00:14:02.710 --> 00:14:04.850 does it do? Its main job is to reach out to any 00:14:04.850 --> 00:14:07.190 service on the internet that offers an API. An 00:14:07.190 --> 00:14:09.450 API is just like a specific menu of commands 00:14:09.450 --> 00:14:11.549 that lets different software talk to each other. 00:14:11.629 --> 00:14:13.049 Right, the application programming interface. 00:14:13.600 --> 00:14:17.340 Exactly. So you use this node to either EAT data 00:14:17.340 --> 00:14:19.820 -like, pull information from another service, 00:14:19.960 --> 00:14:22.679 or POST data -like, send information to another 00:14:22.679 --> 00:14:25.259 service. Once you get comfortable with this node, 00:14:25.360 --> 00:14:27.559 you're basically never limited by the pre -built 00:14:27.559 --> 00:14:30.860 integrations NAN offers. If a service has an 00:14:30.860 --> 00:14:32.820 API, you can probably talk to it with this node. 00:14:32.980 --> 00:14:34.919 That really does sound like it breaks down almost 00:14:34.919 --> 00:14:37.840 any barrier. Okay, but what if I need other services 00:14:37.840 --> 00:14:41.500 to contact my workflow to send data in? Ah, right. 00:14:42.120 --> 00:14:46.120 For that you need the digital mailbox. The webhook 00:14:46.120 --> 00:14:48.059 node. Digital mailbox. Yeah, it's pretty much 00:14:48.059 --> 00:14:50.659 the exact opposite of the HTTP request node. 00:14:50.799 --> 00:14:52.960 Instead of your workflow reaching out, this node 00:14:52.960 --> 00:14:55.500 creates a unique, special URL. It's like setting 00:14:55.500 --> 00:14:58.080 up your own private digital mailbox. Okay. Other 00:14:58.080 --> 00:15:00.240 services can then send data to that specific 00:15:00.240 --> 00:15:02.480 URL, and boom, it triggers your NEN workflow 00:15:02.480 --> 00:15:05.120 instantly. This is how you build those super 00:15:05.120 --> 00:15:07.100 reactive automations that kick off immediately 00:15:07.100 --> 00:15:09.659 when something happens elsewhere, like a payment 00:15:09.659 --> 00:15:11.940 completing in Stripe, or someone submitting a 00:15:11.940 --> 00:15:14.179 form on your website, or maybe a message hitting 00:15:14.179 --> 00:15:16.309 a specific site. slack channel so it just sits 00:15:16.309 --> 00:15:18.330 there listening for incoming messages at that 00:15:18.330 --> 00:15:21.870 url got it and when a message arrives how do 00:15:21.870 --> 00:15:25.269 you like confirm you got it is there a digital 00:15:25.269 --> 00:15:27.710 handshake There is, and it's important. That's 00:15:27.710 --> 00:15:29.950 the delivery confirmation, the respond to webhook 00:15:29.950 --> 00:15:32.590 node. It's a simple node, but it's really crucial 00:15:32.590 --> 00:15:35.129 digital etiquette. When another service sends 00:15:35.129 --> 00:15:37.889 data to your webhook URL, it's often expecting 00:15:37.889 --> 00:15:40.830 a quick reply like, yep, got it, thanks. This 00:15:40.830 --> 00:15:43.889 node's whole job is to send that immediate, roger 00:15:43.889 --> 00:15:46.590 that, message received signal back. Why is that 00:15:46.590 --> 00:15:49.149 so important? Well, it prevents the sending service 00:15:49.149 --> 00:15:51.409 from thinking the message failed. If it doesn't 00:15:51.409 --> 00:15:53.350 get that confirmation, it might try sending the 00:15:53.350 --> 00:15:56.490 same data again and again. which can cause chaos. 00:15:57.190 --> 00:15:59.809 So this little node helps make your integrations 00:15:59.809 --> 00:16:02.850 robust and reliable. Makes sense. Prevents duplicates 00:16:02.850 --> 00:16:05.909 and errors. Okay, quick check. If I want my workflow 00:16:05.909 --> 00:16:08.809 to get data from pretty much any website or service 00:16:08.809 --> 00:16:11.730 out there, which node is my main tool? The HTTP 00:16:11.730 --> 00:16:14.289 request node. That's your universal connector 00:16:14.289 --> 00:16:17.029 for grabbing data from the web. HTTP request. 00:16:17.149 --> 00:16:19.759 Okay. All right. We've reached our final category, 00:16:19.879 --> 00:16:22.679 the brains and the library. This covers AI and 00:16:22.679 --> 00:16:25.860 storage. Adding intelligence and giving the data 00:16:25.860 --> 00:16:28.360 a home. Exactly. These are the nodes that add 00:16:28.360 --> 00:16:30.759 that layer of judgment and then provide a reliable 00:16:30.759 --> 00:16:33.419 place to keep all the valuable data you've processed. 00:16:33.919 --> 00:16:36.440 Let's start with storage. Okay. For storing data, 00:16:36.659 --> 00:16:40.059 we've got the librarian's filing cabinet. This 00:16:40.059 --> 00:16:42.539 really refers mostly to Google Sheets, but also 00:16:42.539 --> 00:16:45.360 other databases. Filing cabinet, makes sense. 00:16:45.480 --> 00:16:47.700 Yeah, your automations need somewhere to put 00:16:47.700 --> 00:16:50.179 the final results, right? The process data. Lots 00:16:50.179 --> 00:16:52.500 of options exist, but honestly, Google Sheets 00:16:52.500 --> 00:16:54.899 is usually the easiest, most user -friendly place 00:16:54.899 --> 00:16:57.600 to start. Easy to see, easy to share. Exactly, 00:16:57.759 --> 00:16:59.860 and easy to connect any end to. Then, you know, 00:16:59.879 --> 00:17:01.820 as your needs get more complex, maybe you graduate, 00:17:01.919 --> 00:17:04.059 you might move up to something like Airtable, 00:17:04.160 --> 00:17:05.799 which is kind of like a database on steroids, 00:17:06.019 --> 00:17:08.920 or even a proper database like Supabase or Postgres. 00:17:08.910 --> 00:17:10.970 But the idea is the same. It's the organized 00:17:10.970 --> 00:17:13.910 library where all your valuable automated work 00:17:13.910 --> 00:17:16.730 ends up. A structured home for the output. Okay. 00:17:16.950 --> 00:17:20.609 And what about adding the brains, the AI part, 00:17:20.769 --> 00:17:24.190 the AI brain trust? Right. Now, the absolute 00:17:24.190 --> 00:17:27.549 key with AI in NAN is to use it intelligently. 00:17:27.930 --> 00:17:30.009 And by that, I mean use it only when you actually 00:17:30.009 --> 00:17:32.690 need human -like judgment or complex understanding. 00:17:33.049 --> 00:17:35.269 Don't use it for simple stuff. Exactly. Don't 00:17:35.269 --> 00:17:38.369 pay for an expensive AI model to, like, add two 00:17:38.369 --> 00:17:40.990 numbers together or format some text when a basic 00:17:40.990 --> 00:17:43.549 built -in node can do it better, faster, and 00:17:43.549 --> 00:17:46.490 for free. Use the right tool for the job. Okay. 00:17:46.569 --> 00:17:49.390 So when do you use it? What are the types? There 00:17:49.390 --> 00:17:52.329 are basically two main types of AI brains you'll 00:17:52.329 --> 00:17:55.690 use in AN. First is the specialist. This is your 00:17:55.690 --> 00:17:58.809 basic LLM chain node. Honestly, this node will 00:17:58.809 --> 00:18:01.890 handle probably 90 % of the AI tasks you'll ever 00:18:01.890 --> 00:18:04.670 need. Think of it as a highly focused expert. 00:18:04.809 --> 00:18:07.589 It's great for single -step specific jobs, things 00:18:07.589 --> 00:18:09.829 like analyzing the sentiment of some text, is 00:18:09.829 --> 00:18:11.950 it positive or negative, or extracting specific 00:18:11.950 --> 00:18:14.349 pieces of beta from a paragraph like names or 00:18:14.349 --> 00:18:16.630 dates, or maybe doing basic classification, like 00:18:16.630 --> 00:18:18.829 figuring out what category an email belongs to. 00:18:18.950 --> 00:18:22.210 So focused, specific AI tasks. Exactly. Then 00:18:22.210 --> 00:18:24.529 you have the manager. This is the AI agent node. 00:18:24.690 --> 00:18:27.480 The manager. Sounds more complex. It is, and 00:18:27.480 --> 00:18:29.680 often more expensive to run, too. You should 00:18:29.680 --> 00:18:31.700 really only bring in the manager when you need 00:18:31.700 --> 00:18:34.099 an AI that can handle more complex scenarios. 00:18:34.759 --> 00:18:37.259 Like, maybe it needs to have an ongoing conversation 00:18:37.259 --> 00:18:40.259 where it remembers previous turns. Or maybe it 00:18:40.259 --> 00:18:42.059 needs to use several different tools, like searching 00:18:42.059 --> 00:18:45.099 the web, then summarizing, then saving the result 00:18:45.099 --> 00:18:47.619 to solve a multi -step problem. Okay, so it's 00:18:47.619 --> 00:18:50.339 for more involved multi -step reasoning or tasks 00:18:50.339 --> 00:18:52.940 requiring memory. Makes sense. So, quick question 00:18:52.940 --> 00:18:55.670 then. When should I choose... The specialist 00:18:55.670 --> 00:18:58.690 AI versus the manager AI. Yeah. Good rule of 00:18:58.690 --> 00:19:01.490 thumb. Specialist for those focused single tasks. 00:19:01.809 --> 00:19:04.130 Manager for the complex multi -step problems, 00:19:04.210 --> 00:19:06.390 especially if they need memory or multiple tools. 00:19:06.869 --> 00:19:09.490 Specialist for single tasks. Manager for complex 00:19:09.490 --> 00:19:12.230 problems. Got it. Wow, this has been really clarifying. 00:19:12.369 --> 00:19:15.710 We've walked through these 14 essential NA nodes, 00:19:16.049 --> 00:19:18.269 broken them down into those five key categories. 00:19:18.450 --> 00:19:20.730 And what really stands out, I think, is that 00:19:20.730 --> 00:19:24.099 80 -20 rule in action. True mastery, it seems, 00:19:24.299 --> 00:19:26.339 isn't really about knowing every single one of 00:19:26.339 --> 00:19:28.559 those thousand plus nodes. It's about deeply 00:19:28.559 --> 00:19:30.859 understanding how to creatively combine these 00:19:30.859 --> 00:19:34.440 core 14. That shift in thinking, that's what 00:19:34.440 --> 00:19:36.740 takes you from being stuck in tutorial hell to 00:19:36.740 --> 00:19:38.799 actually being a professional builder. Absolutely. 00:19:39.299 --> 00:19:41.660 These 14 nodes we've talked about today, they 00:19:41.660 --> 00:19:44.680 genuinely make up a complete toolkit. If you 00:19:44.680 --> 00:19:46.680 get comfortable with these, you really can tackle 00:19:46.680 --> 00:19:49.019 almost any automation challenge you're likely 00:19:49.019 --> 00:19:51.740 to face. Okay. So here's the challenge for you 00:19:51.740 --> 00:19:55.089 listening. Your mission, should you choose to 00:19:55.089 --> 00:19:58.569 accept it. Stop watching the tutorials for a 00:19:58.569 --> 00:20:02.130 bit. Start building. Find one thing in your work 00:20:02.130 --> 00:20:04.769 or even your personal life that's repetitive, 00:20:05.009 --> 00:20:07.509 maybe a bit painful, something you dread doing 00:20:07.509 --> 00:20:09.950 manually. Yeah, find that pain point. Exactly. 00:20:10.289 --> 00:20:12.670 Then try to map out a simple solution for it 00:20:12.670 --> 00:20:15.190 using only the nodes we talked about today, just 00:20:15.190 --> 00:20:18.680 these 14. Then build it. Test it. And definitely 00:20:18.680 --> 00:20:21.099 break it. Yeah. Throw messy real -world data 00:20:21.099 --> 00:20:23.140 at it. See where it fails. That's how you learn. 00:20:23.220 --> 00:20:25.299 For sure. Find the breaking points, then iterate. 00:20:25.720 --> 00:20:29.359 Improve it. And then launch it. Put it into action. 00:20:29.380 --> 00:20:31.740 See how it performs in the real world and keep 00:20:31.740 --> 00:20:34.579 learning from that. And just remember, the real 00:20:34.579 --> 00:20:37.940 power, the real creativity, it doesn't come from 00:20:37.940 --> 00:20:40.799 knowing a thousand tools superficially. It comes 00:20:40.799 --> 00:20:43.039 from knowing how to combine a few essential tools 00:20:43.039 --> 00:20:46.019 in really smart ways. And this deep dive, it's 00:20:46.019 --> 00:20:48.599 given you that complete essential toolkit. Couldn't 00:20:48.599 --> 00:20:50.180 have said it better. Thank you so much for joining 00:20:50.180 --> 00:20:52.259 us on this deep dive. My pleasure. Until next 00:20:52.259 --> 00:20:53.900 time, out to your own music.