NoCode Architects Toolkit Overview

Are you tired of wasting thousands of dollars on API subscriptions to support all of your automations? What if there was a free alternative? In this video, I'm going to show you how you can eliminate the costly monthly subscriptions for ChatGPT Whisper, Creatomate, JSON to video, cloud convert, and even tools like ZeroCodeKit that allow you to run Python code. And we'll replace it with one tool, the NoCode Architects Toolkit. Subscription services like OpenAI, Creatomate, and JSON to video run servers on the internet with some code that allows you to access their resources through an API for a monthly fee. And it's very easy for these subscription services to add up. And the NoCode Architects Toolkit is meant to replace all of these costly services. And how we help you do that is that we wrote some of our own code. that you can easily deploy into your own server and access through an api inside of your own automations at almost no cost to you you can even use the toolkit to build more efficient automations here's a single module on the no code architect running some python code i'll show you how this works but it eliminates hundreds of operations and replaces it with a single operation And it scales well too, even if this automation were to process more data, we would only burn one operation, whereas otherwise this module would continue to eat up more and more operations. So today I'll go over all the features of the NoCode Architects Toolkit by showing you examples of how we can create video, transcribe it, how we can transform media into different types, manipulate and combine videos, caption videos. I'll show you how to use the custom GPT I built to help you use it. And of course, I'll show you how to install it on the Google Cloud platform so that you can start saving money today. Now, after you've actually installed your NCA toolkit server on the Google Cloud, and I'll show you how to do that later in the video, you can access that API in your automations through the no code architects toolkit make module. We're continuing to build this out and to add more features, but you can also access your no code architects toolkit API through the common HTTP module that you find in make. And again, after I help you install the toolkit, later in the video, I'll show you how to set this up. But I'm actually gonna demo some of the features today in a tool called Postman. This is a great tool for testing API calls. It really does the same thing as these two modules. It just allows you to test quickly. And you can also save a bunch of different API calls for testing and demonstration like I'm doing today. I'll also give you access to the sample of API calls so that after you install Postman, you'll have access to all of these for testing. It's great when you can just cycle through here and just see how all of these things are built. There are sample files here. You can just hit send and it'll work and then you can explore and modify as you see fit. But let's just go ahead and start at the top and we'll move down and I'll show you a bunch of examples on what this toolkit is capable of. So at the top here we have the caption feature. You essentially just pass it a video. I'll copy this and put it in the browser so you can see. This is just a quick short video of me on the School Games podcast and then there's just a bunch of different settings here that control the color, the font size, how many words per line. bold, italic, underline, strike out, the outline width, sometimes called the stroke. And then I'm adding in a shadow on the font as well. The captions API is quite powerful. You can control the positioning. You can control exactly the X and the Y of where the caption should be. Let's go ahead and test this out and see what it looks like. All right, so it looks like that process completed. So let's go ahead and take a look at the file. So here is the captions. This is just the classic style. So let's go back and do something a little more fancy. We'll go with highlight. We'll go ahead and run that again. Looks like it's done. Let's take a look at this new file. So now you can see we've got an active color here. Let's go back and we'll choose a font style. I like the bold font. I'm going to go here also and move it to three words per line. It's not font style, it's font family. Send that again. I realize there I've got a dash instead of an underscore. That should fix it. Alright, so now the next video is done. Let's go ahead and test it out. And of course we can come here and control the x and y. We'll go with 400 and y 400. So on our video here, We can control those captions to be at some x and y coordinate. We'll go ahead and run this as well and we can take a look at that new file. So now you can see we can actually adjust and put the captions at a specific x and y coordinates on the video. There's also some built-in positioning so you can just type position. and something like bottom center and we'll give that a test. So now it's at the bottom center and there's also a cool feature that allows you to find and replace words in the video. So if I type replace here I can actually send it an array of objects to find we'll just go with you and we'll replace it. with these characters here. But this is handy for when the transcription service commonly gets certain types of words wrong. You can put this in here and automatically replace them. Sometimes you'll see that when you're talking about URLs or emails. It really just depends, but this allows you to address it. So we'll go ahead and test this as well. So now let's take a look at this new video here. You can see right there the word you was replaced here by that string that we added right here. So this is a really powerful one. I encourage you to explore the captions api and see what it can do then moving along we also have a function here that allows you to concatenate two videos together this is a simple one that comes up a lot and so this becomes a very handy tool to have here you can see i'm just linking to two videos and that's that nine second video here so once we run this and we check out the url you can see here we have a new video that's 18 seconds long it's simply the same video that's concatenated and repeated i use this end point a lot in my faceless video generator and now next up we have the ffmpeg comp pose endpoint this is a feature that was created really after i had developed several other end points like this one here for concatenating videos it just turned out that there were so many different things that we needed to do with audio and video that it'd be hard to create separate functions for everything that we needed to do and what a lot of these endpoints actually did like concatenate is that they really just worked with a tool called ffmpeg and we don't have to go into a lot of detail here But a lot of the functions that I was developing inside the toolkit were actually using that FFmpeg tool. And so what I found was that instead of having to try to create new API calls for everything, although it's nice to have some things that are used a lot like concatenate, it would actually be better to develop a tool that was more flexible where you could pass in different types of media. In this case here, we have a FFmpeg compose function that is actually concatenating two videos. just like the endpoint that I showed you here, but it's showing you how to combine these videos using FFmpeg Compose instead of using the dedicated endpoint. So this is a good example to see what's happening behind the scenes in this concatenate API call. Here's another example where we actually pull a clip from another video. So let's take a look at this source video here that we have. Here's a two minute YouTube video that's horizontal style. Again, I just have a bunch of these videos up on the cloud for testing. Once you download Postman and get access to this workspace, you'll have all of these examples that you can pull from, including those videos on the cloud. And then you can just replace it with your own videos. But if we run this example here, it's going to give us a five second clip starting at second 10 all the way to 15. So let's give that a try. Let's go ahead and test this endpoint. So we can scroll down here. We can see that the file URL is here. Go ahead and open that up. And notice now we have a five second video that was clipped from second 10 to 15. And so next up, this example here will actually crop a video out of another. So we have a horizontal video, the one that we were just using before. It'll actually crop out a vertical video. And then because the height of that vertical video would just be 1080 pixels, it'll actually scale it to the proper size for. vertical videos on social media which is 19 20 and you'll see these specific values inside the api call so you can start to see how everything works and after some time and with the help of the gpt that we created specifically for this toolkit api it becomes quite easy to build these json's for each of these different endpoints So again, we're using that same horizontal YouTube video. Let's go ahead and give this one a try. It looks like it finished, so let's go take a quick look. So now we have the vertical video that was pulled from the horizontal video using the coordinates that we added here and then scaling it up to the proper size. Next up, we have another example here, which will grab a still frame from a video. So here again, I'm using that vertical video clip that was taken from the School Games podcast. I'm gonna grab a still frame at the first second here. Let's go ahead and run it. so this is a good way to get thumbnails from your videos let's go ahead and open that up and here we go this one's just an image and in this next example we're going to overlay a logo on top of a video here i'm using that youtube video again but in this case i have a logo i'm going to open that up in the browser here just so you can see so we have the no code architects toolkit logo and we'll go ahead and run this example and while that's running we can see here that we are scaling that logo to the proper size and then we are overlaying that on top of the video at a specific coordinate and you might also notice that in this particular case the api is giving us some additional information and i'll talk about that in just a moment but that's because we are adding in this metadata object here which allows us to get access to some additional data when we run these commands to ffmpeg compose so here's that youtube video and now you can see we've embedded that logo in the bottom left corner In this next example, we're going to build a tweet pic. So I've got two images here. I'm going to grab this one just so we can see what it looks like. This is a still image pulled from the School Games podcast. And then this here is a... Image as well. This is a tweet pic image that we can embed on that image to create a new piece of content Let's go ahead and run this example. Here's the output. Let's take a look So here's the school games image with the tweet pic overlay done for us automatically We can also do a tweet video in this case I'm going to use that school games podcast clip with a tweet pic So instead of doing a tweet pic on top of a image, we're gonna do it on top of a video Let's go ahead and run this example. So now we've got that video with that tweet pic that is overlaid on top of the video then in this next example this is going to build a reaction style video you might have seen these where someone is watching another video they're sitting here and down here in the corner there's another video that they're watching and then after it's done they react to it so let's take a look at the source material for that we have a reaction video so this is me reacting to the video and then at the end i'm actually saying something about the video itself and then this is the video that i'm actually watching and reacting to let's take a look at that and i'm actually reacting to my own school games podcast clip just for fun so let's go ahead and run this example and again i made these examples so you can start to look and see how these things are designed and of course you can work with the gpt that we built for the ncaa toolkit specifically here you can see the first thing that we're doing is we're making sure that the video that i'm watching is scaled up to the proper size i'm scaling that video down into position we're also drawing a red box around the video i'm reacting to and there's a few other settings here as well but let's go ahead and take a look at the output video and so here you can see there's me reacting to that school games podcast clip and we also generated that red box around it so if we were to let that play you would just see me reacting to my own video and then once this video was over it would disappear and then you would see my reaction and then we have another example here where we are overlaying some audio on top of a video and mixing them together and then within this filter itself you can control the volume of either of those two tracks i'm going to go ahead and replace this url with the school games podcast clip this is actually a mp3 we can take a quick listen i'm actually going to grab a different mp3 for this example here drop that in instead all right so now let's go mix these two together you might not be able to tell but that operation happened really quickly and that's also something to note that each of these different commands that we're running here are going to take a different amount of time depending on the amount of processing that has to take place so let's take a look at the clip mixed with the audio you got to keep people moving forward yeah there's all these gimmicks in the school communities around like so by no means is that all that you are capable of doing with ffmpeg compose and ffmpeg in general the tool that powers ffmpeg compose but i wanted to give a wide range of different examples so that you could see the power and maybe start to develop your own ideas of what you might want to do because this tool is quite flexible you can do all sorts of different things so try to be creative and then use the ncaa toolkit api gpt which can actually help you generate these json's just by working with it and telling it what you want to do so let's continue on with the capabilities of the toolkit here i'm in the media folder and we are going to show you how to transform media into an mp3 so this is a simple one here i'm just simply passing a vertical clip from the school games podcast and i'm asking back for an mp3 at a specific bitrate let's go ahead and run this example we can see that was quickly generated now we have an mp3 next up we have the completely redesigned transcribe module you just pass in a media url either audio or video you give it the task you can either transcribe or translate and then you just simply tell the api whether you want the text include text is going to bring back the actual transcription include SRT is going to bring back the SRT file for captioning videos. You can also include segments. I'll show you what that is. It gives you data related to the transcription and various timestamps. You can also control whether the API gives you the response directly in the response, or it can also upload the text in the SRT file into a file and give you the file instead. You can turn on word timestamps, which gives you the timestamp for every single word in that transcription. And then you can also set the language. so let's go ahead and run this as is so here you can see the result let me move this up a bit first here you can see the segments that's what we included right here there's just a lot of data here that you can use if you need that level of detail in whatever you're doing in some cases you'll find that this is just not needed and it's overkill and you can turn it off if i scroll to the bottom you can see we have that srt and that is a file that you can use when you are creating captions on videos and you can also see the text here as well which is just the straight transcription and so depending on what you need you can turn these on or off text srt or segments and then like i mentioned you can control whether it gives you the response back directly in the json response or we can adjust this to cloud in this case it's going to take all of this data here it's going to upload it to a file and give us the file instead Let's check that out. So here you can see we got the response, but instead we're getting the segments SRT and text as a file. We can go ahead and open that up. So here you can see we have that same data just in a remote file. And whether you would choose direct or cloud in your automation really just depends on what your automation is doing and what is best in that particular situation. Then we have two more endpoints here, authenticate and test. Authenticate is just a simple function that allows you to make sure that your password and your authentication and your... toolkit is working properly from an authorization point of view then there's a test endpoint which is a simple endpoint that just allows you to test to make sure your toolkit is working properly here you can see we have a success and if you open this up you're going to see the contents of that file are you have successfully installed the ncaa toolkit api great job and then next up we have another endpoint here that takes an image and transforms it into a video here i have an image that was generated in mid journey here if i run this example it's going to take that image and add a slight ken burns zoom style effect to that video you can control the length of the video the frame rate and also the zoom speed let's take a look at the output and so now you can see we have a video that does a slight zoom on that image that we provided and then finally here i want to show you the endpoint that allows you to execute python code it's all encoded here so it's a bit hard to read but i wanted to create an example to show you how you can use that endpoint here i'm using the http module in make to call the run python endpoint and it's just a simple example here where we have a bunch of youtube titles here i'll expand this so we can see it's a bit hard to see here but all of these titles are all lowercase but what if we were in a situation where we had to uppercase the first letter of each word in the title well this is how you would do that and make we're parsing that json so we're getting all of the different titles in separate bundles that we can loop through so here you can see all of the titles and all of the characters are in lowercase and then in this module here We are simply using this function start case, which will uppercase each of the first letters of each word. And so you can see here we had more than 100 titles. So we had to run this over 100 times. And here are all of those various operations. And you can imagine if there were more titles, it would get even worse. And then we have an aggregator here that allows us to bring all the data together. So here we can see how make helped us uppercase the first letter of each word. But now using the no code architects toolkit, using the Python code, I can open this up. There's a small bit of code here and we're passing it in those titles. And in one operation, we do all of the work and we can see the response here from the toolkit. Here's all of the titles and we can open one up and we can see that we have uppercased the first letter of each word. So I'm gonna jump back to Postman and I've got all that code and all of those titles here. And so you can also just test this endpoint as well. Whenever you're running code, those run very quickly. And so here you can see that we got the response and we've got all of those titles back all with that uppercase on the first letter of each word. So there's quite a few examples of what you can do with the no-code architects toolkit. There's a whole lot more that you can do with the toolkit. But first, if you're enjoying this video, make sure to like and subscribe to the channel. Tells me what type of content you want more of. Now, before I show you how to install the toolkit so that you can use it on your own, I wanna point out And I've mentioned this before that there is a GPT called the NCA Toolkit API GPT that you can use to help you use the toolkit. I'm improving this all the time and it's a great resource just to learn about the toolkit, the different endpoints. You can ask it questions. It'll tell you what it can do. You can even ask specific questions like, help me use the version one media transcribe endpoint. and then it's going to give you an overview and give you some examples on how to use it you can see here it'll give you an overview steps on how you can actually use the endpoint the different options and parameters you can use it'll give you sample json payloads that you can copy and paste into postman just like this or inside your make automations if you're using the http module and you can use the gpt to help you build ffmpeg compose json's give me the ff mpeg compose json payload for combining two videos into one so it'll give you that entire payload you can copy the code and modify the urls and then it'll actually break down and give you an explanation of everything that is going on in that json now one thing to note is that sometimes it will make a mistake i'm adding more and more content to better train the gpt But if you do run into errors, you can always just take that error, cut and paste it directly into the GPT itself, let it know you're running into a problem, and then it will go ahead and help you actually fix it. And then over time, I expect the GPT to make fewer and fewer mistakes. And if you want more dedicated support, make sure to jump into the NoCode Architects community. I'll provide a link to the NCA Toolkit API GPT in the description below. All right, so now I'm going to go ahead and show you how to install the NCA Toolkit from scratch on the Google Cloud Platform. Now, a couple of things to keep in mind. If you are new to the Google Cloud, I think you can get a $300 credit. You might go to Google and type Google Cloud 300. Then you can see that sponsored link and click through to get your free trial. But the other thing I want to point out is that I'm installing this toolkit into a Google Workspace account under my SGPLabs.com domain. And you can control which account you're in with the Google user selection in the upper right hand corner. Now, I prefer installing it into a Google Workspace account myself because I'm a business and just in the long run, this makes a lot more sense. But I do want to point out that when you install it into a Google Workspace account, there are some additional settings that you might need to configure as you go through this install process. Because I've already gone through the process of installing the NCA toolkit before, I'm not going to run into the same potential problems that you might. But when I get to the sections where you might encounter an issue. I'll point that out to you and also provide some ideas on how you can fix it. Now, you can avoid some of those issues if you use a standard Gmail account. But down the line, if you're a business and you want that inside of your Google workspace, you might have to redo it. But on the flip side, if you're just playing around and you want to install this quickly with as few issues as possible, you might consider just using a standard Gmail.com account. So with that, I'm going to assume that you already have your Google Cloud account. and then you've selected the right account in the upper right hand corner. So the first thing that you're going to want to do is to create a new project. I'm already in an existing project so I'm going to come up here to the project selector and then you're going to want to find the button for a new project. Go ahead and click on that and then you go ahead and give your project a name. NCA Toolkit API YouTube Demo. I'm going to go ahead and create that project. Once that project is completed you can go ahead and select that project. And then later on, you can always use this selector up here to switch between projects. I'll select the new one. Now we can see we are in that new project. Now the instructions I'm following today are located on GitHub. I'll also provide this link in the description below. The first thing that we're going to do is we're going to enable a few APIs, the Cloud Storage API, the Cloud Storage JSON API, and the Cloud Run API. So I'm going to come back to Google Cloud. We're going to go to API and Services, Enable APIs and Services. I believe we can go ahead and start to type those here. I'm going to type storage API. I'll go ahead and hit enter. We can see that pop up right here. So I'm going to go ahead and select that. It already looks like for me, this is already enabled. If it's not for you, there'll be an enable here. You'll want to go ahead and click through to that. Next, we're going to do the JSON, the storage JSON API right here. Looks like it's already enabled for me. If it's not for you, you can go ahead and enable it there. And then finally, we want to get the Google Run admin API. So we'll come back up here. Google run admin API. Go ahead and hit enter. And then in this case, it's asking me to go ahead and enable it. So now that we have that, we should be good to go. Next up, we're going to go to the menu and then we are going to navigate to the IM and admin section. And then we're going to go to service accounts. And then here we need to create a new service account. Here I'm going to go ahead and call mine the NCA toolkit SA for service account. And then I'll just put YouTube demo. Then you'll go ahead and create and continue. Then here we're going to go ahead and type storage admin. You're going to go ahead and select that. Then you'll want to add another role. Here we're going to type viewer. You'll go ahead and select that. Now you can go ahead and click continue and then done. Now you'll want to click through to your NCA toolkit service account. Navigate to keys. Now you're going to go down to add keys. Create new key. You'll go ahead and select JSON. And then you'll hit create. Now if you're using a Google Workspace account, this is where you might see your first error. It could look something like this. Service account key creation is disabled. I have some instructions on GitHub on how you can overcome this issue. You just need to follow these instructions very carefully. I've also seen people overcome the same issue with ChatGPT and you can always join. no code architects for support as well i'm going to go ahead and click create notice this is going to download a file to your downloads folder you can see here private key saved to your computer keep that in mind we're going to use that file later go ahead and close next up we are going to head back to our menu and go to cloud storage here we're going to head to buckets and we're going to create a new bucket i'm going to go ahead and call it the ncaa toolkit bucket youtube demo we're going to go ahead and click continue you can go ahead and use the defaults here go ahead and click continue at this step you can go ahead and click through on continue at choose how to control access to objects uncheck this box here for enforce public access prevention this is going to allow us to allow public access to the files we upload leave this on uniform go ahead and click through on continue and then you can leave the defaults on for this should look something like this go ahead and click create it's going to go ahead and create that bucket you should have that here Next up, we're going to go to permissions. We're going to go to grant access. For new principles, we're going to go ahead and type all users. You'll select that here. And then you'll select storage object viewer. You'll select that here. Now, this is another area where you might run into a permission problem if you're using a Google Workspace account. It depends on when your Google Workspace account was created. They've enforced a lot of new security rules. If you run into that issue, make sure to check out the documentation on GitHub. You can use ChatGPT or feel free to jump into the NoCode Architects community. I'm going to go ahead and click save. It's now going to give you this warning. Go ahead and allow public access. Now we're going to jump back to our menu and we're going to head over to the Cloud Run service. From here, we're going to create a service. You can leave it on this option here. We're going to use a Docker Hub image. Now, before I continue, make sure you do everything that I do below exactly as I do it very carefully or you will run into issues. and you may not know how to solve them for the container image url i'll link this in the description below but you want to grab this text and copy and paste it directly here for the service name if you'd like to change it you can or you can leave it at the default you want to make sure to allow unauthenticated invocations giving you another warning here another permission that you may need to check out pretty sure my workspace is already configured to allow Under CPU allocation and pricing, it's very important that you select CPU is always allocated. For service scaling, you're going to go ahead and leave minimum number of instances at zero. Then you can go ahead and open up containers, volumes, networking, and security. Here you're going to see the container image that you put above, and you're going to leave the container port alone. Let's go ahead and set up the rest of these settings, and then we're going to come back to variables and secrets. For memory, I tend to go with 16 gigabytes, which requires four CPUs. What's nice about Google Cloud Run is that it only runs when you actually make a request. So even using larger resources like this isn't an issue because these processes tend not to run very long. However, you do want to make sure that you're tracking your billing to make sure you know what is being charged on your account. You can leave GPU off. You don't need to worry about health checks. You can leave the request timeout at 300. Maximum concurrent requests per instance. You want to move this to one and you'll want to click second generation. and for minimum number of instances you can leave that at zero and for maximum number of instances i usually go with five depending on your google account you might be limited and may not be able to enter five in that case you can always just enter one go ahead and leave the startup boost on now before we actually create this go ahead and scroll back up we're going to go to variables and secrets now this is very important that you follow exactly what i do here some common mistakes is that when people enter in these values here i'm going to be using underscores and sometimes i see people use dash instead or they make a spelling mistake if you get this wrong it will not work and when you are putting in these values do not put spaces before you type or after you type it will cause an issue when you go to test out your toolkit so for environment variables the first one we are going to use is api underscore key again make sure there are no spaces before or after you've spelled this exactly as i have and you're using an underscore not a dash Here, I'm going to go ahead and type in test123. Down the line, you'll want to change this to something more secure. But for now, let's go ahead and just use that. We're going to add another variable, gcp underscore bucket. And again, notice that these are all uppercase as well, underscore name. Now, in another window, you'll want to come back to your menu, head back to your cloud storage, head over to your buckets. I would go ahead and click into this and then cut and paste. directly with nothing before or after and then you can drop that into the value section. Again make sure that it's spelled exactly the same and there's no spaces before or after. I've seen countless people make that tiny mistake and then they get really thrown off. Nothing before after. GCP bucket name underscores. Just double check everything. This is the time to do it. Go ahead and add another variable. This time we're going to type GCP underscore SA credentials. Again, GCP underscore SA underscore credentials. Now we're going to go to our downloads file. Remember we downloaded a file earlier in the process. You should see this JSON file that was downloaded when we created the service file. You'll want to open that up with a text editor. I'm going to go ahead and use visual. code studio go ahead and copy the entire contents of that file and you'll want to paste that directly into this value here once you've got that you can go ahead and create your service assuming you've done everything right this should turn into a green check mark it might take a few minutes to deploy the first time and then once it's done you should see this green check mark if you are not seeing this green check mark make sure you go back on this video and double check everything that we've done together Feel free to use the NCA toolkit API GPT if you're having issues or feel free to jump into the no code architects community. All right. So now the final thing to do is just to make sure that everything we've done was done correctly and that the toolkit is actually working. And then you'll be able to experiment with the toolkit and then actually use it within your own automations. So the best way to test out the toolkit is with a tool called Postman. We were looking at this tool earlier in the description below. There is a link that will allow you to copy this entire suite of. NCA Toolkit API examples. But before you do that, make sure you go to Postman. You can access it at postman.com. You want to make sure that you download the desktop app for your computer. They do actually have a web version that you can use, but it's much better to download it to your desktop and you'll face fewer issues. So make sure you download it and install it. And then once you've completed the download and created your account and you've actually signed in, in the description below, there's going to be a link that you can use. that will give you access and the ability to copy all of the different examples i have here in this exact same format also make sure to log in to the web before you actually do this so that when you use this link it will actually import it into your account so you'll want to be logged in on the web and also on your desktop application then you can copy and paste that link in the description below for postman you should see something that looks similar to this Before you actually try to use it, you want to come to the three dots and you'll want to create your own fork. Otherwise, this is just a template that you can't use and you won't be able to actually run the examples. So make sure you create your own fork. You can go ahead and give it a name. You can leave on the notifications. That way, when I make changes, it'll give you a notification. Go ahead and fork that collection. Once you've created your own fork of the examples, make sure to go back to the desktop application. and then find your new workspace where you should see all of the examples here then the first thing that you're going to notice once you click on and open up one of these folders and click on something like captions you're going to see a base url here that is colored red we need to create two environment variables one is the base url and then one is also the x api key so head over to the top right and go to environment go ahead and click on that you can see i already have two environments here one for when i'm testing locally and then one for when I'm on the Google Cloud, you'll want to go ahead and click the plus sign. From here, you're gonna add a new variable. Go ahead and use curly brace base underscore URL, close curly brace. So you have two open curly braces, base URL, and then two close curly braces. And then for the initial value, you're gonna jump back to your Google Cloud. We're gonna pick up where we left off here, and we're gonna come up here to the top, and we're gonna copy this URL back into Postman. you can put that right here into the initial value then you're going to add another variable this time two curly braces x dash api dash key and then two close curly braces here you're going to put test one, two, three. Again, remember that is the value that we put into our environment variable right here. Test one, two, three for the API underscore key. I'm going to jump back to Postman. Now, the final thing here is that you must save this or it won't actually register. So make sure you save it. You can come up here and just click save. And then once you have these variables defined, you can come back to your examples. And now I'm noticing that this is still red. It's not picking up the values that we added in to the environment. Actually, I'm seeing what the issue is. When I created the new environment, when I came up here to the plus, I added in those curly braces before and after in the environment variable when I should not have. Those curly braces are only used when you are actually using the variables within the Postman configuration here in the URL and then also in the headers. So we see that here. But when you're creating the environment variable, you don't want those in there. So let's go ahead and fix that. I'm going to come back up here to the environment tab. If you have already closed that, you can get access to it again if you come to the environments and then you select the environment. And then if you click on environment, it should open up the tab again. I'm going to go ahead and close it. And again, I'm here. Select the environment. You come here and then you just click environment. It should open up again. And then I'm going to come back here. I'm going to remove the curly braces that are after and before the variable name. So it's just base URL. base underscore URL and also on the xAPI key, just like that. And now make sure you save it because if you don't save it, it's not going to save or it's not going to publish throughout the rest of these examples. If I come back to concatenate, now we're seeing the variables come through. So if I click through to any of these, they should all be this gray color, as well as the headers here. The xAPI key should also be gray. That means you've configured it correctly. Now... If for whatever reason you're having trouble with these environment variables, you just can't get it to work, you can always come in here and just copy and paste the URL directly into this box here. So if we're here and we copy this URL and we jump back to Postman, you can always just come here and simply delete the variable and then you can just paste that directly into the URL box here. Make sure that everything is correct here. Notice that I still have this endpoint here and there's not two slashes. So just make sure everything looks okay here, but you can always just copy and paste the values directly into Postman if you want. And same goes for the XAPI key, correct? So if I come here to the value, I can erase this and I can just type test one, two, three. But you can see why this would be a pain because if you have a bunch of different examples here, or if you change your password, going through every single example and having to change these values, like let's say you deploy a new server, you wanna change that. Having to go through every example and changing these is a pain. So that's what the variables let you do. I'm going to come back here to this example here and return this back to the way it was. Curly brace, base URL, close curly brace, and you can see it turned back into a variable there. And I'll do the same here for the xapi key and the value. xapi key, always opening with two curly braces and closing with two curly braces. And then you can save everything. Anytime you see a little red dot in any one of these tabs, it means it wasn't saved before. All right, so now that we have these variables fixed and they are gray, both in the base URL of the URL for the endpoint and also here in the headers for the xAPI key, and we can just go to any of these and we see those there and they are not red, we are good to go ahead and test the toolkit. So if it's not already expanded, come down here to the toolkit. if it looks something more like this or whatever state it is you just want to get to the toolkit and then the first thing that we're going to go to is authenticate again the base url should be gray as well as the x api key so now all we have to do is simply hit send here if this is grayed out it likely means that you didn't create your own fork so in that case just make sure you clone it first and then go ahead and click send and what we are looking for here is the response with authorized so the first time you send the request it might take just a few seconds as it's booting up the container in google cloud if this comes back and returns some sort of error then you're going to want to go back and make sure that you set up everything in your cloud correctly and again when there are issues it's usually related to the environment variables or the different values that were set up here in the beginning double check all of those values And then if you are getting an error, go ahead and send the request again. And then once you are getting the request back, what you're looking for here is authorized. And if you're getting unauthorized, it usually means that the XAPI key that you set in your environment variables is not correct. So you can come back to your environment variables, fix that password, both here in the initial value and the current value, and also make sure to save it. And then you can come back to the authenticate. and run it again. And if it's still off, then make sure that you come back to your Google Cloud and double check that you have everything here, right? You've spelled everything correctly. You're using underscores. There's no spaces before and after. This should say API underscore key. I always go with test one, two, three in the beginning. And if you just get stuck and you want some help, feel free to jump into the NoCode Architects community. Once you see that authorized, you're good to go. The last thing that you need to do is just check this test. endpoint here this is going to make sure that everything in the api is functioning and it's able to upload files to the google cloud storage that we created earlier so once you're here again you should see the gray base url and the gray x api key and then go ahead and click send again you're looking for that success it's going to return to you a file that says success.txt go ahead and open that up and it should say you have successfully installed the ncaa toolkit api great As long as both of these two things are working, then you're good to go. If not, you'll need to go back and correct any of the issues. Otherwise, if you're seeing that success, congratulations, you've successfully installed the no-code architects toolkit. So finally, let me also show you in Make, once you have this set up, how to actually call the API from make.com. We're going to go ahead and use this HTTP module. If you're starting a scenario from scratch, you can come here to Make. You can click HTTP. you can scroll down and make a request now for the url it's going to be the same url that we copied here grab that come back and drop that into make now depending on which endpoint you are using you're going to want to add the slash and then the full path of that endpoint url let's head back to postman i'll head up here to concatenate i'm going to grab this part of the url here make sure you grab the slash and everything after it and do not include that actual base url We actually copied that earlier right here so we don't need that. Put this into the URL box here. Make sure not to have two slashes here. I actually have two slashes so I'm going to remove one. The method is a post and you can see that in Postman as well. You can see that we have a post here and here. Next we have to add the headers and notice we're just setting the same settings here that we have here in Postman. Postman and the HTTP module essentially do the exact same thing, they just look a little bit different. So we want to make sure we have that X API key from the headers and that password or the API key directly here in the headers here. X dash API key. And then for that value, we'll put test one, two, three. Now for the body type, we're going to go ahead and select raw for the content type. We're going to go ahead and click JSON. And then for the request content here, we are going to jump back to Postman. We'll go ahead and grab the body. Go ahead and copy and paste. And then I'm going to go ahead and come back to make, and I'm going to go ahead and paste this exact code as it was in Postman directly into make. Now I've noticed sometimes, depending on the computer, when people copy and paste that value into the request content, they get a 400 error. Now I think it's related to whether they are on a PC or a Mac, but irregardless, if you run into that error, I assure you that the contents here are correct, but sometimes these spaces or new lines. in the code will cause that 400 error. So if you run into that, just come into the request content and just remove all of the spaces, all of the new lines, so that it's just one continuous piece of text. Remove everything here. Make sure you don't delete anything in that process. Be very careful. You can go ahead and change this to parse response. Go ahead and click OK. If you want, you can save it. Then you should be able to run once. Now it's calling our server. you should get status code 200 and the data here should give you a response and this should be the concatenated video we can just copy that right into our url here if you remember earlier i believe that video was nine seconds so this one should be 18 seconds and there we go it's that video that's duplicated twice each clip was nine seconds so now the total is 18. now if you need help with the toolkit don't hesitate to join the no code architects it's an engaged community you can submit all your questions to tech support It's a community, so others help each other as well. There are calls with me almost every single day. And inside the classroom, there's also a make an Airtable beginner course, access to all my automation templates, and a whole lot more. I hope to see you there. Either way, I hope you enjoyed this video and I'll see you on the next one.

