hello and welcome to video number six of the advanced course for nadn. In this video, we will be building a complete workflow from scratch, so let's dive right in. The objective of the workflow that we're going to be building today is to use the form trigger to take a list of company URLs as an input. Then we will be enriching these URLs using the People Data Lab API, while making sure to manage all errors. Then we will append all of this data of the companies that are in Europe to a Google Sheets before summarizing the data and sending a Slack message. So, the first step here is going to be to add our form trigger. This will allow us to have an interface that we can share with people where they'll be able to submit this list of URLs. So here we have submit URL form. We'll leave the description blank for now, and we'll just have one field called URL. Now I can test this step, and I will see this form pop up, and here I can have a list of URLs. Here we have Google.

naden Facebook pull and spendesk. When I submit the form, I can go back to the workflow, and I will have the data here as one item. The first thing we're going to do here is pin this data. We don't want to have to go back into the form and submit it again and again every time. We can just pin the data so we have workable items to start using. The next step is we want to split out these URLs so that we can go over them one by one. From here, we can use the edit Fields node to separate this string of URLs into an array or a list that we can then split the one item into multiple items so that we can loop over field by field. So here, we're just going to name this URL list. The type is going to be an array, and for the value, we want the list of URLs, except this time we're going to split it by the comma value. So here, when we execute this, we're going to have the list of

URLs directly here. We don't need anything else, so I'm not going to include the other input fields. Now, I can use the split-out node to take this URL list and turn it into different items, and we can move over to the enrichment part of the workflow. So, what we're going to do here is iterate over each URL one by one. So, we can use the loop over items node here. I want the batch size to be of one. I want to go through the URLs one by one. So, if I execute here, you see from the five items we go down to one. After looping over all of the items, I can add an HTTP node here, and we can take a look at the documentation for People Data Labs here. We're going to use the SQL query, so it's a GET onto this URL. So, I can copy over the URL. Then, I see here we have a header for authentication. So, I've already set this up. I have generic credential type. It's going to be a header or as described in

the documentation, and I already have this set up with my API key. Here, we have the body, so we have two different fields that we need: the size, so the number of results that we want to get as a result, and then the SQL query itself. So, we can send a body size of one and SQL, and I can just copy over this query. Now, we should be ready to execute, but we actually need to replace this Google.com with the expression for the current URL that we are working on, just to make sure that we're not always looking up Google, but we're looking up the right company every time. So, here, I can replace all of this website [Music] equals dollar json. URL list. And here, actually, we need to separate this out because this is going to be part of the string and the final apostrophes. So, here, when I execute this, it should be perfect. So, we have a status 200, and we have the information about Google that was returned. The first thing we would like to do here is handle any potential error.

so how do we do this? We're going to use an if node, and we can check if the status field here, which is going to be a number, is equal to 200. Sorry, it's not equal to 200. This means that we don't have a positive response, and we need to handle the error. So, if the answer is not 200, then we can stop and throw an error on PDL enrichment. If we don't have an error, we can just loop back over, and that way, for all five items, we're going to do this enrichment. So, starting again from the form trigger, we can execute all of the nodes, and one by one, these are all going to be enriched. From here, we can set an edit field, and just maybe make the information a little bit easier to access. Here, we have a very deep JSON, so what we can do is we can pull the primary information up to the top level. So, what we want is to find all of the companies that are in Europe. So, what

we're going to do is add a few fields here. The first thing here, let's execute the full work. So here, we can just execute so that we have all of the data and we can keep building the workflow. What we'd like to do here is take all of the data we need and move it up top level. So, we're only going to include specific fields, and the fields that are going to be useful are the name, the number of employees, which is going to be a number employee count. Then, we need the country, which is going to be somewhere in location country, United States. We need the geography or the continent, so we know if it's Europe. And finally, we're going to add the amount of funding because this might be useful. And if we look in here, total funding raised, perfect. So, when we execute this, we now have only the main information that we need for every single one of these companies. Now, we're going to filter this with an if node, and here, we're going to only keep

companies that are in Europe, so I want the continent, and here where string is equal to Europe, and here we're only going to have three companies that are in Europe. I have a Google sheet here with name, employees, country, and funding, and we're going to add a Google sheet node. We're going to append rows into the company and data, and here we we're just going to map the fields. So we have name, employees, country, and funding. When we execute this, it's going to add all of the names to that Google sheet. The final step in our workflow is going to be sending a summary message in slack, um, so that we know how many companies we added, um, to the Google sheet. So we're going to use the summarize node here, and we're simply going to be counting the number of names, which is going to give us here the length. We could have done this with um, set Fields node that we uh, using an expression for example, but here we have a built-in node that we can just use. Finally, let's add the slack node and

We're going to send a message here. I already have my authentication set up. It is simply an OAuth, so I can just log in. It'll open a window, and I can log into my Slack account. We're going to be sending a message to a user, in this case, myself. And instead of using a simple text message, we're going to use blocks. Blocks allow you to have a little bit more control over the Slack messages, for example, including buttons. And what we're going to do here is add a button that links back to the sheet so that it's very easy to access. In the Slack documentation, we have a few templates that we can use to help build blocks. Instead of starting from scratch, we're going to use this one and modify it for our use case. So, we're going to start with a maxim here. We're going to confirm what the workflow just did. Your NN workflow just added X companies to your Google sheet. And we will replace X in the expression directly in Anyen. We don't need these puted.

points and here we can just add here is a link to access your Google sheet and here using the button I can uh change the text Google Sheets and I can just copy over the value directly here so now this I can use by copying all of this directly in naden and I can paste the block Builder directly here so obviously I now need to change the x that I mentioned up here and I can simply do this with an expression here using oops json. counter name and when I execute this I can add a little notification message when I test the step I'm going to oops when I test the step it's going to send the message with the direct number of um companies that were added in the sheet mentioned in the message so now we have the full workflow uh what we can do is do a final test run it A to Z and make sure that everything is working as expected so I'm going to get the list of URLs again refresh the page test the workflow oops okay now refresh the

page here. I'm going to unpin the data so that we can start afresh. And when I click test step and I put in my list of companies, submit form, we should see everything go through. So here we get all the URLs, split them out, start looping over, get enriched five times. All of them were 200s. We go back and we get our main data, top level, add them to the Google Sheets, summarize the number of items that were added to the sheet, and then send our final Slack notification confirming that the work was successful and giving a recap. Thanks for listening to video number six of the advanced course. In the next video, we'll be covering how to handle files in your Nend workflows.

n8n Advanced Course (6/8) - Build a full example

n8n Advanced Course (6/8) - Build a full example