WEBVTT 00:00.040 --> 00:01.000 Welcome back. 00:01.040 --> 00:04.440 Today I'm going to walk you through how to work with community nodes. 00:05.040 --> 00:08.000 Now let me quickly explain what a community node actually is. 00:08.400 --> 00:15.480 So it's basically a pre-built connector that someone from the community has created to solve a specific 00:15.480 --> 00:17.240 problem or add functionality. 00:17.680 --> 00:23.000 So to connect a platform, app or service that N810 doesn't have it. 00:23.360 --> 00:25.640 So the native node or direct integration. 00:26.400 --> 00:29.600 So far you would need to use the HTTP request node. 00:30.600 --> 00:36.920 So instead of you having to mess around with APIs, documentation, finding parameters, JSON formats, 00:37.440 --> 00:39.640 they have already done all that work for you. 00:39.920 --> 00:44.040 So they build these nodes to handle all the backend stuff. 00:44.760 --> 00:48.000 And the only thing you need to do is provide your API keys. 00:48.360 --> 00:54.560 That's going to save you a lot of time because instead of figuring out how to set up API connections. 00:54.880 --> 00:59.230 So all these credentials parameters and so on, we can use community Notes. 00:59.510 --> 01:03.910 This applies whether you are using a cloud or you are hosting an item. 01:05.630 --> 01:12.950 So on the 27th of May, the N810 team announced that this community nodes are now available directly 01:12.950 --> 01:14.710 in their cloud platform. 01:15.110 --> 01:21.230 So this is actually a big deal because up until now, if you wanted to use this, you had to self-host 01:21.230 --> 01:26.030 N810 and set up everything manually and scroll down. 01:28.750 --> 01:37.190 You can see that they're starting with 25 of the most popular community nodes and partner integrations. 01:37.390 --> 01:42.670 So they are planning to gradually expand this library and adding more verified nodes over time. 01:43.470 --> 01:49.350 So the goal is to make it much easier to connect to pretty much any service you need without setting 01:49.350 --> 01:53.510 up and configuring sometimes very complex HTTP requests. 01:54.150 --> 01:59.570 They are investing time into it because they discovered that these community nodes have been really 01:59.570 --> 02:06.130 successful and people are using them to solve real problems, and it makes sense to make them more accessible 02:06.130 --> 02:06.810 to everyone. 02:07.970 --> 02:13.050 Now, in this article, you can read that the ones that are going to be available include things like 02:13.090 --> 02:20.010 tablet for search, server API, even 11 labs for AI voice beyond presence. 02:20.210 --> 02:27.090 To create realistic avatar video agents, you will also find nodes supported by chat data. 02:27.130 --> 02:28.010 Click send. 02:28.530 --> 02:31.210 It could run, scrape less and so on. 02:31.530 --> 02:36.290 So all these nodes will be available to install directly from the editor. 02:37.170 --> 02:39.250 Now there is one important thing you need to check. 02:39.250 --> 02:43.450 First you have to be running version 1.94. 02:43.970 --> 02:47.890 So I will go to my n810 and click on admin panel. 02:51.130 --> 02:56.200 And here you can see that I'm currently running version 1.10.1. 02:56.960 --> 02:59.320 In case you are running the older version. 03:02.600 --> 03:05.800 You will see a notification that the update is available. 03:06.320 --> 03:09.800 So just simply click on it and update your instance. 03:11.440 --> 03:13.160 Now here is what we need to do next. 03:13.680 --> 03:17.200 In the admin panel we need to click on settings. 03:18.280 --> 03:19.120 Scroll down. 03:21.400 --> 03:23.600 And you can see verified community nodes. 03:23.640 --> 03:24.440 Turn that on. 03:26.760 --> 03:28.360 And then click on Save Changes. 03:30.480 --> 03:33.360 So this is going to restart your workspace. 03:33.360 --> 03:37.000 So make sure you have saved any workflows you are working on. 03:37.320 --> 03:44.400 Now when I go back to my dashboard you will see it's being back up and making the changes. 03:45.040 --> 03:52.440 So once it turns green, we'll be able to click open and get back into our instance. 03:53.390 --> 03:53.710 Yes. 03:53.710 --> 03:54.350 Perfect. 03:55.110 --> 03:58.950 So let's open the instance now that we are back in. 03:59.270 --> 04:00.910 If we go to settings again. 04:03.230 --> 04:06.470 You will notice that there is a new option community nodes. 04:07.110 --> 04:13.230 This is where you can install community nodes that have been verified by Natan directly from this panel. 04:14.070 --> 04:19.390 This is much easier than the old way where you had to install things manually if you are self-hosting. 04:20.470 --> 04:22.910 Now let's create a new workflow and see how this works. 04:23.550 --> 04:26.990 Let's say I want to use 11 labs for text to speech. 04:27.310 --> 04:33.430 Normally, without a pre-built community node for 11 labs, I would need to use the HTTP request node. 04:35.510 --> 04:37.630 So let's add HTTP request node. 04:38.950 --> 04:44.950 I'm going to show you what I mean, and I would have to go through the API documentation, figure out 04:44.950 --> 04:47.950 all the parameters, set up the authentication. 04:48.070 --> 04:49.430 So it's quite a process. 04:49.550 --> 04:52.450 Let's do it now to see how tedious it can be. 04:52.490 --> 04:58.610 And then we'll use the 11 labs community node to show you how simple it is and how much time you can 04:58.610 --> 04:59.050 save. 04:59.450 --> 05:08.090 So for the method we need to use post and I need to go to 11 labs API documentation. 05:13.290 --> 05:17.050 Here we need to find the API reference section. 05:17.050 --> 05:20.410 So text to speech endpoints. 05:20.650 --> 05:24.530 Basically what we need to do we need to copy this URL. 05:25.730 --> 05:30.210 Go back to n810 and paste it into this field. 05:31.170 --> 05:33.210 Then I need to set up a headers. 05:34.690 --> 05:36.170 So I need to send headers. 05:36.170 --> 05:38.370 So now I need to find the header name. 05:38.610 --> 05:41.130 So I need to go back to API documentation. 05:44.290 --> 05:47.170 As you can see the headers are required. 05:47.530 --> 05:48.810 So I need to copy this. 05:48.810 --> 05:48.920 Is. 05:51.880 --> 05:55.080 Go back to 2010 and paste it right here. 05:55.560 --> 05:58.480 And for the value I need to get my API keys. 05:59.480 --> 06:07.400 So I need to go into my 11 labs account to go to at the at the bottom left corner. 06:07.760 --> 06:09.480 I need to go to API keys. 06:09.640 --> 06:11.480 And here I can create API keys. 06:13.080 --> 06:14.200 So let's create new one. 06:14.960 --> 06:15.960 Community notes. 06:17.080 --> 06:17.560 Demo. 06:21.280 --> 06:21.840 Confirm. 06:21.840 --> 06:22.400 Create. 06:23.280 --> 06:24.080 Create key. 06:26.000 --> 06:27.400 Now copy API key. 06:27.600 --> 06:31.720 Go back to ten and paste it into the value field. 06:32.400 --> 06:40.360 Then I need to toggle Send Body and go to API docs again to add the required fields. 06:43.280 --> 06:46.240 I need to scroll down and find request. 06:47.430 --> 06:51.710 As you can see, the text string is required, so let's copy it. 06:54.350 --> 06:55.910 Let's go back to N810. 06:58.110 --> 07:00.910 We're going to leave the body content type as JSON. 07:01.350 --> 07:09.670 Paste text into the name field, and in the value field I will put something like either. 07:11.830 --> 07:12.910 Community nodes. 07:15.790 --> 07:16.550 Are awesome. 07:21.150 --> 07:22.950 And this is how the process looks like. 07:22.990 --> 07:28.310 Or alternatively I can use the curl command from the API documentation. 07:28.310 --> 07:29.750 So copy this curl command. 07:31.990 --> 07:35.350 And instead of adding each field manually. 07:37.630 --> 07:40.150 I can do this this way. 07:41.430 --> 07:49.500 So I'm going to add another HTTP request node I'm going to show you how to set up it, uh, in a different 07:49.500 --> 07:49.820 way. 07:53.060 --> 07:53.780 So what can I do? 07:53.780 --> 07:54.380 I can. 07:57.980 --> 07:58.980 Uh, import curl. 08:04.660 --> 08:08.820 Paste the curl command here and then click import. 08:10.180 --> 08:11.860 But I still need to configure it. 08:11.860 --> 08:14.500 So I need to add my credentials and so on. 08:14.780 --> 08:21.420 Also to use other actions like creating a voice clone or transcribing audio I would need to use different 08:21.420 --> 08:22.700 API endpoints. 08:22.700 --> 08:28.420 So that means I would need to add another HTTP request node going through the documentation again, 08:28.660 --> 08:33.020 and configuring each node to set up the connection for different actions. 08:33.060 --> 08:37.940 Also, I would need to add the voice ID to this URL. 08:38.340 --> 08:40.780 I need to go back to my 11 labs account. 08:44.320 --> 08:46.520 Go to text to speech section. 08:48.240 --> 08:49.360 Go to voices. 08:49.960 --> 08:54.520 Copy the voice ID of the voice of our choice. 08:55.400 --> 08:59.400 Go back to ne10 and include the voice ID in this URL. 09:00.880 --> 09:06.840 So replace everything after slash and paste the voice ID here. 09:08.520 --> 09:11.560 All of this requires a lot of manual setup. 09:12.720 --> 09:19.000 But now with community nodes, the process of setting up connections with services like for example, 09:19.000 --> 09:21.200 11 labs is much, much easier. 09:22.120 --> 09:24.200 Look how much simpler this becomes. 09:24.880 --> 09:26.560 So once in the admin panel. 09:29.560 --> 09:32.120 You turn on the verified community nodes. 09:33.000 --> 09:34.120 So in the settings. 09:36.520 --> 09:44.790 You turn on this option you will be able to install community build node packages very easily and quickly. 09:46.150 --> 09:47.910 So let's go back to our dashboard. 09:56.790 --> 10:00.230 And now I can simply search for it overlaps. 10:00.670 --> 10:03.670 And we have this clean node with the 11 labs logo. 10:04.350 --> 10:06.630 And all I need to do is add my credential. 10:07.470 --> 10:10.310 So you can see this um tick symbol. 10:10.470 --> 10:13.390 So this is an official node maintained by Level Labs. 10:13.590 --> 10:16.830 So this that means that this is community node. 10:20.510 --> 10:21.470 So let's select it. 10:24.390 --> 10:26.390 Let's use this action. 10:27.790 --> 10:29.150 So convert text to speech. 10:29.790 --> 10:32.590 And all I need to do is add my credential. 10:36.790 --> 10:38.030 So create new credential. 10:39.030 --> 10:41.100 Go to your Level Apps account. 10:43.380 --> 10:46.820 Go to settings API keys. 10:48.620 --> 10:49.820 Copy your API key. 10:55.940 --> 10:56.260 Create. 10:56.260 --> 10:56.940 Create key. 10:58.740 --> 11:02.820 Let's toggle off this restriction to give it access to all the actions. 11:03.380 --> 11:09.420 You need to remember that an unrestricted API key can be significantly more harmful if leaked. 11:10.060 --> 11:13.260 Please consider restricting the API key to specific actions. 11:13.300 --> 11:16.980 But I'm going to create it for now and copy it. 11:17.420 --> 11:20.620 Go back to ten and paste it right here. 11:21.780 --> 11:22.500 Hit save. 11:24.020 --> 11:24.900 And that's it. 11:26.020 --> 11:31.900 I don't have to worry about bearer tokens or any of that authentication complexity. 11:32.180 --> 11:35.740 So the community node handles all of that for me. 11:37.100 --> 11:38.320 Let's close this pop up. 11:41.000 --> 11:41.960 And now look at this. 11:42.000 --> 11:50.160 Instead of having to find voice IDs manually like we did with the HTTP request, I can just choose from 11:50.200 --> 11:51.800 a drop down list of voices. 11:53.120 --> 11:55.720 I even have access to my own voice I cloned. 11:56.400 --> 11:58.840 I can see Archer, Archer, and so on. 11:59.040 --> 12:00.880 So all the available voices right here. 12:01.080 --> 12:02.680 Here you can specify the operation. 12:02.680 --> 12:08.320 So text to speech, speech to text, speech to speech and custom API call. 12:09.400 --> 12:10.360 Let me select. 12:13.640 --> 12:15.440 A dummy for now and let's test it. 12:15.440 --> 12:23.000 Let's say something like community nuts are amazing. 12:27.000 --> 12:29.440 And now I run this and see what we get. 12:30.240 --> 12:31.320 So execute step. 12:33.720 --> 12:35.000 Now let's download a file. 12:37.390 --> 12:38.630 And now let's listen to it. 12:40.790 --> 12:42.350 Community nodes are amazing. 12:43.670 --> 12:44.950 That's exactly what we wanted. 12:45.630 --> 12:51.950 Now look at how much simpler that was compared to all the manual setup we had to do with the HTTP request 12:51.990 --> 12:52.430 node. 12:54.430 --> 12:59.990 What's really nice about this community nodes is that they solve one of the biggest pain points people 12:59.990 --> 13:00.430 have. 13:00.750 --> 13:08.870 So authentication with HTTP request method, you have to figure out exactly how each service wants their 13:08.870 --> 13:13.790 API connection to be formatted according to the documentation. 13:15.350 --> 13:21.710 But with this community nodes, you just paste in your API key and the node handles all the technical 13:21.710 --> 13:22.310 details. 13:22.990 --> 13:30.030 Also, with this verified community nodes, you can use other actions as this API endpoints have been 13:30.030 --> 13:33.860 configured for us, so you can see how much time and hassle Hustle. 13:33.900 --> 13:34.620 This saves. 13:35.380 --> 13:41.740 Instead of spending time figuring out API documentation and troubleshooting authentication issues, 13:41.740 --> 13:44.420 you can focus on actually building your workflows. 13:45.100 --> 13:47.540 Now here is something cool I want to point out. 13:48.060 --> 13:52.180 The community nodes are not just limited to regular workflow steps. 13:52.180 --> 13:54.460 You can also use them as a agent. 13:54.500 --> 13:55.700 Tools and triggers. 13:56.500 --> 13:57.980 So let me show you what I mean. 13:58.580 --> 14:06.060 I've got a simple agent setup here, so if I'm working with an agent and I want to add, for example, 14:06.100 --> 14:11.380 search capabilities as a tool, I can install that community node. 14:13.260 --> 14:14.580 So let's search for WP. 14:17.540 --> 14:19.500 As you can see this is the community node. 14:19.500 --> 14:21.860 This is an official node maintained by Tavileh. 14:22.580 --> 14:25.820 You can recognize it thanks to this tick symbol. 14:27.540 --> 14:28.900 So let's install this node. 14:31.340 --> 14:32.600 Package has been installed. 14:32.640 --> 14:35.920 Now let me go to my tablet account and grab my credentials. 14:35.920 --> 14:36.920 So my API key. 14:40.000 --> 14:41.800 Going to create new API keys. 14:44.240 --> 14:45.320 I'll need two notes. 14:45.800 --> 14:46.320 Demo. 14:47.560 --> 14:48.320 Create. 14:50.920 --> 14:51.880 Let's copy it. 14:52.480 --> 14:53.800 Let's go back to editing. 14:55.440 --> 15:06.320 Now when I go to add tools to my agent and I search for tabulae, I can see the tablet tool option right 15:06.320 --> 15:06.680 there. 15:07.560 --> 15:08.680 So let's select it. 15:09.800 --> 15:11.640 And now let's create new credential. 15:13.240 --> 15:17.560 Let's paste the API key and let's save it. 15:18.400 --> 15:19.120 Perfect. 15:20.240 --> 15:21.360 And now it's ready to go. 15:21.560 --> 15:27.880 So this means my agent now has access to a web search functionality without additional configuration. 15:28.600 --> 15:36.030 Previously You would need to go to travel documentation, use HTTP request node and set up the connection 15:36.030 --> 15:36.590 manually. 15:36.830 --> 15:42.390 Now, thanks to this community node, the process of setting up connection is very simple and quick. 15:42.510 --> 15:46.030 You just need to generate API keys and paste it into this field. 15:47.190 --> 15:51.230 Now as for triggers, it depends on what the community node offers. 15:51.750 --> 15:56.550 Some because some have trigger functionality, some don't. 15:56.950 --> 16:00.030 You just need to check when you are browsing available triggers. 16:01.030 --> 16:03.830 So on up event. 16:03.870 --> 16:10.910 And now when I browse triggers, we can see that there are several community nodes. 16:10.950 --> 16:13.030 Community triggers available here. 16:13.590 --> 16:18.870 So you can recognize them based on this small tick symbol next to them. 16:19.310 --> 16:20.830 So you have a scraper. 16:21.350 --> 16:22.430 You have API. 16:22.790 --> 16:28.980 You also have beyond presence brave search browser flow for LinkedIn Chart data. 16:33.460 --> 16:39.020 So the nice thing is that this community packages often include multiple components. 16:39.020 --> 16:44.060 So the main node tools for agents and sometimes triggers too. 16:44.500 --> 16:48.380 So you get a complete integration rather than just one piece. 16:49.460 --> 16:51.220 Now let's look at how this works. 16:51.220 --> 16:52.940 If you are a self-hosting Canadian. 16:53.380 --> 16:56.900 So the process is slightly different but actually just as simple. 16:57.660 --> 17:03.380 So now I'm in my self-hosted instance I set forth on hosting. 17:04.060 --> 17:05.540 So I will go to settings. 17:07.580 --> 17:11.340 At the bottom left corner and click on Community Nodes. 17:13.060 --> 17:20.380 And here instead of having a curated list like on the cloud version where you can browse and search 17:20.380 --> 17:26.810 for different community nodes, I can install community nodes directly by typing in the package name. 17:27.010 --> 17:28.170 So click on install. 17:29.170 --> 17:35.090 And here you can either type the name if you know it, or click browse to see all the all available 17:35.130 --> 17:36.810 and community node packages. 17:37.690 --> 17:38.810 So let's click browse. 17:39.610 --> 17:40.410 Let's have a look. 17:41.250 --> 17:44.610 As you can see we have over thousand packages found. 17:44.650 --> 17:51.210 You can browse them by default by most downloaded this week this month recently published. 17:54.330 --> 18:00.850 There is actually a really helpful GitHub repo that lists the top 100 community nodes organized by category. 18:01.610 --> 18:08.450 So things like communication, messaging nodes, document content generation nodes, browser automation 18:08.490 --> 18:15.690 and web scraping nodes, data processing, validation and utilities nodes, API cloud integrations and 18:15.690 --> 18:16.490 voice nodes. 18:17.010 --> 18:18.930 File PDF manipulation nodes. 18:19.290 --> 18:22.570 I will put a link to that in the resources section of this lesson. 18:23.650 --> 18:30.310 For example, in the communication and messaging category, we can see that the top spot is held by 18:31.070 --> 18:35.350 evolution API, which is an alternative to the official WhatsApp business API. 18:36.110 --> 18:42.350 And it's really impressive because it has almost 2 million monthly downloads and gets updated regularly. 18:42.990 --> 18:47.150 Here you can see the description so provides a channel hub focused on WhatsApp. 18:47.150 --> 18:52.150 You can see the author version and also the link to the documentation. 18:52.550 --> 18:58.350 And when I click on that, the documentation is in Portuguese, but I'm actually planning to record 18:58.910 --> 19:05.750 a separate tutorial on this one because I've had quite a few students ask me about WhatsApp automation, 19:05.790 --> 19:06.910 this evolution API. 19:07.150 --> 19:12.190 But this gives you an idea of how popular and useful these community nodes can be. 19:12.230 --> 19:16.790 When you have millions of downloads, you know people are finding great value in these tools. 19:17.230 --> 19:24.580 Now, since we used 11 labs in our earlier example, let me install the same package in the self-hosted 19:24.580 --> 19:25.300 environment. 19:25.300 --> 19:27.860 So let's search for 11 laps. 19:30.460 --> 19:37.140 I can click on the package name, which takes me to the npm page for this community node. 19:39.460 --> 19:41.500 From here it's really straightforward. 19:42.780 --> 19:44.300 Just copy the package name. 19:45.100 --> 19:46.100 Go back to n810. 19:48.860 --> 19:56.060 So settings community nodes install paste the npm package name here. 19:56.740 --> 20:02.860 Hit the check mark to confirm that I understand the risk of installing unverified code from a public 20:02.860 --> 20:05.380 sources install. 20:06.940 --> 20:12.540 Now I have the 11 labs node installed if I create a new workflow. 20:15.660 --> 20:16.860 Search for 11 apps. 20:19.620 --> 20:22.770 You will notice that I actually get two options. 20:22.770 --> 20:29.850 So this one is verified by an Asian team and it's maintained by 11 labs themselves. 20:30.450 --> 20:37.770 And this would be the same one we saw in the cloud version, this one with this little block icon. 20:38.250 --> 20:39.930 This is a node from our community. 20:39.930 --> 20:44.410 It's a part of the ten nodes uh, 11 labs package. 20:44.410 --> 20:48.810 So it's a community node that I installed myself and both work the same way. 20:49.170 --> 20:54.130 I can use either one for text to speech or in the other 11 labs functionality. 20:54.930 --> 20:58.570 Now, if you are running locally, the process is a bit different. 20:58.930 --> 21:04.890 You can just go to settings and install community nodes by typing, by typing, by typing in the name 21:04.890 --> 21:07.450 like we did with the other methods. 21:07.610 --> 21:14.250 That's because you need to install the actual node package somewhere that your local ten can access. 21:14.610 --> 21:15.850 So according to. 21:17.590 --> 21:19.190 An intense documentation. 21:19.190 --> 21:25.950 If you want to manually install a community node using npm, you will need to access your Docker shell. 21:26.510 --> 21:35.710 So basically you get into your environment, create a directory for nodes if it doesn't already exist, 21:35.710 --> 21:41.350 and then run the npm install command for the node we have been using. 21:41.390 --> 21:46.070 As an example, you would run the npm install command for that package. 21:46.310 --> 21:49.670 So each node will have its npm command listed. 21:49.670 --> 21:56.990 So if you are self-hosting locally, refer to GitHub repos and once you have installed it and restarted, 21:57.390 --> 22:00.710 the node should appear when you search for it in your workflow. 22:01.350 --> 22:01.670 All right. 22:01.670 --> 22:02.030 Great. 22:02.070 --> 22:07.190 That's how you set up community nodes across all three hosting options. 22:07.190 --> 22:10.950 So cloud self-hosted online and locally. 22:11.270 --> 22:15.390 This is going to save you a lot of time and make your workflows much cleaner. 22:15.750 --> 22:17.470 Thanks for watching and see you next time.