Subscription services like OpenAI, Creatomate, and JSON to video run servers on the internet with some code that allows you to access their resources through an API for a monthly fee. And it's very easy for these subscription services to add up. And the NoCode Architects Toolkit is meant to replace all of these costly services.

And how we help you do that is that we wrote some of our own code. that you can easily deploy into your own server and access through an api inside of your own automations at almost no cost to you you can even use the toolkit to build more efficient automations here's a single module on the no code architect running some python code i'll show you how this works but it eliminates hundreds of operations and replaces it with a single operation And it scales well too, even if this automation were to process more data, we would only burn one operation, whereas otherwise this module would continue to eat up more and more operations. So today I'll go over all the features of the NoCode Architects Toolkit by showing you examples of how we can create video, transcribe it, how we can transform media into different types, manipulate and combine videos, caption videos. I'll show you how to use the custom GPT I built to help you use it.

And of course, I'll show you how to install it on the Google Cloud platform so that you can start saving money today. Now, after you've actually installed your NCA toolkit server on the Google Cloud, and I'll show you how to do that later in the video, you can access that API in your automations through the no code architects toolkit make module. We're continuing to build this out and to add more features, but you can also access your no code architects toolkit API through the common HTTP module that you find in make. And again, after I help you install the toolkit, later in the video, I'll show you how to set this up. But I'm actually gonna demo some of the features today in a tool called Postman.

