Welcome back.
Today I'm going to walk you through how to work with community nodes.
Now let me quickly explain what a community node actually is.
So it's basically a pre-built connector that someone from the community has created to solve a specific
problem or add functionality.
So to connect a platform, app or service that N810 doesn't have it.
So the native node or direct integration.
So far you would need to use the HTTP request node.
So instead of you having to mess around with APIs, documentation, finding parameters, JSON formats,
they have already done all that work for you.
So they build these nodes to handle all the backend stuff.
And the only thing you need to do is provide your API keys.
That's going to save you a lot of time because instead of figuring out how to set up API connections.
So all these credentials parameters and so on, we can use community Notes.
This applies whether you are using a cloud or you are hosting an item.
So on the 27th of May, the N810 team announced that this community nodes are now available directly
in their cloud platform.
So this is actually a big deal because up until now, if you wanted to use this, you had to self-host
N810 and set up everything manually and scroll down.
You can see that they're starting with 25 of the most popular community nodes and partner integrations.
So they are planning to gradually expand this library and adding more verified nodes over time.
So the goal is to make it much easier to connect to pretty much any service you need without setting
up and configuring sometimes very complex HTTP requests.
They are investing time into it because they discovered that these community nodes have been really
successful and people are using them to solve real problems, and it makes sense to make them more accessible
to everyone.
Now, in this article, you can read that the ones that are going to be available include things like
tablet for search, server API, even 11 labs for AI voice beyond presence.
To create realistic avatar video agents, you will also find nodes supported by chat data.
Click send.
It could run, scrape less and so on.
So all these nodes will be available to install directly from the editor.
Now there is one important thing you need to check.
First you have to be running version 1.94.
So I will go to my n810 and click on admin panel.
And here you can see that I'm currently running version 1.10.1.
In case you are running the older version.
You will see a notification that the update is available.
So just simply click on it and update your instance.
Now here is what we need to do next.
In the admin panel we need to click on settings.
Scroll down.
And you can see verified community nodes.
Turn that on.
And then click on Save Changes.
So this is going to restart your workspace.
So make sure you have saved any workflows you are working on.
Now when I go back to my dashboard you will see it's being back up and making the changes.
So once it turns green, we'll be able to click open and get back into our instance.
Yes.
Perfect.
So let's open the instance now that we are back in.
If we go to settings again.
You will notice that there is a new option community nodes.
This is where you can install community nodes that have been verified by Natan directly from this panel.
This is much easier than the old way where you had to install things manually if you are self-hosting.
Now let's create a new workflow and see how this works.
Let's say I want to use 11 labs for text to speech.
Normally, without a pre-built community node for 11 labs, I would need to use the HTTP request node.
So let's add HTTP request node.
I'm going to show you what I mean, and I would have to go through the API documentation, figure out
all the parameters, set up the authentication.
So it's quite a process.
Let's do it now to see how tedious it can be.
And then we'll use the 11 labs community node to show you how simple it is and how much time you can
save.
So for the method we need to use post and I need to go to 11 labs API documentation.
Here we need to find the API reference section.
So text to speech endpoints.
Basically what we need to do we need to copy this URL.
Go back to n810 and paste it into this field.
Then I need to set up a headers.
So I need to send headers.
So now I need to find the header name.
So I need to go back to API documentation.
As you can see the headers are required.
So I need to copy this.
Is.
Go back to 2010 and paste it right here.
And for the value I need to get my API keys.
So I need to go into my 11 labs account to go to at the at the bottom left corner.
I need to go to API keys.
And here I can create API keys.
So let's create new one.
Community notes.
Demo.
Confirm.
Create.
Create key.
Now copy API key.
Go back to ten and paste it into the value field.
Then I need to toggle Send Body and go to API docs again to add the required fields.
I need to scroll down and find request.
As you can see, the text string is required, so let's copy it.
Let's go back to N810.
We're going to leave the body content type as JSON.
Paste text into the name field, and in the value field I will put something like either.
Community nodes.
Are awesome.
And this is how the process looks like.
Or alternatively I can use the curl command from the API documentation.
So copy this curl command.
And instead of adding each field manually.
I can do this this way.
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
way.
So what can I do?
I can.
Uh, import curl.
Paste the curl command here and then click import.
But I still need to configure it.
So I need to add my credentials and so on.
Also to use other actions like creating a voice clone or transcribing audio I would need to use different
API endpoints.
So that means I would need to add another HTTP request node going through the documentation again,
and configuring each node to set up the connection for different actions.
Also, I would need to add the voice ID to this URL.
I need to go back to my 11 labs account.
Go to text to speech section.
Go to voices.
Copy the voice ID of the voice of our choice.
Go back to ne10 and include the voice ID in this URL.
So replace everything after slash and paste the voice ID here.
All of this requires a lot of manual setup.
But now with community nodes, the process of setting up connections with services like for example,
11 labs is much, much easier.
Look how much simpler this becomes.
So once in the admin panel.
You turn on the verified community nodes.
So in the settings.
You turn on this option you will be able to install community build node packages very easily and quickly.
So let's go back to our dashboard.
And now I can simply search for it overlaps.
And we have this clean node with the 11 labs logo.
And all I need to do is add my credential.
So you can see this um tick symbol.
So this is an official node maintained by Level Labs.
So this that means that this is community node.
So let's select it.
Let's use this action.
So convert text to speech.
And all I need to do is add my credential.
So create new credential.
Go to your Level Apps account.
Go to settings API keys.
Copy your API key.
Create.
Create key.
Let's toggle off this restriction to give it access to all the actions.
You need to remember that an unrestricted API key can be significantly more harmful if leaked.
Please consider restricting the API key to specific actions.
But I'm going to create it for now and copy it.
Go back to ten and paste it right here.
Hit save.
And that's it.
I don't have to worry about bearer tokens or any of that authentication complexity.
So the community node handles all of that for me.
Let's close this pop up.
And now look at this.
Instead of having to find voice IDs manually like we did with the HTTP request, I can just choose from
a drop down list of voices.
I even have access to my own voice I cloned.
I can see Archer, Archer, and so on.
So all the available voices right here.
Here you can specify the operation.
So text to speech, speech to text, speech to speech and custom API call.
Let me select.
A dummy for now and let's test it.
Let's say something like community nuts are amazing.
And now I run this and see what we get.
So execute step.
Now let's download a file.
And now let's listen to it.
Community nodes are amazing.
That's exactly what we wanted.
Now look at how much simpler that was compared to all the manual setup we had to do with the HTTP request
node.
What's really nice about this community nodes is that they solve one of the biggest pain points people
have.
So authentication with HTTP request method, you have to figure out exactly how each service wants their
API connection to be formatted according to the documentation.
But with this community nodes, you just paste in your API key and the node handles all the technical
details.
Also, with this verified community nodes, you can use other actions as this API endpoints have been
configured for us, so you can see how much time and hassle Hustle.
This saves.
Instead of spending time figuring out API documentation and troubleshooting authentication issues,
you can focus on actually building your workflows.
Now here is something cool I want to point out.
The community nodes are not just limited to regular workflow steps.
You can also use them as a agent.
Tools and triggers.
So let me show you what I mean.
I've got a simple agent setup here, so if I'm working with an agent and I want to add, for example,
search capabilities as a tool, I can install that community node.
So let's search for WP.
As you can see this is the community node.
This is an official node maintained by Tavileh.
You can recognize it thanks to this tick symbol.
So let's install this node.
Package has been installed.
Now let me go to my tablet account and grab my credentials.
So my API key.
Going to create new API keys.
I'll need two notes.
Demo.
Create.
Let's copy it.
Let's go back to editing.
Now when I go to add tools to my agent and I search for tabulae, I can see the tablet tool option right
there.
So let's select it.
And now let's create new credential.
Let's paste the API key and let's save it.
Perfect.
And now it's ready to go.
So this means my agent now has access to a web search functionality without additional configuration.
Previously You would need to go to travel documentation, use HTTP request node and set up the connection
manually.
Now, thanks to this community node, the process of setting up connection is very simple and quick.
You just need to generate API keys and paste it into this field.
Now as for triggers, it depends on what the community node offers.
Some because some have trigger functionality, some don't.
You just need to check when you are browsing available triggers.
So on up event.
And now when I browse triggers, we can see that there are several community nodes.
Community triggers available here.
So you can recognize them based on this small tick symbol next to them.
So you have a scraper.
You have API.
You also have beyond presence brave search browser flow for LinkedIn Chart data.
So the nice thing is that this community packages often include multiple components.
So the main node tools for agents and sometimes triggers too.
So you get a complete integration rather than just one piece.
Now let's look at how this works.
If you are a self-hosting Canadian.
So the process is slightly different but actually just as simple.
So now I'm in my self-hosted instance I set forth on hosting.
So I will go to settings.
At the bottom left corner and click on Community Nodes.
And here instead of having a curated list like on the cloud version where you can browse and search
for different community nodes, I can install community nodes directly by typing in the package name.
So click on install.
And here you can either type the name if you know it, or click browse to see all the all available
and community node packages.
So let's click browse.
Let's have a look.
As you can see we have over thousand packages found.
You can browse them by default by most downloaded this week this month recently published.
There is actually a really helpful GitHub repo that lists the top 100 community nodes organized by category.
So things like communication, messaging nodes, document content generation nodes, browser automation
and web scraping nodes, data processing, validation and utilities nodes, API cloud integrations and
voice nodes.
File PDF manipulation nodes.
I will put a link to that in the resources section of this lesson.
For example, in the communication and messaging category, we can see that the top spot is held by
evolution API, which is an alternative to the official WhatsApp business API.
And it's really impressive because it has almost 2 million monthly downloads and gets updated regularly.
Here you can see the description so provides a channel hub focused on WhatsApp.
You can see the author version and also the link to the documentation.
And when I click on that, the documentation is in Portuguese, but I'm actually planning to record
a separate tutorial on this one because I've had quite a few students ask me about WhatsApp automation,
this evolution API.
But this gives you an idea of how popular and useful these community nodes can be.
When you have millions of downloads, you know people are finding great value in these tools.
Now, since we used 11 labs in our earlier example, let me install the same package in the self-hosted
environment.
So let's search for 11 laps.
I can click on the package name, which takes me to the npm page for this community node.
From here it's really straightforward.
Just copy the package name.
Go back to n810.
So settings community nodes install paste the npm package name here.
Hit the check mark to confirm that I understand the risk of installing unverified code from a public
sources install.
Now I have the 11 labs node installed if I create a new workflow.
Search for 11 apps.
You will notice that I actually get two options.
So this one is verified by an Asian team and it's maintained by 11 labs themselves.
And this would be the same one we saw in the cloud version, this one with this little block icon.
This is a node from our community.
It's a part of the ten nodes uh, 11 labs package.
So it's a community node that I installed myself and both work the same way.
I can use either one for text to speech or in the other 11 labs functionality.
Now, if you are running locally, the process is a bit different.
You can just go to settings and install community nodes by typing, by typing, by typing in the name
like we did with the other methods.
That's because you need to install the actual node package somewhere that your local ten can access.
So according to.
An intense documentation.
If you want to manually install a community node using npm, you will need to access your Docker shell.
So basically you get into your environment, create a directory for nodes if it doesn't already exist,
and then run the npm install command for the node we have been using.
As an example, you would run the npm install command for that package.
So each node will have its npm command listed.
So if you are self-hosting locally, refer to GitHub repos and once you have installed it and restarted,
the node should appear when you search for it in your workflow.
All right.
Great.
That's how you set up community nodes across all three hosting options.
So cloud self-hosted online and locally.
This is going to save you a lot of time and make your workflows much cleaner.
Thanks for watching and see you next time.