This is a great tool for testing API calls. It really does the same thing as these two modules. It just allows you to test quickly.

And you can also save a bunch of different API calls for testing and demonstration like I'm doing today. I'll also give you access to the sample of API calls so that after you install Postman, you'll have access to all of these for testing. It's great when you can just cycle through here and just see how all of these things are built. There are sample files here. You can just hit send and it'll work and then you can explore and modify as you see fit.

But let's just go ahead and start at the top and we'll move down and I'll show you a bunch of examples on what this toolkit is capable of. So at the top here we have the caption feature. You essentially just pass it a video.

I'll copy this and put it in the browser so you can see. This is just a quick short video of me on the School Games podcast and then there's just a bunch of different settings here that control the color, the font size, how many words per line. bold, italic, underline, strike out, the outline width, sometimes called the stroke.

And then I'm adding in a shadow on the font as well. The captions API is quite powerful. You can control the positioning. You can control exactly the X and the Y of where the caption should be. Let's go ahead and test this out and see what it looks like.

All right, so it looks like that process completed. So let's go ahead and take a look at the file. So here is the captions. This is just the classic style.

So let's go back and do something a little more fancy. We'll go with highlight. We'll go ahead and run that again.

Looks like it's done. Let's take a look at this new file. So now you can see we've got an active color here.

Let's go back and we'll choose a font style. I like the bold font. I'm going to go here also and move it to three words per line.

It's not font style, it's font family. Send that again. I realize there I've got a dash instead of an underscore. That should fix it.

Alright, so now the next video is done. Let's go ahead and test it out. And of course we can come here and control the x and y.

We'll go with 400 and y 400. So on our video here, We can control those captions to be at some x and y coordinate. We'll go ahead and run this as well and we can take a look at that new file. So now you can see we can actually adjust and put the captions at a specific x and y coordinates on the video.

There's also some built-in positioning so you can just type position. and something like bottom center and we'll give that a test. So now it's at the bottom center and there's also a cool feature that allows you to find and replace words in the video. So if I type replace here I can actually send it an array of objects to find we'll just go with you and we'll replace it. with these characters here.

But this is handy for when the transcription service commonly gets certain types of words wrong. You can put this in here and automatically replace them. Sometimes you'll see that when you're talking about URLs or emails. It really just depends, but this allows you to address it. So we'll go ahead and test this as well.

So now let's take a look at this new video here. You can see right there the word you was replaced here by that string that we added right here. So this is a really powerful one. I encourage you to explore the captions api and see what it can do then moving along we also have a function here that allows you to concatenate two videos together this is a simple one that comes up a lot and so this becomes a very handy tool to have here you can see i'm just linking to two videos and that's that nine second video here so once we run this and we check out the url you can see here we have a new video that's 18 seconds long it's simply the same video that's concatenated and repeated i use this end point a lot in my faceless video generator and now next up we have the ffmpeg comp pose endpoint this is a feature that was created really after i had developed several other end points like this one here for concatenating videos it just turned out that there were so many different things that we needed to do with audio and video that it'd be hard to create separate functions for everything that we needed to do and what a lot of these endpoints actually did like concatenate is that they really just worked with a tool called ffmpeg and we don't have to go into a lot of detail here But a lot of the functions that I was developing inside the toolkit were actually using that FFmpeg tool. And so what I found was that instead of having to try to create new API calls for everything, although it's nice to have some things that are used a lot like concatenate, it would actually be better to develop a tool that was more flexible where you could pass in different types of media.

In this case here, we have a FFmpeg compose function that is actually concatenating two videos. just like the endpoint that I showed you here, but it's showing you how to combine these videos using FFmpeg Compose instead of using the dedicated endpoint. So this is a good example to see what's happening behind the scenes in this concatenate API call. Here's another example where we actually pull a clip from another video. So let's take a look at this source video here that we have.

Here's a two minute YouTube video that's horizontal style. Again, I just have a bunch of these videos up on the cloud for testing. Once you download Postman and get access to this workspace, you'll have all of these examples that you can pull from, including those videos on the cloud.

And then you can just replace it with your own videos. But if we run this example here, it's going to give us a five second clip starting at second 10 all the way to 15. So let's give that a try. Let's go ahead and test this endpoint.

So we can scroll down here. We can see that the file URL is here. Go ahead and open that up.

And notice now we have a five second video that was clipped from second 10 to 15. And so next up, this example here will actually crop a video out of another. So we have a horizontal video, the one that we were just using before. It'll actually crop out a vertical video. And then because the height of that vertical video would just be 1080 pixels, it'll actually scale it to the proper size for. vertical videos on social media which is 19 20 and you'll see these specific values inside the api call so you can start to see how everything works and after some time and with the help of the gpt that we created specifically for this toolkit api it becomes quite easy to build these json's for each of these different endpoints So again, we're using that same horizontal YouTube video.

Let's go ahead and give this one a try. It looks like it finished, so let's go take a quick look. So now we have the vertical video that was pulled from the horizontal video using the coordinates that we added here and then scaling it up to the proper size. Next up, we have another example here, which will grab a still frame from a video. So here again, I'm using that vertical video clip that was taken from the School Games podcast.

I'm gonna grab a still frame at the first second here. Let's go ahead and run it. so this is a good way to get thumbnails from your videos let's go ahead and open that up and here we go this one's just an image and in this next example we're going to overlay a logo on top of a video here i'm using that youtube video again but in this case i have a logo i'm going to open that up in the browser here just so you can see so we have the no code architects toolkit logo and we'll go ahead and run this example and while that's running we can see here that we are scaling that logo to the proper size and then we are overlaying that on top of the video at a specific coordinate and you might also notice that in this particular case the api is giving us some additional information and i'll talk about that in just a moment but that's because we are adding in this metadata object here which allows us to get access to some additional data when we run these commands to ffmpeg compose so here's that youtube video and now you can see we've embedded that logo in the bottom left corner In this next example, we're going to build a tweet pic. So I've got two images here.

I'm going to grab this one just so we can see what it looks like. This is a still image pulled from the School Games podcast. And then this here is a...

Image as well. This is a tweet pic image that we can embed on that image to create a new piece of content Let's go ahead and run this example. Here's the output.

Let's take a look So here's the school games image with the tweet pic overlay done for us automatically We can also do a tweet video in this case I'm going to use that school games podcast clip with a tweet pic So instead of doing a tweet pic on top of a image, we're gonna do it on top of a video Let's go ahead and run this example. So now we've got that video with that tweet pic that is overlaid on top of the video then in this next example this is going to build a reaction style video you might have seen these where someone is watching another video they're sitting here and down here in the corner there's another video that they're watching and then after it's done they react to it so let's take a look at the source material for that we have a reaction video so this is me reacting to the video and then at the end i'm actually saying something about the video itself and then this is the video that i'm actually watching and reacting to let's take a look at that and i'm actually reacting to my own school games podcast clip just for fun so let's go ahead and run this example and again i made these examples so you can start to look and see how these things are designed and of course you can work with the gpt that we built for the ncaa toolkit specifically here you can see the first thing that we're doing is we're making sure that the video that i'm watching is scaled up to the proper size i'm scaling that video down into position we're also drawing a red box around the video i'm reacting to and there's a few other settings here as well but let's go ahead and take a look at the output video and so here you can see there's me reacting to that school games podcast clip and we also generated that red box around it so if we were to let that play you would just see me reacting to my own video and then once this video was over it would disappear and then you would see my reaction and then we have another example here where we are overlaying some audio on top of a video and mixing them together and then within this filter itself you can control the volume of either of those two tracks i'm going to go ahead and replace this url with the school games podcast clip this is actually a mp3 we can take a quick listen i'm actually going to grab a different mp3 for this example here drop that in instead all right so now let's go mix these two together you might not be able to tell but that operation happened really quickly and that's also something to note that each of these different commands that we're running here are going to take a different amount of time depending on the amount of processing that has to take place so let's take a look at the clip mixed with the audio you got to keep people moving forward yeah there's all these gimmicks in the school communities around like so by no means is that all that you are capable of doing with ffmpeg compose and ffmpeg in general the tool that powers ffmpeg compose but i wanted to give a wide range of different examples so that you could see the power and maybe start to develop your own ideas of what you might want to do because this tool is quite flexible you can do all sorts of different things so try to be creative and then use the ncaa toolkit api gpt which can actually help you generate these json's just by working with it and telling it what you want to do so let's continue on with the capabilities of the toolkit here i'm in the media folder and we are going to show you how to transform media into an mp3 so this is a simple one here i'm just simply passing a vertical clip from the school games podcast and i'm asking back for an mp3 at a specific bitrate let's go ahead and run this example we can see that was quickly generated now we have an mp3 next up we have the completely redesigned transcribe module you just pass in a media url either audio or video you give it the task you can either transcribe or translate and then you just simply tell the api whether you want the text include text is going to bring back the actual transcription include SRT is going to bring back the SRT file for captioning videos. You can also include segments.

I'll show you what that is. It gives you data related to the transcription and various timestamps. You can also control whether the API gives you the response directly in the response, or it can also upload the text in the SRT file into a file and give you the file instead.

You can turn on word timestamps, which gives you the timestamp for every single word in that transcription. And then you can also set the language. so let's go ahead and run this as is so here you can see the result let me move this up a bit first here you can see the segments that's what we included right here there's just a lot of data here that you can use if you need that level of detail in whatever you're doing in some cases you'll find that this is just not needed and it's overkill and you can turn it off if i scroll to the bottom you can see we have that srt and that is a file that you can use when you are creating captions on videos and you can also see the text here as well which is just the straight transcription and so depending on what you need you can turn these on or off text srt or segments and then like i mentioned you can control whether it gives you the response back directly in the json response or we can adjust this to cloud in this case it's going to take all of this data here it's going to upload it to a file and give us the file instead Let's check that out. So here you can see we got the response, but instead we're getting the segments SRT and text as a file. We can go ahead and open that up.

So here you can see we have that same data just in a remote file. And whether you would choose direct or cloud in your automation really just depends on what your automation is doing and what is best in that particular situation. Then we have two more endpoints here, authenticate and test.

Authenticate is just a simple function that allows you to make sure that your password and your authentication and your... toolkit is working properly from an authorization point of view then there's a test endpoint which is a simple endpoint that just allows you to test to make sure your toolkit is working properly here you can see we have a success and if you open this up you're going to see the contents of that file are you have successfully installed the ncaa toolkit api great job and then next up we have another endpoint here that takes an image and transforms it into a video here i have an image that was generated in mid journey here if i run this example it's going to take that image and add a slight ken burns zoom style effect to that video you can control the length of the video the frame rate and also the zoom speed let's take a look at the output and so now you can see we have a video that does a slight zoom on that image that we provided and then finally here i want to show you the endpoint that allows you to execute python code it's all encoded here so it's a bit hard to read but i wanted to create an example to show you how you can use that endpoint here i'm using the http module in make to call the run python endpoint and it's just a simple example here where we have a bunch of youtube titles here i'll expand this so we can see it's a bit hard to see here but all of these titles are all lowercase but what if we were in a situation where we had to uppercase the first letter of each word in the title well this is how you would do that and make we're parsing that json so we're getting all of the different titles in separate bundles that we can loop through so here you can see all of the titles and all of the characters are in lowercase and then in this module here We are simply using this function start case, which will uppercase each of the first letters of each word. And so you can see here we had more than 100 titles.

So we had to run this over 100 times. And here are all of those various operations. And you can imagine if there were more titles, it would get even worse. And then we have an aggregator here that allows us to bring all the data together.

So here we can see how make helped us uppercase the first letter of each word. But now using the no code architects toolkit, using the Python code, I can open this up. There's a small bit of code here and we're passing it in those titles.

And in one operation, we do all of the work and we can see the response here from the toolkit. Here's all of the titles and we can open one up and we can see that we have uppercased the first letter of each word. So I'm gonna jump back to Postman and I've got all that code and all of those titles here. And so you can also just test this endpoint as well. Whenever you're running code, those run very quickly.

And so here you can see that we got the response and we've got all of those titles back all with that uppercase on the first letter of each word. So there's quite a few examples of what you can do with the no-code architects toolkit. There's a whole lot more that you can do with the toolkit. But first, if you're enjoying this video, make sure to like and subscribe to the channel.

Tells me what type of content you want more of. Now, before I show you how to install the toolkit so that you can use it on your own, I wanna point out And I've mentioned this before that there is a GPT called the NCA Toolkit API GPT that you can use to help you use the toolkit. I'm improving this all the time and it's a great resource just to learn about the toolkit, the different endpoints.

You can ask it questions. It'll tell you what it can do. You can even ask specific questions like, help me use the version one media transcribe endpoint. and then it's going to give you an overview and give you some examples on how to use it you can see here it'll give you an overview steps on how you can actually use the endpoint the different options and parameters you can use it'll give you sample json payloads that you can copy and paste into postman just like this or inside your make automations if you're using the http module and you can use the gpt to help you build ffmpeg compose json's give me the ff mpeg compose json payload for combining two videos into one so it'll give you that entire payload you can copy the code and modify the urls and then it'll actually break down and give you an explanation of everything that is going on in that json now one thing to note is that sometimes it will make a mistake i'm adding more and more content to better train the gpt But if you do run into errors, you can always just take that error, cut and paste it directly into the GPT itself, let it know you're running into a problem, and then it will go ahead and help you actually fix it.

And then over time, I expect the GPT to make fewer and fewer mistakes. And if you want more dedicated support, make sure to jump into the NoCode Architects community. I'll provide a link to the NCA Toolkit API GPT in the description below.

All right, so now I'm going to go ahead and show you how to install the NCA Toolkit from scratch on the Google Cloud Platform. Now, a couple of things to keep in mind. If you are new to the Google Cloud, I think you can get a $300 credit. You might go to Google and type Google Cloud 300. Then you can see that sponsored link and click through to get your free trial. But the other thing I want to point out is that I'm installing this toolkit into a Google Workspace account under my SGPLabs.com domain.

And you can control which account you're in with the Google user selection in the upper right hand corner. Now, I prefer installing it into a Google Workspace account myself because I'm a business and just in the long run, this makes a lot more sense. But I do want to point out that when you install it into a Google Workspace account, there are some additional settings that you might need to configure as you go through this install process. Because I've already gone through the process of installing the NCA toolkit before, I'm not going to run into the same potential problems that you might. But when I get to the sections where you might encounter an issue.

I'll point that out to you and also provide some ideas on how you can fix it. Now, you can avoid some of those issues if you use a standard Gmail account. But down the line, if you're a business and you want that inside of your Google workspace, you might have to redo it.

But on the flip side, if you're just playing around and you want to install this quickly with as few issues as possible, you might consider just using a standard Gmail.com account. So with that, I'm going to assume that you already have your Google Cloud account. and then you've selected the right account in the upper right hand corner. So the first thing that you're going to want to do is to create a new project.

I'm already in an existing project so I'm going to come up here to the project selector and then you're going to want to find the button for a new project. Go ahead and click on that and then you go ahead and give your project a name. NCA Toolkit API YouTube Demo. I'm going to go ahead and create that project.

Once that project is completed you can go ahead and select that project. And then later on, you can always use this selector up here to switch between projects. I'll select the new one. Now we can see we are in that new project. Now the instructions I'm following today are located on GitHub.

I'll also provide this link in the description below. The first thing that we're going to do is we're going to enable a few APIs, the Cloud Storage API, the Cloud Storage JSON API, and the Cloud Run API. So I'm going to come back to Google Cloud.

We're going to go to API and Services, Enable APIs and Services. I believe we can go ahead and start to type those here. I'm going to type storage API. I'll go ahead and hit enter.

We can see that pop up right here. So I'm going to go ahead and select that. It already looks like for me, this is already enabled.

If it's not for you, there'll be an enable here. You'll want to go ahead and click through to that. Next, we're going to do the JSON, the storage JSON API right here. Looks like it's already enabled for me. If it's not for you, you can go ahead and enable it there.

And then finally, we want to get the Google Run admin API. So we'll come back up here. Google run admin API.

Go ahead and hit enter. And then in this case, it's asking me to go ahead and enable it. So now that we have that, we should be good to go. Next up, we're going to go to the menu and then we are going to navigate to the IM and admin section. And then we're going to go to service accounts.

And then here we need to create a new service account. Here I'm going to go ahead and call mine the NCA toolkit SA for service account. And then I'll just put YouTube demo. Then you'll go ahead and create and continue.

Then here we're going to go ahead and type storage admin. You're going to go ahead and select that. Then you'll want to add another role. Here we're going to type viewer. You'll go ahead and select that.

Now you can go ahead and click continue and then done. Now you'll want to click through to your NCA toolkit service account. Navigate to keys. Now you're going to go down to add keys.

Create new key. You'll go ahead and select JSON. And then you'll hit create.

Now if you're using a Google Workspace account, this is where you might see your first error. It could look something like this. Service account key creation is disabled.

I have some instructions on GitHub on how you can overcome this issue. You just need to follow these instructions very carefully. I've also seen people overcome the same issue with ChatGPT and you can always join. no code architects for support as well i'm going to go ahead and click create notice this is going to download a file to your downloads folder you can see here private key saved to your computer keep that in mind we're going to use that file later go ahead and close next up we are going to head back to our menu and go to cloud storage here we're going to head to buckets and we're going to create a new bucket i'm going to go ahead and call it the ncaa toolkit bucket youtube demo we're going to go ahead and click continue you can go ahead and use the defaults here go ahead and click continue at this step you can go ahead and click through on continue at choose how to control access to objects uncheck this box here for enforce public access prevention this is going to allow us to allow public access to the files we upload leave this on uniform go ahead and click through on continue and then you can leave the defaults on for this should look something like this go ahead and click create it's going to go ahead and create that bucket you should have that here Next up, we're going to go to permissions.

We're going to go to grant access. For new principles, we're going to go ahead and type all users. You'll select that here. And then you'll select storage object viewer. You'll select that here.

Now, this is another area where you might run into a permission problem if you're using a Google Workspace account. It depends on when your Google Workspace account was created. They've enforced a lot of new security rules.

If you run into that issue, make sure to check out the documentation on GitHub. You can use ChatGPT or feel free to jump into the NoCode Architects community. I'm going to go ahead and click save. It's now going to give you this warning.

Go ahead and allow public access. Now we're going to jump back to our menu and we're going to head over to the Cloud Run service. From here, we're going to create a service.

You can leave it on this option here. We're going to use a Docker Hub image. Now, before I continue, make sure you do everything that I do below exactly as I do it very carefully or you will run into issues. and you may not know how to solve them for the container image url i'll link this in the description below but you want to grab this text and copy and paste it directly here for the service name if you'd like to change it you can or you can leave it at the default you want to make sure to allow unauthenticated invocations giving you another warning here another permission that you may need to check out pretty sure my workspace is already configured to allow Under CPU allocation and pricing, it's very important that you select CPU is always allocated.

For service scaling, you're going to go ahead and leave minimum number of instances at zero. Then you can go ahead and open up containers, volumes, networking, and security. Here you're going to see the container image that you put above, and you're going to leave the container port alone. Let's go ahead and set up the rest of these settings, and then we're going to come back to variables and secrets.

For memory, I tend to go with 16 gigabytes, which requires four CPUs. What's nice about Google Cloud Run is that it only runs when you actually make a request. So even using larger resources like this isn't an issue because these processes tend not to run very long.

However, you do want to make sure that you're tracking your billing to make sure you know what is being charged on your account. You can leave GPU off. You don't need to worry about health checks. You can leave the request timeout at 300. Maximum concurrent requests per instance. You want to move this to one and you'll want to click second generation.

and for minimum number of instances you can leave that at zero and for maximum number of instances i usually go with five depending on your google account you might be limited and may not be able to enter five in that case you can always just enter one go ahead and leave the startup boost on now before we actually create this go ahead and scroll back up we're going to go to variables and secrets now this is very important that you follow exactly what i do here some common mistakes is that when people enter in these values here i'm going to be using underscores and sometimes i see people use dash instead or they make a spelling mistake if you get this wrong it will not work and when you are putting in these values do not put spaces before you type or after you type it will cause an issue when you go to test out your toolkit so for environment variables the first one we are going to use is api underscore key again make sure there are no spaces before or after you've spelled this exactly as i have and you're using an underscore not a dash Here, I'm going to go ahead and type in test123. Down the line, you'll want to change this to something more secure. But for now, let's go ahead and just use that.

We're going to add another variable, gcp underscore bucket. And again, notice that these are all uppercase as well, underscore name. Now, in another window, you'll want to come back to your menu, head back to your cloud storage, head over to your buckets. I would go ahead and click into this and then cut and paste.

directly with nothing before or after and then you can drop that into the value section. Again make sure that it's spelled exactly the same and there's no spaces before or after. I've seen countless people make that tiny mistake and then they get really thrown off. Nothing before after. GCP bucket name underscores.

Just double check everything. This is the time to do it. Go ahead and add another variable.

This time we're going to type GCP underscore SA credentials. Again, GCP underscore SA underscore credentials. Now we're going to go to our downloads file. Remember we downloaded a file earlier in the process.

You should see this JSON file that was downloaded when we created the service file. You'll want to open that up with a text editor. I'm going to go ahead and use visual. code studio go ahead and copy the entire contents of that file and you'll want to paste that directly into this value here once you've got that you can go ahead and create your service assuming you've done everything right this should turn into a green check mark it might take a few minutes to deploy the first time and then once it's done you should see this green check mark if you are not seeing this green check mark make sure you go back on this video and double check everything that we've done together Feel free to use the NCA toolkit API GPT if you're having issues or feel free to jump into the no code architects community. All right.

So now the final thing to do is just to make sure that everything we've done was done correctly and that the toolkit is actually working. And then you'll be able to experiment with the toolkit and then actually use it within your own automations. So the best way to test out the toolkit is with a tool called Postman. We were looking at this tool earlier in the description below. There is a link that will allow you to copy this entire suite of.

NCA Toolkit API examples. But before you do that, make sure you go to Postman. You can access it at postman.com.

You want to make sure that you download the desktop app for your computer. They do actually have a web version that you can use, but it's much better to download it to your desktop and you'll face fewer issues. So make sure you download it and install it. And then once you've completed the download and created your account and you've actually signed in, in the description below, there's going to be a link that you can use.

that will give you access and the ability to copy all of the different examples i have here in this exact same format also make sure to log in to the web before you actually do this so that when you use this link it will actually import it into your account so you'll want to be logged in on the web and also on your desktop application then you can copy and paste that link in the description below for postman you should see something that looks similar to this Before you actually try to use it, you want to come to the three dots and you'll want to create your own fork. Otherwise, this is just a template that you can't use and you won't be able to actually run the examples. So make sure you create your own fork. You can go ahead and give it a name.

You can leave on the notifications. That way, when I make changes, it'll give you a notification. Go ahead and fork that collection. Once you've created your own fork of the examples, make sure to go back to the desktop application.

and then find your new workspace where you should see all of the examples here then the first thing that you're going to notice once you click on and open up one of these folders and click on something like captions you're going to see a base url here that is colored red we need to create two environment variables one is the base url and then one is also the x api key so head over to the top right and go to environment go ahead and click on that you can see i already have two environments here one for when i'm testing locally and then one for when I'm on the Google Cloud, you'll want to go ahead and click the plus sign. From here, you're gonna add a new variable. Go ahead and use curly brace base underscore URL, close curly brace.

So you have two open curly braces, base URL, and then two close curly braces. And then for the initial value, you're gonna jump back to your Google Cloud. We're gonna pick up where we left off here, and we're gonna come up here to the top, and we're gonna copy this URL back into Postman.

you can put that right here into the initial value then you're going to add another variable this time two curly braces x dash api dash key and then two close curly braces here you're going to put test one, two, three. Again, remember that is the value that we put into our environment variable right here. Test one, two, three for the API underscore key.

I'm going to jump back to Postman. Now, the final thing here is that you must save this or it won't actually register. So make sure you save it.

You can come up here and just click save. And then once you have these variables defined, you can come back to your examples. And now I'm noticing that this is still red. It's not picking up the values that we added in to the environment. Actually, I'm seeing what the issue is.

When I created the new environment, when I came up here to the plus, I added in those curly braces before and after in the environment variable when I should not have. Those curly braces are only used when you are actually using the variables within the Postman configuration here in the URL and then also in the headers. So we see that here. But when you're creating the environment variable, you don't want those in there. So let's go ahead and fix that.

I'm going to come back up here to the environment tab. If you have already closed that, you can get access to it again if you come to the environments and then you select the environment. And then if you click on environment, it should open up the tab again. I'm going to go ahead and close it. And again, I'm here.

Select the environment. You come here and then you just click environment. It should open up again.

And then I'm going to come back here. I'm going to remove the curly braces that are after and before the variable name. So it's just base URL. base underscore URL and also on the xAPI key, just like that.

And now make sure you save it because if you don't save it, it's not going to save or it's not going to publish throughout the rest of these examples. If I come back to concatenate, now we're seeing the variables come through. So if I click through to any of these, they should all be this gray color, as well as the headers here.

The xAPI key should also be gray. That means you've configured it correctly. Now...

If for whatever reason you're having trouble with these environment variables, you just can't get it to work, you can always come in here and just copy and paste the URL directly into this box here. So if we're here and we copy this URL and we jump back to Postman, you can always just come here and simply delete the variable and then you can just paste that directly into the URL box here. Make sure that everything is correct here.

Notice that I still have this endpoint here and there's not two slashes. So just make sure everything looks okay here, but you can always just copy and paste the values directly into Postman if you want. And same goes for the XAPI key, correct? So if I come here to the value, I can erase this and I can just type test one, two, three. But you can see why this would be a pain because if you have a bunch of different examples here, or if you change your password, going through every single example and having to change these values, like let's say you deploy a new server, you wanna change that.

Having to go through every example and changing these is a pain. So that's what the variables let you do. I'm going to come back here to this example here and return this back to the way it was. Curly brace, base URL, close curly brace, and you can see it turned back into a variable there. And I'll do the same here for the xapi key and the value.

xapi key, always opening with two curly braces and closing with two curly braces. And then you can save everything. Anytime you see a little red dot in any one of these tabs, it means it wasn't saved before.

All right, so now that we have these variables fixed and they are gray, both in the base URL of the URL for the endpoint and also here in the headers for the xAPI key, and we can just go to any of these and we see those there and they are not red, we are good to go ahead and test the toolkit. So if it's not already expanded, come down here to the toolkit. if it looks something more like this or whatever state it is you just want to get to the toolkit and then the first thing that we're going to go to is authenticate again the base url should be gray as well as the x api key so now all we have to do is simply hit send here if this is grayed out it likely means that you didn't create your own fork so in that case just make sure you clone it first and then go ahead and click send and what we are looking for here is the response with authorized so the first time you send the request it might take just a few seconds as it's booting up the container in google cloud if this comes back and returns some sort of error then you're going to want to go back and make sure that you set up everything in your cloud correctly and again when there are issues it's usually related to the environment variables or the different values that were set up here in the beginning double check all of those values And then if you are getting an error, go ahead and send the request again. And then once you are getting the request back, what you're looking for here is authorized.

And if you're getting unauthorized, it usually means that the XAPI key that you set in your environment variables is not correct. So you can come back to your environment variables, fix that password, both here in the initial value and the current value, and also make sure to save it. And then you can come back to the authenticate.

and run it again. And if it's still off, then make sure that you come back to your Google Cloud and double check that you have everything here, right? You've spelled everything correctly.

You're using underscores. There's no spaces before and after. This should say API underscore key. I always go with test one, two, three in the beginning. And if you just get stuck and you want some help, feel free to jump into the NoCode Architects community.

Once you see that authorized, you're good to go. The last thing that you need to do is just check this test. endpoint here this is going to make sure that everything in the api is functioning and it's able to upload files to the google cloud storage that we created earlier so once you're here again you should see the gray base url and the gray x api key and then go ahead and click send again you're looking for that success it's going to return to you a file that says success.txt go ahead and open that up and it should say you have successfully installed the ncaa toolkit api great As long as both of these two things are working, then you're good to go. If not, you'll need to go back and correct any of the issues.

Otherwise, if you're seeing that success, congratulations, you've successfully installed the no-code architects toolkit. So finally, let me also show you in Make, once you have this set up, how to actually call the API from make.com. We're going to go ahead and use this HTTP module.

If you're starting a scenario from scratch, you can come here to Make. You can click HTTP. you can scroll down and make a request now for the url it's going to be the same url that we copied here grab that come back and drop that into make now depending on which endpoint you are using you're going to want to add the slash and then the full path of that endpoint url let's head back to postman i'll head up here to concatenate i'm going to grab this part of the url here make sure you grab the slash and everything after it and do not include that actual base url We actually copied that earlier right here so we don't need that.

Put this into the URL box here. Make sure not to have two slashes here. I actually have two slashes so I'm going to remove one. The method is a post and you can see that in Postman as well. You can see that we have a post here and here.

Next we have to add the headers and notice we're just setting the same settings here that we have here in Postman. Postman and the HTTP module essentially do the exact same thing, they just look a little bit different. So we want to make sure we have that X API key from the headers and that password or the API key directly here in the headers here.

X dash API key. And then for that value, we'll put test one, two, three. Now for the body type, we're going to go ahead and select raw for the content type.

We're going to go ahead and click JSON. And then for the request content here, we are going to jump back to Postman. We'll go ahead and grab the body.

Go ahead and copy and paste. And then I'm going to go ahead and come back to make, and I'm going to go ahead and paste this exact code as it was in Postman directly into make. Now I've noticed sometimes, depending on the computer, when people copy and paste that value into the request content, they get a 400 error.

Now I think it's related to whether they are on a PC or a Mac, but irregardless, if you run into that error, I assure you that the contents here are correct, but sometimes these spaces or new lines. in the code will cause that 400 error. So if you run into that, just come into the request content and just remove all of the spaces, all of the new lines, so that it's just one continuous piece of text. Remove everything here. Make sure you don't delete anything in that process.

Be very careful. You can go ahead and change this to parse response. Go ahead and click OK.

If you want, you can save it. Then you should be able to run once. Now it's calling our server.

you should get status code 200 and the data here should give you a response and this should be the concatenated video we can just copy that right into our url here if you remember earlier i believe that video was nine seconds so this one should be 18 seconds and there we go it's that video that's duplicated twice each clip was nine seconds so now the total is 18. now if you need help with the toolkit don't hesitate to join the no code architects it's an engaged community you can submit all your questions to tech support It's a community, so others help each other as well. There are calls with me almost every single day. And inside the classroom, there's also a make an Airtable beginner course, access to all my automation templates, and a whole lot more. I hope to see you there. Either way, I hope you enjoyed this video and I'll see you on the next one.

Transcript for:NoCode Architects Toolkit Overview

Transcript for:
NoCode Architects Toolkit Overview