WEBVTT 00:00.240 --> 00:04.960 I'm sure I created the best LinkedIn posting system you will ever see. 00:05.120 --> 00:07.160 And trust me, I know what I'm saying. 00:07.200 --> 00:13.120 I spent a few days on building this project because actually it does everything for you from making 00:13.120 --> 00:19.760 a research and picking the most popular topic to actually creating all of the LinkedIn and post parts 00:19.800 --> 00:25.920 such as post description, LinkedIn, title image, prompt to going through actually the process of 00:25.920 --> 00:27.880 generating the high quality image. 00:27.920 --> 00:32.080 Picking the best one and actually auto publishing it on LinkedIn. 00:32.080 --> 00:35.760 So either on your personal account or just your business account. 00:35.760 --> 00:39.400 And I will be showing you everything in this specific video. 00:39.960 --> 00:46.200 And trust me, if you watch this lesson to the end, your skills will skyrocket because we'll be building 00:46.200 --> 00:51.360 this entire project from scratch, from setting the trigger to setting all of the nodes here. 00:51.600 --> 00:57.160 And in general, you will see how to use different nodes, how to combine it together, how we solve 00:57.200 --> 00:59.400 errors actually approximately. 00:59.440 --> 01:03.490 And this automation, I had over 100 errors before building it. 01:03.530 --> 01:04.930 It's highly complex. 01:05.130 --> 01:11.010 And again, watch this video to the end because after you do this, your skills will be much better 01:11.170 --> 01:13.570 and you will be much more experienced. 01:13.930 --> 01:17.850 However, before we get started, let me show you how this automation works. 01:17.850 --> 01:19.730 And actually I will run this automation. 01:19.730 --> 01:23.530 So we will see the post generated with this entire project. 01:23.530 --> 01:26.810 But first things first here we've got the instructions. 01:26.810 --> 01:28.650 So what it does step by step. 01:28.690 --> 01:33.050 The first thing what we do we provide the keyword via our chat. 01:33.050 --> 01:36.570 And there is a disclaimer actually you can have different triggers. 01:36.570 --> 01:43.410 For example right here in the alternative I provided for you other actually beginning of this automation. 01:43.410 --> 01:45.770 So you can use a trigger which is schedule trigger. 01:45.770 --> 01:50.450 You can run this automation every day and publish your content on autopilot. 01:50.450 --> 01:51.050 All right. 01:51.050 --> 01:55.330 So then you've got Keyword Agent that creates for you this specific keyword. 01:55.450 --> 01:58.010 However um let's move to the back end. 01:58.050 --> 02:04.010 So in general, for the original version for this project we provide specific keyword for. 02:04.010 --> 02:06.730 For this case, maybe it can be a agent. 02:07.010 --> 02:09.890 Then what we do we do the keyword research. 02:10.050 --> 02:13.450 So we use HTTP request and we connect to Google. 02:13.650 --> 02:19.290 So we search for the most relevant related and popular keywords right now to the keyword we provided 02:19.290 --> 02:20.130 in the chat. 02:20.730 --> 02:26.290 So simply if I provide some keywords to my chat then what it does it takes from the internet, from 02:26.290 --> 02:32.210 Google search the most and the best related keywords to the specific keywords, and it returns it for 02:32.210 --> 02:32.490 me. 02:32.530 --> 02:38.250 So actually what we do, we take the most popular topics from the internet right now and we create the 02:38.250 --> 02:39.370 post about it. 02:39.850 --> 02:41.610 So it simply works by this way. 02:41.650 --> 02:47.130 And after we run this step, we get our search results and then we need to format them. 02:47.130 --> 02:51.370 So we are using these fields and right away we go ahead to our loop. 02:51.370 --> 02:53.450 So content creation and part. 02:53.490 --> 02:59.780 So in general what we do here um the list of approximately ten keywords, is stored in a variable and 02:59.780 --> 03:02.100 passed into a loop for content generation. 03:02.220 --> 03:06.300 So inside the content generation loop for each keyword. 03:06.300 --> 03:08.860 So we will have approximately ten runs. 03:08.900 --> 03:15.500 We generate LinkedIn post description title for the post tailored image prompt um which is actually 03:15.500 --> 03:16.180 given for us. 03:16.180 --> 03:16.780 All right. 03:17.020 --> 03:23.460 So for this case we've got our free agents that are creating for us the entire content and we save. 03:23.460 --> 03:30.860 Additionally, um, like this information inside Google Sheets, after our content is generated, we 03:30.860 --> 03:33.340 store all of the data inside Google Sheets. 03:33.340 --> 03:35.100 So approximately ten ideas. 03:35.260 --> 03:36.900 And now even you can ask, all right. 03:36.940 --> 03:39.860 But for what do we need ten content ideas. 03:40.260 --> 03:47.940 And actually the reason is very simple because um, by this way we expand our possibility to choose 03:47.940 --> 03:49.300 the best content, all right. 03:49.500 --> 03:51.220 For this specific purpose. 03:51.220 --> 03:54.620 After we've got this loop, we create ten content ideas. 03:54.820 --> 04:01.510 We've got our a agent that chooses for us one keyword, and then we retrieve the data for the specific 04:01.510 --> 04:02.070 keyword. 04:02.190 --> 04:04.910 So this agent is pretty I can say complex. 04:04.910 --> 04:06.190 We've got a think node. 04:06.710 --> 04:07.990 We've got the search web. 04:07.990 --> 04:12.470 So we search for which one actually keyword and which one content which will be the best. 04:12.470 --> 04:14.470 We've got structured output parser. 04:14.630 --> 04:21.750 And then after we choose one keyword from ten of them and we search for the data, because actually 04:21.750 --> 04:25.630 we saved the keyword along with the content inside Google Sheets before. 04:25.830 --> 04:30.630 So we search for this content and we retrieve it and then we generate our image. 04:30.790 --> 04:37.270 And this part is, I can say really interesting because what we do, we generate our image, we convert 04:37.270 --> 04:39.590 it to file, we get image URL. 04:39.630 --> 04:43.270 However what we do inside this specific I can say loop. 04:43.310 --> 04:47.950 And this is actually not the loop however condition if we analyze our image quality. 04:48.110 --> 04:55.240 So we ask all right if this image is high quality, if don't we have truncated text or any, you know, 04:55.280 --> 04:56.640 cut words or so. 04:57.240 --> 04:59.560 So actually this node does everything for us. 04:59.600 --> 05:02.560 And then it returns the response which is yes or no. 05:02.880 --> 05:09.760 If actually the response is yes we generate another image until the image is perfect for our LinkedIn 05:09.760 --> 05:10.280 post. 05:10.280 --> 05:13.440 So we've got this step which is kind of our safety net. 05:13.640 --> 05:17.880 So again until our image is being generated it's totally perfect. 05:17.920 --> 05:19.600 We run actually no. 05:19.640 --> 05:22.320 Again the image creation process. 05:22.760 --> 05:26.600 So all right, after we generate the image it passes through the if node. 05:27.240 --> 05:30.520 Then what we do we just publish the content on LinkedIn. 05:30.960 --> 05:35.840 And at the end we just check the status to publish and we save image URL. 05:36.040 --> 05:37.560 So this is the entire automation. 05:37.560 --> 05:39.720 And now look on these three parts. 05:39.720 --> 05:40.840 This is the content creation. 05:40.840 --> 05:42.240 We've got ten ideas. 05:42.720 --> 05:43.800 Then what we do. 05:43.840 --> 05:45.360 We choose one keyword. 05:45.360 --> 05:49.000 So from ten ideas we choose only the best one. 05:49.120 --> 05:56.120 Um actually I can say idea for the content and then even we create the best image possible. 05:56.160 --> 06:01.000 Because, you know, sometimes we may have some automations about LinkedIn, how to generate posts, 06:01.000 --> 06:02.200 how to do all of this stuff. 06:02.240 --> 06:04.120 However, it's not that complex. 06:04.440 --> 06:08.400 Uh, but with this automation, I need to I need to say I spend a lot of time. 06:08.400 --> 06:12.920 I had over 100 errors and I came with this entire project. 06:12.920 --> 06:13.920 That is perfect. 06:13.920 --> 06:16.400 I'm using it for my very own LinkedIn. 06:16.560 --> 06:20.440 And also I provided for you alternatives for this specific case. 06:20.440 --> 06:24.120 So for this automation I will show everything in this video obviously. 06:24.160 --> 06:27.320 However what you have here you use LinkedIn note. 06:27.320 --> 06:30.200 So you publish the content to your business profile. 06:30.200 --> 06:34.800 And this note actually publishes your content to your personal profile. 06:35.040 --> 06:41.400 Also in this video it's very important I will be showing you how to publish your content to your LinkedIn 06:41.400 --> 06:45.040 profile, which is personal and your business profile. 06:45.400 --> 06:49.280 I know many people struggle with this specific case. 06:49.280 --> 06:52.050 So yeah, again, watch this video to the end. 06:52.530 --> 06:59.170 But obviously the most important fact is that how this automation manages to create our content on LinkedIn. 06:59.370 --> 07:02.850 So this is the post that our automation created. 07:02.890 --> 07:06.410 What we have inside we've got perfect description. 07:06.450 --> 07:10.250 Artificial intelligence is reshaping the way we handle complex tasks. 07:10.290 --> 07:14.010 And agents are at the forefront of this revolution. 07:14.210 --> 07:16.450 We've got here some statistics. 07:16.490 --> 07:23.450 According to Gartner, by 2025, 50% of businesses will have agents incorporated into their operations 07:23.450 --> 07:24.770 to some extent. 07:24.810 --> 07:26.530 So this is the end of 2025. 07:26.570 --> 07:33.010 Remember, these agents are not just performers of routine tasks, but are becoming decision makers, 07:33.010 --> 07:35.890 providing insights that drive business growth. 07:36.210 --> 07:39.170 Even like look on this quality of this image. 07:39.330 --> 07:44.610 So for this case, we are using this specific loop to indicate if image is perfect. 07:44.610 --> 07:51.500 And yet we came with the best image possible for the specific case we've got perfect text not truncated 07:51.540 --> 07:53.180 and quality is great. 07:53.460 --> 07:57.220 And another case actually also we've got the hashtags have another case. 07:57.260 --> 07:58.700 And this is my business profile. 07:58.700 --> 07:58.980 All right. 07:58.980 --> 08:00.340 This is my business profile. 08:00.540 --> 08:02.460 But this is my personal profile. 08:02.460 --> 08:04.060 And also I've got some posts. 08:04.060 --> 08:05.700 So this is another format of the post. 08:05.740 --> 08:07.940 However still we've got our image. 08:07.940 --> 08:09.860 We've got specific facts. 08:09.860 --> 08:13.380 So here efficiency boosts over 30%. 08:13.580 --> 08:19.860 Even yesterday I were testing this automation and then some person actually I don't have a lot of reach 08:19.900 --> 08:20.780 on LinkedIn. 08:20.820 --> 08:23.580 However, some person commented like this post. 08:23.580 --> 08:25.380 So we've got to know this post here. 08:25.740 --> 08:27.860 And the image and there we've got a discussion. 08:27.860 --> 08:32.620 So the numbers you shared are wild, but honestly think they are still lowballing IT. 08:32.620 --> 08:37.500 Companies dragging their feet on a integration are gonna get left behind fast. 08:37.500 --> 08:39.780 So even you know, we've got a lot of impressions. 08:39.940 --> 08:45.980 Um, and this content is highly professional to post on LinkedIn right away, even to show you that 08:45.980 --> 08:49.660 the posts our automation can create are highly valuable. 08:49.940 --> 08:51.140 I've got two examples. 08:51.140 --> 08:53.020 So firstly we've got Gary Vaynerchuk. 08:53.180 --> 08:57.900 And for instance like this image can be generated by ChatGPT image generator. 08:58.020 --> 09:03.420 We've got over 2000 likes here approximately 300 comments. 09:03.420 --> 09:05.420 And this is another another example. 09:05.420 --> 09:09.100 So we've got Ruben Hassett and like look on the structure. 09:09.140 --> 09:13.500 Like our automation created similar structure of the content. 09:13.740 --> 09:23.700 And here also we've got an image generated by AI and over 3000 likes 900 comments 300 reposts. 09:24.300 --> 09:26.500 But all right really long introduction. 09:26.500 --> 09:31.020 Nevertheless our video for this automation will be very long either. 09:31.260 --> 09:32.980 So let's don't waste more time. 09:32.980 --> 09:35.380 And let's start with actually first steps. 09:35.540 --> 09:39.980 So I can go ahead to my Nan and create the workflow. 09:40.900 --> 09:42.780 And here we'll be starting. 09:42.940 --> 09:46.900 And so the original version will have the trigger which is action chat message. 09:47.420 --> 09:50.310 So we pick that trigger and that's perfect. 09:50.310 --> 09:52.150 Insight will provide some keywords. 09:52.470 --> 09:57.630 Also remember in the resources of this material you've got all of the instructions. 09:57.750 --> 09:59.990 Um yeah I just created for you. 10:00.230 --> 10:05.670 So for instance you can copy all of the system messages prompts from our from our agents. 10:05.670 --> 10:08.350 You see how to set up your HTTP requests. 10:08.550 --> 10:10.230 So this is pretty long file. 10:10.270 --> 10:13.830 However, I put a lot of attention, um, to include everything here. 10:13.830 --> 10:19.310 So again you've got all of the instructions and we'll be using it for the case of this material for 10:19.310 --> 10:20.110 this video. 10:20.510 --> 10:22.190 And because we've got a lot of steps. 10:22.230 --> 10:22.630 All right. 10:22.630 --> 10:26.350 As you can see here, we've got a lot of agents a lot of HTTP requests. 10:26.350 --> 10:29.390 So for sure it's really valuable. 10:29.430 --> 10:32.990 Also we can download the JSON file and the resources to remember about it. 10:33.230 --> 10:35.030 But for now let's move on. 10:35.310 --> 10:38.750 Um, after we've got our chat we've got our HTTP request. 10:39.190 --> 10:44.110 So simply, um, if I go ahead to our file we can scroll up. 10:44.990 --> 10:50.920 And it's really unusual HTTP requests, I need to say, because right there we've got only two specific 10:50.920 --> 10:51.920 fields set up. 10:51.920 --> 10:54.360 So method which is get and the URL. 10:54.520 --> 10:56.600 So right now let's just copy this URL. 10:57.400 --> 11:00.200 Um pretty simply let's move on here. 11:00.640 --> 11:04.840 Just paste this URL method which is get and we can execute previous nodes. 11:04.840 --> 11:08.600 So for now I can open the chat and type A agents. 11:09.800 --> 11:10.160 All right. 11:10.160 --> 11:10.840 That's great. 11:11.160 --> 11:17.560 And then what we have after we do this we've got our data however in XML format. 11:18.000 --> 11:20.240 So these are the searches from the internet. 11:20.240 --> 11:23.440 So simply we provided the keyword which is a agent. 11:23.440 --> 11:30.440 And then it searched for the most relevant actually related and popular keywords right now on the internet. 11:30.920 --> 11:35.800 So it works by this way, it's great because we are using main Google search tool. 11:36.000 --> 11:36.720 That's great. 11:36.760 --> 11:39.480 Um, and also we provide here chat input at the end. 11:39.520 --> 11:41.600 So this is us our search result. 11:42.640 --> 11:48.760 And then we need to kind of And put it so this HTML format into JSON. 11:49.080 --> 11:52.720 So I can pick actually HTML node. 11:53.760 --> 11:56.400 This is not HTML however XML. 11:56.440 --> 11:57.240 I'm sorry. 11:57.560 --> 12:01.760 So in general what we do, um, we've got the property name which is data. 12:01.760 --> 12:03.000 We execute the step. 12:03.440 --> 12:05.280 So after we do this there's a simple note. 12:05.280 --> 12:07.640 We don't need to provide anything here. 12:07.640 --> 12:08.480 Just set it up. 12:09.000 --> 12:13.600 And what we get we've got our one item with our all of the keywords. 12:13.600 --> 12:15.680 So let's see how many we've got of them. 12:15.880 --> 12:17.360 It counts from zero. 12:17.360 --> 12:18.320 So we have ten. 12:18.640 --> 12:19.480 That's perfect. 12:19.800 --> 12:22.960 And in general we need to do some specific stuff. 12:23.880 --> 12:27.840 So I want to have ten different items. 12:28.320 --> 12:29.320 It's pretty important. 12:29.320 --> 12:35.120 We need to have ten different items to then put them into our loop loop part. 12:35.160 --> 12:35.600 Okay. 12:35.880 --> 12:38.840 And because we'll be creating for each of them content. 12:39.280 --> 12:47.290 So I can pick the node which is split out so we can turn a list inside items into separate items. 12:47.690 --> 12:48.410 That's great. 12:48.810 --> 12:53.410 And for this specific case, we just drag and drop our object variable. 12:53.410 --> 12:54.490 So top level. 12:54.770 --> 12:56.490 And then what it should do. 12:56.530 --> 12:57.850 Actually no no top level. 12:57.890 --> 13:01.530 However we just pick complete suggestion. 13:02.970 --> 13:07.650 So when we execute this step we should get our suggestion and data. 13:07.770 --> 13:10.930 So we've got a agents and then we've got ten items. 13:10.930 --> 13:12.410 Let me let me show you. 13:12.450 --> 13:15.490 We've got first keyword which is agent. 13:15.530 --> 13:15.850 Next. 13:15.850 --> 13:19.490 We've got agents explained a agents versus agent. 13:19.690 --> 13:21.810 I, I can say it's highly popular. 13:21.850 --> 13:22.890 Popular right now. 13:23.050 --> 13:24.130 So agent I. 13:24.450 --> 13:29.930 And we've got even agents course directory crypto Reddit and action. 13:30.210 --> 13:31.810 That's very very cool. 13:32.210 --> 13:38.810 And remember afterwards we'll choose from these ten items one item to create the content for it. 13:38.850 --> 13:43.900 So if it gives you some specific keyword that you don't think will be great. 13:43.900 --> 13:47.100 Let's say maybe it's agent stocks. 13:47.140 --> 13:47.860 All right. 13:47.900 --> 13:48.540 Don't worry. 13:48.580 --> 13:51.340 Our agent will handle the entire problem later. 13:52.140 --> 13:52.820 That's cool. 13:53.180 --> 13:53.980 Let's move on. 13:53.980 --> 13:55.580 And now what we need to do. 13:55.620 --> 13:57.340 I want to provide the edit field. 13:57.580 --> 13:59.060 So instead of the data. 13:59.220 --> 14:00.420 Because let me show you. 14:00.460 --> 14:03.500 We've got here, um, the data and the variable. 14:03.500 --> 14:07.380 So the name of it I want to actually, you know, name it as keywords. 14:07.540 --> 14:14.220 So provide the name keywords and then just pick our variable which is data and the value. 14:15.100 --> 14:16.580 And now execute this step. 14:16.780 --> 14:21.020 So we've got the items and keywords you know for each of them. 14:21.260 --> 14:21.900 Perfect. 14:22.860 --> 14:23.820 It was pretty fast. 14:23.860 --> 14:26.540 I need to say so we've got our inputs right here. 14:26.940 --> 14:29.460 And the next step will be providing our loop. 14:30.340 --> 14:32.660 So let's move on and provide our loop. 14:33.220 --> 14:34.420 Loop over items. 14:34.620 --> 14:36.900 And batch size is one. 14:36.940 --> 14:37.420 All right. 14:37.420 --> 14:43.950 So it indicates how many items you would like to return with every loop iteration. 14:44.230 --> 14:45.470 Even you can read it here. 14:45.510 --> 14:48.070 Probably the number of items to return with each call. 14:48.310 --> 14:52.630 Um, obviously we have one, and mostly it's one, so it works by this way. 14:53.070 --> 14:58.270 And inside the loop, what we'll have, we'll have our free agents. 14:58.990 --> 15:04.270 Um, the first one will generate for us the post content, the second the title and the third image 15:04.270 --> 15:05.990 prompt image prompt. 15:05.990 --> 15:09.350 And actually the fourth step is saving the data inside Google Sheets. 15:09.790 --> 15:11.270 So let me show you what we do. 15:11.870 --> 15:14.030 We provide our node which is a agent. 15:14.190 --> 15:16.830 After we do this we pick define below. 15:16.830 --> 15:18.150 So source for prompt. 15:18.710 --> 15:21.830 Uh so we provide a prompt um inside our file. 15:21.830 --> 15:22.990 Let's see what we have. 15:22.990 --> 15:26.070 So let me guide you through uh maybe firstly let's provide the prompt. 15:26.070 --> 15:32.350 So we've got the post keyword uh and then um even actually we can set it up. 15:32.350 --> 15:36.990 Um, let's execute the previous nodes so we can execute this node. 15:36.990 --> 15:37.390 All right. 15:37.390 --> 15:38.830 To, to provide the data. 15:39.430 --> 15:44.750 So we've got in the prompt post keyword, we choose here the keyword from loop. 15:45.030 --> 15:50.670 So simply I dragged and dropped this specific um the specific variable. 15:50.990 --> 15:57.870 So with every loop iteration we take other keyword and we feed it to our agent. 15:58.030 --> 16:04.230 And this agent is to create LinkedIn uh post description. 16:06.590 --> 16:07.470 That's perfect. 16:07.790 --> 16:09.910 Um, so the prompt is pretty simple. 16:09.910 --> 16:13.590 I like to every time like structure it by by by this way. 16:13.750 --> 16:18.790 So provide in the prompt all of my variables and in the system message like background, you know, 16:18.830 --> 16:22.310 instructions for the model to behave in a particular way. 16:22.830 --> 16:25.150 So we can add system message. 16:25.390 --> 16:30.430 And here um, I will pick the system message and we'll analyze it in a while. 16:30.670 --> 16:31.150 Okay. 16:31.950 --> 16:33.590 Um, let me go. 16:33.870 --> 16:34.590 Here. 16:34.630 --> 16:35.950 Pick expression. 16:36.510 --> 16:40.160 Um, now open it in full tab and see what we have. 16:40.600 --> 16:46.640 Create high impact LinkedIn posts that are professional, insightful, and designed to grow our LinkedIn 16:46.640 --> 16:47.360 presence. 16:47.560 --> 16:51.080 Each post is built around a specific keyword provided by the user. 16:51.320 --> 16:54.160 When you receive a keyword, follow this process. 16:54.880 --> 17:01.160 Read the keyword as the core focus of the post built around it using relevant facts, statistics, case 17:01.160 --> 17:02.960 studies, or market trends. 17:03.000 --> 17:07.200 Make sure the post delivers clear value to a professional audience. 17:07.600 --> 17:08.760 Write the post. 17:08.760 --> 17:13.520 So also I like to highlight the sections of the system message. 17:13.680 --> 17:14.240 By this way. 17:14.240 --> 17:18.560 So providing these two signs and again just providing these two signs. 17:19.000 --> 17:22.440 So inside how it works we've got different points. 17:22.440 --> 17:25.320 So the first one is research contextualize. 17:25.320 --> 17:26.480 We read it already. 17:26.480 --> 17:28.520 And the second one is write the post. 17:28.680 --> 17:32.760 So we've got bagging with a strong hook to grab attention immediately. 17:32.800 --> 17:36.240 Maintain a confident professional tone throughout. 17:36.280 --> 17:39.770 Use short paragraphs and logical flow to ensure readability. 17:39.810 --> 17:42.370 Deliver education or actionable insights. 17:42.410 --> 17:42.730 Teach. 17:42.770 --> 17:43.890 Inspire or provoke. 17:43.930 --> 17:45.010 Provoke thoughts. 17:45.370 --> 17:46.570 So also you need to remember. 17:46.610 --> 17:54.530 Actually, I customized these instructions based on the best LinkedIn posts out there from other people. 17:54.570 --> 18:01.130 Actually, um, you know, I based on the best content on the proven strategies, how the content should 18:01.130 --> 18:01.770 be structured. 18:02.530 --> 18:05.810 So also this instructor instructions contain that. 18:06.290 --> 18:09.490 That's highly great because, you know, not even you've got the automation. 18:09.490 --> 18:13.970 However the entire strategy, how the posts, um should look like. 18:14.330 --> 18:17.970 So inside I included everything inside this specific part. 18:18.010 --> 18:23.970 So write the post for for example, you've got also use emojis only if they enhance clarity or tone. 18:24.930 --> 18:30.730 Add a few smart keyword specific hashtags to improve reach and visibility, even with hashtags. 18:30.770 --> 18:36.210 As you could have noticed in our LinkedIn post, I showed you previously output roles. 18:36.210 --> 18:39.690 So for the output roles only output the final LinkedIn post. 18:39.850 --> 18:42.290 Do not explain the post or describe the steps taken. 18:42.330 --> 18:46.570 Avoid quotation marks unless part of a statement. 18:46.730 --> 18:49.370 Keep formatting natural and LinkedIn appropriate. 18:49.410 --> 18:51.370 No markdowns or styling notes. 18:51.610 --> 18:56.010 Don't provide line breaks or new lines, just give plain text. 18:56.050 --> 19:00.450 Don't use the specific sign and this sentence is really crucial. 19:00.810 --> 19:06.010 I had a lot of errors previously without the sentence, without just providing it. 19:06.570 --> 19:13.170 So what it does and for what reason this is if we go ahead to our automation that we'll be creating 19:13.210 --> 19:16.730 step by step, we've got here HTTP request. 19:17.170 --> 19:20.570 And the catch is inside our JSON code here. 19:20.850 --> 19:28.010 When we have our text we need to have something I need to say without any, you know, like specific 19:28.370 --> 19:33.370 signs or even like let's say line breaks right here. 19:33.530 --> 19:36.060 So it's compatible with JSON format. 19:36.820 --> 19:40.340 So for this purpose, that's why we've got this specific sentence. 19:40.900 --> 19:45.620 However, I need to say that you've got other way of connecting LinkedIn. 19:45.820 --> 19:49.860 So here in general you don't need to like be very restrictive. 19:49.860 --> 19:53.580 You can provide the content format that let's say you want to provide the breaks. 19:53.620 --> 19:57.180 I don't know, maybe some numbers like from new lines and so on. 19:57.220 --> 19:59.300 So you've got two methods how you do this. 19:59.340 --> 20:02.620 However, I wanted to explain you why we've got this specific sentence. 20:02.780 --> 20:07.100 So by this way again we've got the plain text without any specific parts. 20:07.340 --> 20:09.180 However, this text is highly professional. 20:09.220 --> 20:11.500 Again, still, it's very, very good. 20:11.900 --> 20:14.060 Also remember you've got the alternative. 20:14.060 --> 20:20.660 So you can I will show you later how you can switch for example this part with some parts inside and 20:20.660 --> 20:23.380 just use the LinkedIn note inside. 20:24.180 --> 20:25.980 However let's let's move on to the video. 20:26.420 --> 20:27.860 So yeah it works by this way. 20:27.860 --> 20:29.980 This is the instruction for the first agent. 20:29.980 --> 20:31.780 We've got also sample use case. 20:31.780 --> 20:35.510 So let's say we provide the keyword and then, um, like the instructions. 20:35.510 --> 20:39.070 So you create a polished LinkedIn post with a sharp hook and a lot of more. 20:39.350 --> 20:39.990 Perfect. 20:40.230 --> 20:44.390 After we run it, um, obviously, first we need to pick the chat model. 20:44.430 --> 20:45.590 This is OpenAI. 20:46.430 --> 20:51.190 OpenAI, GPT 4.1 mini is enough really enough? 20:51.990 --> 20:53.030 So what do we do next? 20:53.350 --> 20:57.070 Uh, we run this agent and we see what happens, actually. 20:58.110 --> 21:00.630 So we run this agent and we've got a. 21:00.630 --> 21:07.830 Agents are transforming how businesses operate, offering unprecedented scalability and efficiency. 21:08.030 --> 21:10.430 And now we need to check for for the format. 21:10.430 --> 21:11.110 So that's perfect. 21:11.110 --> 21:14.910 We've got plain text with hashtags which are which are totally fine. 21:15.270 --> 21:16.510 So it's pretty cool. 21:16.550 --> 21:17.150 All right. 21:17.790 --> 21:21.790 The next agent we'll have will be our, um. 21:21.830 --> 21:26.270 I'm sorry, will be our agent for generating the title. 21:26.310 --> 21:27.870 And now we can do the following trick. 21:27.870 --> 21:31.750 So let's click on this agent and click control. 21:31.830 --> 21:36.150 Click on this note and now click Ctrl D and again Ctrl D. 21:37.430 --> 21:38.510 What do we do by this? 21:38.550 --> 21:43.550 We just um yeah we just connect our different agents. 21:43.790 --> 21:46.950 Um, actually we duplicate them and we connect them to our loop. 21:47.710 --> 21:49.190 So let's do it by this way. 21:50.430 --> 21:51.230 That's perfect. 21:51.710 --> 21:54.750 And for this agent will be generating the titles. 21:55.150 --> 21:57.870 If we go back to our instructions. 21:58.390 --> 22:03.630 So the file you can download in the resources of this material, you will see we've got the prompt which 22:03.630 --> 22:06.030 is only we provide here the description. 22:06.350 --> 22:10.990 So we can actually copy it and then just paste it here. 22:11.030 --> 22:12.030 Let's see what we have. 22:12.350 --> 22:17.230 So it doesn't work because probably we've got a different name of the previous agent. 22:17.230 --> 22:20.750 So this is LinkedIn create LinkedIn post description. 22:20.750 --> 22:27.950 And let's see what we have even for for that I can just, you know copy it create LinkedIn post description. 22:27.990 --> 22:29.230 Let me see what is happening. 22:29.390 --> 22:31.240 So even actually what we can do. 22:31.240 --> 22:37.200 We can provide the output from this specific agent and see all right we've got JSON output. 22:37.240 --> 22:40.720 However for now what we can do we can click just delete it. 22:40.760 --> 22:45.360 And now for instance we can execute the steps to see if that works. 22:46.520 --> 22:49.600 So now for an example to solve the problem what we can do. 22:49.600 --> 22:52.520 We can take this output and see what's different. 22:52.560 --> 22:55.120 Okay so I know we've got only JSON output. 22:55.120 --> 22:58.320 So we don't have like this specific you know variable right here. 22:58.520 --> 22:59.440 So it's pretty enough. 22:59.440 --> 23:01.920 We've got our here JSON output. 23:01.920 --> 23:08.000 So we fit our LinkedIn title agent with our description we created. 23:08.000 --> 23:08.800 That's perfect. 23:09.200 --> 23:12.880 So also it matches the description it creates for it the title. 23:13.200 --> 23:14.520 But further instructions. 23:14.720 --> 23:15.840 Let me show you what we have. 23:16.200 --> 23:17.080 Instructions. 23:17.080 --> 23:19.240 Instructions are pretty simple. 23:19.800 --> 23:23.120 Um, let me paste it here actually. 23:23.120 --> 23:23.360 Yeah. 23:23.400 --> 23:24.520 Let me paste it here. 23:25.440 --> 23:31.730 So your job is to create a clear, highly engaging title for the LinkedIn post based on on its description. 23:32.570 --> 23:39.050 Don't use word title at the beginning, just provide plain title at one emoji at the end of the title. 23:39.050 --> 23:39.650 That's great. 23:39.650 --> 23:40.370 That's enough. 23:40.570 --> 23:47.530 We use only GPT 4.1 mini model, so the same model and we do the following stuff. 23:47.570 --> 23:54.530 Remember, every time you run some steps inside loop, you need to run the entire loop itself. 23:54.730 --> 24:01.970 So let's say if we'll be creating our image, our agent to create image prompt also will be need needed 24:01.970 --> 24:04.690 to run the two previous agents. 24:05.130 --> 24:11.490 Uh, it's pretty annoying in terms of just, you know, testing the automation and doing all the stuff. 24:11.530 --> 24:18.290 However, later I will have for you specific solution because imagine if you have ten items to create 24:18.290 --> 24:19.050 in the loop. 24:19.690 --> 24:26.370 Um, and then you've got other notes after the loop, you need to wait for ten items to be created. 24:26.410 --> 24:28.660 You spend credits and so on. 24:28.700 --> 24:32.740 Actually, the credits, the credits spent on this specific loop won't be high. 24:32.780 --> 24:34.100 We are using mini model. 24:34.100 --> 24:36.740 We are generating only the text so it won't be high. 24:36.900 --> 24:43.020 However, I will show you, um, actually you know other way how you can, um, make the process faster. 24:44.020 --> 24:55.860 But for now, what we can do, let's go ahead and rename it as create LinkedIn Post title. 24:56.340 --> 24:57.020 Great. 24:58.300 --> 25:08.580 Then, uh, we just create our image prompt, create image prompt a agent a agent. 25:08.580 --> 25:09.260 That's great. 25:09.740 --> 25:12.700 Now let's move on to our file and see what we have here. 25:12.940 --> 25:16.340 Again let's pick our prompt very simply. 25:17.060 --> 25:19.900 Um, and this is the message I will explain everything. 25:20.060 --> 25:22.340 So we've got our free agents for each. 25:22.380 --> 25:25.380 We've got different, um, obviously different instructions. 25:25.380 --> 25:26.740 So again we've got the purpose. 25:26.860 --> 25:33.660 We've got goals, visual criteria, output requirements, design style, style elements. 25:34.100 --> 25:36.300 And here prompt format example. 25:36.300 --> 25:37.660 So let me preview it. 25:37.700 --> 25:42.900 You are an AI agent designed to convert LinkedIn posts into visuals, prompts, descriptions. 25:42.900 --> 25:47.460 These prompts guide the creation of compelling marketing graphics that visually enhance the written 25:47.460 --> 25:51.100 message and align with professional branding standards. 25:51.140 --> 25:51.780 Goals. 25:51.820 --> 25:57.100 Analyze the content of the LinkedIn post and identify the core message, insight, or idea. 25:57.220 --> 26:02.540 Craft a visual prompt that represents the message in a striking and brand consistent way. 26:02.540 --> 26:08.220 Ensure the prompt is ideal for generating a professional marketing style graphic, not a literal or 26:08.260 --> 26:09.580 hyper realistic image. 26:09.780 --> 26:13.660 So this agent actually makes sure our image is the best. 26:13.660 --> 26:19.180 I put a lot of attention into preparing all of these prompts, like system messages for example. 26:19.180 --> 26:19.740 For this one. 26:19.740 --> 26:21.580 Also, I had to put a lot of effort. 26:21.580 --> 26:27.510 So what we have your graphic prompt must visually support or represent the key idea for the post. 26:27.550 --> 26:29.670 Be suitable for a modern LinkedIn post. 26:29.710 --> 26:30.070 Clean. 26:30.070 --> 26:30.630 Professional. 26:30.630 --> 26:31.190 Polished. 26:31.510 --> 26:35.950 Reflect a current design aesthetic and we've got output requirements. 26:36.110 --> 26:40.510 So what we should receive for us or even design style elements. 26:40.830 --> 26:41.790 There is the point. 26:41.830 --> 26:46.350 Remember it's very important you can change these A agents. 26:46.350 --> 26:49.390 So after you generate this entire automation. 26:49.430 --> 26:54.630 Firstly obviously like create it or even like you know I recommend you to watch this video to the end 26:54.670 --> 26:59.910 because again after you watch it you will see like a lot of different steps, you will be much experienced 26:59.910 --> 27:00.870 in Nadine. 27:00.910 --> 27:06.830 However, if you wish you could just take the JSON template, just, you know, import it here and take 27:06.830 --> 27:07.590 your credentials. 27:07.590 --> 27:09.350 Just connect and see if that works. 27:09.390 --> 27:15.670 And later what I mean you can change the agents to, to just create for you something else. 27:15.790 --> 27:21.910 So let's say you want to have your content for healthcare, maybe for football for some, I don't know, 27:21.910 --> 27:25.640 maybe news for Other specific purposes. 27:25.680 --> 27:27.440 Also, we can provide other instructions. 27:27.440 --> 27:28.680 You can improve them. 27:28.680 --> 27:32.120 So the point is for this automation to run properly. 27:32.120 --> 27:34.480 And then um, yeah, I created everything for you. 27:34.480 --> 27:38.560 You've got the JSON template and then you can customize it for your specific needs. 27:38.600 --> 27:39.800 Hope you appreciate it. 27:39.800 --> 27:42.320 But let's move on to design style elements. 27:42.360 --> 27:45.480 Flat illustrations, bold or minimal typography elements. 27:45.480 --> 27:49.160 Infographic components, modern abstract shapes or gradients. 27:49.200 --> 27:50.000 Metaphors. 27:50.040 --> 27:51.320 Layout suggestions. 27:51.320 --> 27:52.680 So we've got everything here. 27:52.960 --> 27:55.320 After we do this, we execute this step. 27:55.560 --> 27:57.000 We get our image prompt. 27:57.000 --> 28:00.200 So again it runs through the entire, um, loop. 28:00.760 --> 28:06.920 So we have it modern flat style illustration on a sleek a robot interaction with digital holograms of 28:06.920 --> 28:11.880 business charts and innovation icons like light bulbs and gears. 28:12.320 --> 28:13.200 Perfect. 28:13.840 --> 28:18.360 Um, then what we can do, uh, we can open our Google Sheets. 28:19.400 --> 28:22.520 So I would like to open the row in sheet. 28:22.520 --> 28:24.680 And now let me show you what I prepared for you. 28:25.080 --> 28:30.920 So actually we've got our template inside Google Sheets that contains the keyword post title, post 28:30.920 --> 28:33.240 description, post image prompt. 28:33.560 --> 28:36.000 Then we've got the status and image URL. 28:36.480 --> 28:38.040 And for this specific purpose. 28:38.040 --> 28:43.760 So for this Google Sheets we save only a few different, uh, you know, information. 28:44.360 --> 28:48.720 Um, the first one, uh, which is very important is our keyword. 28:49.080 --> 28:51.840 So we take our keyword from edit fields. 28:51.840 --> 28:55.360 So we just fit our Google Sheets with this specific data. 28:55.360 --> 28:59.200 So edit fields and again it changes with every loop iteration. 28:59.200 --> 29:03.360 So it provides you know the relevant keyword for the post title. 29:03.600 --> 29:07.760 Uh we just provide the post title here for post description. 29:07.760 --> 29:08.640 We just do this. 29:08.680 --> 29:09.720 We provide it here. 29:10.240 --> 29:11.320 Image prompt. 29:11.360 --> 29:12.240 Let's move on. 29:12.480 --> 29:13.640 We've got the output. 29:14.120 --> 29:22.170 And for the status we um, actually mark it as not published because if we move on to our Google Sheets 29:22.170 --> 29:22.850 for the status. 29:22.850 --> 29:25.490 We've got two fields not published and published. 29:25.850 --> 29:31.010 And now there is the important part actually for what do we save the data here inside Google Sheets? 29:31.210 --> 29:37.170 There is one main reason because actually we want to store it for each loop iteration. 29:37.170 --> 29:41.890 So every time, uh, like our first let's say first iteration runs. 29:42.090 --> 29:43.530 So this is our first iteration. 29:43.530 --> 29:44.610 It saves the data. 29:44.610 --> 29:45.970 Then we've got second iteration. 29:45.970 --> 29:49.370 It saves the data for the next, you know, like the next content. 29:49.370 --> 29:52.890 So in general we store all of the content inside Google Sheets. 29:53.530 --> 30:00.290 And the next part is actually after we choose specific keyword and specific content we would like to 30:00.330 --> 30:01.810 use for LinkedIn post. 30:01.930 --> 30:06.770 Then from Google Sheets what we do we take the data from here okay. 30:06.930 --> 30:08.610 So firstly we store it. 30:08.770 --> 30:12.730 We store all of the approximately ten different content ideas. 30:12.850 --> 30:18.570 And then after we choose specific keywords and content we want to get, we want to create the post for 30:18.570 --> 30:19.050 it. 30:19.090 --> 30:21.660 We just take the data, all of the data from here. 30:21.940 --> 30:23.460 So it's pretty important. 30:23.460 --> 30:25.180 And yeah, let's move on here. 30:25.380 --> 30:29.340 And now what we can do we can execute this step. 30:29.500 --> 30:33.220 However, for now let's connect our Google Sheets with our loop. 30:33.580 --> 30:35.140 So we do it by this way. 30:35.180 --> 30:36.780 Also let me put it here. 30:37.180 --> 30:38.700 So let's run it. 30:38.860 --> 30:40.180 Let's see how it works. 30:40.940 --> 30:44.060 So for now nice. 30:44.060 --> 30:46.260 We can see it works great. 30:46.940 --> 30:50.620 And in general right now um let's see. 30:50.660 --> 30:56.180 We've got here the schema post title, post description, post image prompt and status not published. 30:57.340 --> 30:59.260 And there is important fact. 30:59.620 --> 31:02.300 Now this loop should run ten times. 31:02.500 --> 31:06.420 So if I open the chart I type a automation. 31:07.300 --> 31:09.220 I need to see if that works. 31:09.220 --> 31:15.620 So what we have actually here make sure the last executed node outputs the content to display here. 31:16.380 --> 31:17.620 Let's see what we have. 31:18.180 --> 31:19.700 Um actually let's run it again. 31:20.500 --> 31:21.460 Agents. 31:22.220 --> 31:28.620 All right, so now it runs and we can see it generates first first content. 31:28.620 --> 31:29.180 All right. 31:29.180 --> 31:30.180 So first keyword. 31:30.180 --> 31:30.900 Let's see. 31:31.020 --> 31:32.100 Um, let's move on. 31:32.420 --> 31:34.420 We've got our agents. 31:34.780 --> 31:35.500 Agents. 31:35.660 --> 31:36.940 Um, explained. 31:38.540 --> 31:43.420 Um, let me even preview actually this specific stuff A agents. 31:43.460 --> 31:44.180 Great. 31:46.340 --> 31:47.140 All right. 31:47.140 --> 31:50.700 So as you can notice right here, it produces for me. 31:51.020 --> 31:51.460 All right. 31:51.500 --> 31:52.700 Yeah I know what happens. 31:52.740 --> 31:59.060 Okay, I didn't see I, I was confused, but now it produces for me all of the keywords along with the 31:59.060 --> 32:01.700 content with the status which is not published. 32:01.900 --> 32:07.060 And now it runs until it generates approximately ten different content ideas. 32:07.380 --> 32:09.100 So our automation works. 32:09.100 --> 32:11.020 We've got post title for each of them. 32:11.020 --> 32:12.380 That's truly amazing. 32:12.700 --> 32:15.340 Um, so here this is the entire description. 32:15.380 --> 32:17.950 We've got agents Reddit crypto directory. 32:18.310 --> 32:21.870 Okay, so it runs, it runs, it runs. 32:23.350 --> 32:25.390 And it's pretty professional actually. 32:25.390 --> 32:29.070 You know, you've got ten content ideas from where from which you can choose. 32:29.430 --> 32:31.230 Um, so that's great. 32:31.550 --> 32:33.190 And then it's cool. 32:33.190 --> 32:37.750 So inside our loop we've got our loop and path and done path. 32:38.230 --> 32:41.190 So after our content is generated. 32:41.190 --> 32:48.430 So we've got our IDs inside, um, Google Sheets, we want to process with the path which is done. 32:48.470 --> 32:57.030 So then what we want to do firstly we want to use aggregate node to actually, you know, create one 32:57.030 --> 33:02.430 item like gather all of the information and one item in one field. 33:02.790 --> 33:05.950 For this case I will be using split out node. 33:06.150 --> 33:09.110 I will drag the suggestion inside here. 33:09.270 --> 33:09.510 Um. 33:09.510 --> 33:18.040 However, firstly I need to change um the aggregate um action type so all item data into a single list. 33:18.600 --> 33:20.520 Now let's change the expression. 33:20.920 --> 33:23.560 And then just provide a suggestion. 33:24.480 --> 33:26.040 So here we've got a suggestion. 33:26.360 --> 33:30.400 And then we should get our result so we can execute the step. 33:30.960 --> 33:35.160 So we've got as you can notice inside one item we have all of the data. 33:35.160 --> 33:38.720 So let's say here we've got the first keyword content for it. 33:38.720 --> 33:44.360 The second keyword content for it, the third keyword content for it, and so on and so on up to ten 33:44.360 --> 33:45.080 different keywords. 33:45.240 --> 33:47.840 So in general, again we've got one item. 33:48.320 --> 33:54.320 So then we can use it for our next step which is edit fields. 33:55.200 --> 33:56.560 We will not take it. 33:56.560 --> 33:58.760 So we just drag and drop. 33:58.760 --> 34:00.360 Let me let me click here. 34:00.360 --> 34:02.880 We just drag and drop this specific field. 34:02.880 --> 34:09.760 So this variable we put it here and then we just specify actually no this is the name. 34:09.960 --> 34:13.880 So we can specify as the content and for the value we put it here. 34:14.400 --> 34:17.170 So what we do, we want to make it a string. 34:17.290 --> 34:21.290 So put all of that data, put all of that data into one string. 34:21.330 --> 34:27.690 Later on we can use our A agent and we can feed this a agent with this specific string. 34:28.050 --> 34:33.170 So the point is actually it will look terrible obviously because we've got one string. 34:33.290 --> 34:36.090 We've got one, you know, like one chunk of the text. 34:36.090 --> 34:37.450 It's looking really messy. 34:37.490 --> 34:38.250 Terrible. 34:38.290 --> 34:42.010 Ever remember for our agent sometimes it doesn't matter. 34:42.050 --> 34:45.930 Like it matters less than for us as humans. 34:45.930 --> 34:52.090 We are very, you know, visual persons like we are visual creatures, not persons, visual creatures. 34:52.330 --> 34:55.530 But again, for our agent, it's totally fine. 34:55.570 --> 34:58.730 Like it will retrieve the most important information from here. 34:59.170 --> 35:02.970 So, uh, when I said that, like, you can, um. 35:03.010 --> 35:03.730 Yeah, you can guess. 35:03.730 --> 35:09.850 The next step will be our agent with this agent will be taking one keyword. 35:10.610 --> 35:11.330 And this is. 35:11.330 --> 35:18.770 This will be the most sophisticated agent from this automation because the task, his task will be pretty 35:18.770 --> 35:19.410 important. 35:20.090 --> 35:22.090 Let's move on here and see what we have. 35:22.450 --> 35:25.130 So this is choose one keyword a agent. 35:25.450 --> 35:29.850 We've got multiple different um, multiple different here extensions. 35:29.850 --> 35:31.650 I will talk about them in a while. 35:31.690 --> 35:33.490 However, for now let's provide a prompt. 35:33.650 --> 35:39.050 So for the prompt what we have we've got the content and we've got the JSON keywords. 35:39.050 --> 35:43.730 I don't know why it's keywords but it should be JSON content. 35:44.650 --> 35:45.090 Okay. 35:45.650 --> 35:50.130 So we just give this entire variable for system message. 35:50.650 --> 35:52.650 Uh we are using this system message. 35:52.650 --> 35:53.650 Let's move on here. 35:54.050 --> 35:57.290 It's quite long I need to say it's quite long, but still. 35:57.370 --> 36:03.850 Um, as I said, this agent will be the most sophisticated from, um, the entire automation. 36:04.330 --> 36:07.770 Let's open the expression and let's see. 36:07.810 --> 36:08.890 We've got a purpose. 36:08.890 --> 36:14.300 So from a list of generated LinkedIn post data, each including a keyword, pose, description, title, 36:14.340 --> 36:15.380 and image prompt. 36:15.420 --> 36:20.940 Select the single most promising topic using real time web insights. 36:21.620 --> 36:24.500 Look how professional like it will be. 36:24.540 --> 36:25.980 Like how powerful? 36:26.540 --> 36:31.860 In general, we'll be using Think Node along with our web search option. 36:31.980 --> 36:35.180 So what it will do it will connect our open AI model. 36:35.500 --> 36:41.860 It will use Think node to decide actually to manage the entire process to be as a manager of this assistant. 36:42.220 --> 36:47.380 And we'll be using our web search extension to search the web for the most relevant topics. 36:47.460 --> 36:54.620 So in short, what this agent will do, it will take all of the keywords, all of the content ideas. 36:54.780 --> 37:02.420 It will decide which one is the best based on the actually best search from the internet and its best 37:02.420 --> 37:02.980 knowledge. 37:03.340 --> 37:05.020 So we've got our purpose. 37:06.100 --> 37:07.020 How it works. 37:07.020 --> 37:11.870 When you receive a long block of input containing multiple LinkedIn post entries, each with keywords 37:11.910 --> 37:13.950 for description, title and image prompt. 37:13.950 --> 37:15.190 Follow this process. 37:15.190 --> 37:19.630 Identify all keywords, so extract all keywords from the provided content. 37:19.790 --> 37:23.110 Each keyword represents a separate post entry. 37:23.230 --> 37:30.270 Evaluate keywords using web search so we have all of the data you know, current relevance, trend potential, 37:30.510 --> 37:36.510 virality and engagement potential, and a business professional context and give priority to topics 37:36.550 --> 37:39.710 gaining traction in the news or social media posts. 37:39.990 --> 37:46.470 Use cases with real stats, success stories, or market relevance keywords that align with LinkedIn's 37:46.510 --> 37:47.830 professional audience. 37:48.070 --> 37:50.310 Select the best topic from all entries. 37:50.310 --> 37:55.470 Select only one keyword that is the most likely to perform well on LinkedIn right now. 37:55.670 --> 37:57.110 Do not generate new content. 37:57.110 --> 38:02.990 Use the existing title, post description and image prompt linked to that keyword and we've got output 38:03.230 --> 38:03.950 format. 38:03.950 --> 38:05.350 So what it returns. 38:06.030 --> 38:06.510 Yeah. 38:06.550 --> 38:09.950 So return a single final output in the following structure. 38:10.470 --> 38:11.390 Let's see. 38:11.670 --> 38:13.870 I think something is wrong here. 38:14.110 --> 38:14.750 Okay. 38:15.390 --> 38:18.790 Return a single final output in the following structure. 38:19.710 --> 38:20.230 All right. 38:20.270 --> 38:22.670 Here we've got the JSON output format. 38:22.670 --> 38:24.630 So for this case I need to delete it. 38:25.150 --> 38:25.710 Okay. 38:25.990 --> 38:29.150 And I also will right now adjust it here. 38:29.990 --> 38:37.030 So you know like errors happen especially if you have that sophisticated automation I had over 100 errors 38:37.030 --> 38:38.310 in this specific project. 38:38.310 --> 38:42.470 Can you even imagine 100 errors like meanwhile building it? 38:42.510 --> 38:43.310 It's huge. 38:43.350 --> 38:44.670 I spend a lot of time. 38:44.950 --> 38:45.990 It was really hard. 38:46.030 --> 38:49.790 I need maybe not that hard, but a lot of time was spent. 38:50.150 --> 38:54.750 But let's go back now to the automation and do not return multiple results. 38:54.790 --> 38:57.630 Explain your choice at formatting or markdown. 38:57.630 --> 38:59.110 Include extra commentary. 38:59.390 --> 39:00.550 Example use case. 39:00.550 --> 39:04.110 So yeah, you can read it and JSON output format. 39:04.110 --> 39:06.430 So only return the following JSON structure. 39:06.470 --> 39:07.510 No extra text. 39:07.510 --> 39:10.600 And we want to get the keyword perfect. 39:11.200 --> 39:15.800 And now there's the part we need to enable the specific output format. 39:16.120 --> 39:19.240 So right away we can add some structured output format. 39:19.400 --> 39:23.080 And here inside the file I provided the output format here. 39:23.200 --> 39:28.400 So this is very simple you know output parser even you can just write it manually. 39:28.480 --> 39:29.880 It's pretty straightforward. 39:30.240 --> 39:33.080 Remember and be careful with the JSON format. 39:33.080 --> 39:35.880 So you need to just specify this JSON format. 39:35.880 --> 39:37.480 Otherwise you may have some problems. 39:37.720 --> 39:40.960 So the safer way will be to just copy it from the document. 39:41.320 --> 39:47.320 I think up next for this agent we add the chat model. 39:48.160 --> 39:51.480 We had the chat model and then we add memory. 39:51.680 --> 39:54.840 So we are using not memory however tool I'm sorry. 39:54.880 --> 39:56.600 We are using the think tool. 39:57.200 --> 40:01.920 And the think tool is really crucial really essential for this specific agent. 40:02.120 --> 40:08.330 Because you know, if we have the agent that operates on different extensions Ventures like web search, 40:08.370 --> 40:11.850 you know, OpenAI, maybe structured output format. 40:11.890 --> 40:17.050 We want to make sure all of that, like we've got the best result and all of that is structured. 40:17.050 --> 40:20.490 It works in the proper way and in the proper format. 40:20.610 --> 40:26.130 So Think Tool allows our agent to think to structure its work. 40:26.490 --> 40:28.610 Um, so that's why I'm using it. 40:28.610 --> 40:31.330 And let me show you what I prepared in the think note. 40:32.170 --> 40:33.690 It's quite interesting. 40:33.690 --> 40:37.770 So I've got a think node and I've got my very own description. 40:38.050 --> 40:40.970 So you're filtering and reasoning assistant. 40:41.130 --> 40:43.210 Review the information gathered below. 40:43.250 --> 40:47.330 Your job is to make sure a agent used web search to the site. 40:47.330 --> 40:50.210 Which keyword and content is the most proper to pick? 40:50.410 --> 40:55.730 Make sure the output format is only one chosen keyword, so it's not that hard. 40:55.770 --> 40:56.850 It's not that complicated. 40:56.890 --> 40:59.050 However, it's it's highly professional. 40:59.650 --> 41:00.410 It's enough. 41:00.730 --> 41:03.610 It's enough for our. 41:03.650 --> 41:04.370 Let me see. 41:04.610 --> 41:06.380 Um, next we've got our search web. 41:06.380 --> 41:09.180 So we've got all of the steps we need to we need to provide. 41:10.060 --> 41:12.180 So overall we'll be using. 41:12.380 --> 41:13.260 Let me show you. 41:13.300 --> 41:14.580 Now let's organize it. 41:15.940 --> 41:17.420 Maybe let's put it by this way. 41:17.780 --> 41:23.660 And even what I can do, let me pick all of my inputs here like sticky notes. 41:24.060 --> 41:24.540 I'm sorry. 41:24.540 --> 41:26.420 Let's let's pick all of the sticky notes. 41:26.700 --> 41:29.220 So you know what is happening inside. 41:29.700 --> 41:31.420 So now I can just paste it here. 41:31.420 --> 41:33.660 And now let me very quickly organize it. 41:34.740 --> 41:36.180 So now it's properly done. 41:36.180 --> 41:40.180 And let me guide you through what we've managed to actually accomplish. 41:40.300 --> 41:42.100 So we've got our inputs part. 41:42.100 --> 41:45.740 So here we provide our keyword and then we format it. 41:45.980 --> 41:49.580 We create a content with our loop and our free agents. 41:49.580 --> 41:51.100 We save it to our Google Sheets. 41:51.380 --> 41:53.140 Then we aggregate the content. 41:53.140 --> 41:55.020 So we put everything together. 41:55.020 --> 41:56.020 We added the fields. 41:56.020 --> 42:00.700 So we change change this specific type of the content into string. 42:00.700 --> 42:04.940 And we put it inside our agent, which is to create our keyword. 42:06.100 --> 42:07.660 So I'm actually not create. 42:07.700 --> 42:08.700 However take. 42:09.140 --> 42:18.620 Um, so what we can do, let's rename it very quickly as choose one keyword and what's now left keyword. 42:18.860 --> 42:24.260 And now what's left is our another tool which is for which is for web search. 42:24.540 --> 42:29.980 For this case I will be using the Tavli, which is actually the application that allows us to do this 42:29.980 --> 42:30.420 stuff. 42:30.860 --> 42:33.700 So I will be using HTTP request to connect to it. 42:33.700 --> 42:42.100 And then um I can click on method which is post, and now provide the URL for the URL we can pick. 42:42.380 --> 42:44.260 We can go ahead to our instructions. 42:44.260 --> 42:45.460 So we are using API. 42:46.020 --> 42:48.020 Com slash search. 42:48.860 --> 42:51.620 Um okay we've got a post search. 42:52.300 --> 42:54.940 And then we need to connect our credentials. 42:54.940 --> 42:57.020 So we pick generic credential type. 42:57.220 --> 43:01.620 We can pick header authentication and now create new credential. 43:01.820 --> 43:03.910 So in general we can name it as. 43:06.790 --> 43:07.670 A web search. 43:08.310 --> 43:08.950 Perfect. 43:10.270 --> 43:14.830 And now we can go ahead to lovely, lovely.com. 43:15.910 --> 43:21.390 And in general you've got your free, you know, free credits inside so you can use it totally for free. 43:21.510 --> 43:24.790 I've never, um, you know like paid for this specific tool. 43:24.790 --> 43:28.310 And it's great because it allows you to search the internet. 43:28.630 --> 43:34.630 So what you need to do, how to connect it, and the name you need to type authorization and exactly 43:34.630 --> 43:35.510 just type it. 43:35.510 --> 43:37.470 This is the required format. 43:37.990 --> 43:42.270 And in the value just go ahead and type BR. 43:43.270 --> 43:44.150 Perfect. 43:44.150 --> 43:47.910 And then just copy your API key. 43:47.950 --> 43:49.110 You can create it here. 43:49.470 --> 43:54.190 Um so copy your API key and now just paste it there. 43:54.230 --> 43:54.830 Perfect. 43:55.070 --> 43:56.230 We can click on save. 43:57.070 --> 43:58.790 And now there is the point. 43:58.790 --> 44:02.600 We need to send the body And click. 44:02.640 --> 44:03.760 Using JSON. 44:03.760 --> 44:05.040 And there is the point. 44:05.040 --> 44:07.680 We need to take the data from here. 44:07.840 --> 44:09.000 So JSON. 44:09.160 --> 44:09.800 Let me show you. 44:09.840 --> 44:12.760 We've got JSON, um, the specific code. 44:13.080 --> 44:14.480 And inside what we have. 44:15.400 --> 44:16.200 Let me show you. 44:16.520 --> 44:22.840 Um, we've got the query topic search depth and chunks per source, max results days and so on. 44:22.840 --> 44:26.000 So just all of the metrics, you can read them if you wish or not. 44:26.280 --> 44:30.160 But this node is now is now almost set up. 44:30.320 --> 44:32.520 However the last case is to type here. 44:32.800 --> 44:36.200 Use this tool to search the web. 44:36.360 --> 44:37.360 Search the web. 44:37.400 --> 44:38.040 Perfect. 44:39.040 --> 44:39.880 Um, great. 44:40.200 --> 44:43.840 And now, with all that being said, what we can do, we need to run this step. 44:43.880 --> 44:45.080 However, there is the point. 44:45.440 --> 44:49.960 Um, to run this step, we need to go through the entire loop. 44:50.160 --> 44:52.920 Um, part, um, looping part. 44:52.960 --> 44:54.600 So creating ten items. 44:55.160 --> 44:58.960 Um, but I've got for you one simple trick to avoid it. 44:58.960 --> 45:03.920 So you go ahead here You pick settings and you click execute once. 45:04.280 --> 45:10.280 Obviously we'll have only one keyword inside our keyword agent, but still. 45:10.480 --> 45:14.520 Um, yeah, we we need to set up the entire automation and then we can turn it off. 45:14.760 --> 45:21.520 So now look, if I want to run this specific step, it needs, it needs to run through the looping part. 45:21.720 --> 45:24.640 But it will return only one item instead of ten. 45:24.880 --> 45:27.480 So it's faster and yeah, it works. 45:27.480 --> 45:29.840 We've got our IT search our internet. 45:30.560 --> 45:32.600 It uses OpenAI think tool. 45:32.760 --> 45:35.000 Even we can preview what is happening inside. 45:35.040 --> 45:37.040 So firstly it used OpenAI. 45:37.120 --> 45:44.440 It gave the input, then it used to search for uh, you know, for the specific content. 45:45.000 --> 45:51.560 And we've got our OpenAI think tool OpenAI again and at the end structured output parser. 45:51.760 --> 45:55.200 And what we get in return, our keyword. 45:55.200 --> 45:56.200 That's perfect. 45:56.440 --> 45:58.440 So obviously right now we've got one keyword. 45:58.440 --> 46:03.850 Remember we don't have like we didn't choose from, let's say ten keywords, but only one. 46:04.770 --> 46:05.810 So that's great. 46:05.850 --> 46:12.730 We want to have only this specific keyword because based on this keyword we'll be searching Google Sheets 46:12.730 --> 46:13.770 for content. 46:14.370 --> 46:16.650 So we have get rows and sheet. 46:17.290 --> 46:18.450 We've got get rows. 46:18.450 --> 46:23.850 And now we pick this specific document this sheet which is this one. 46:25.170 --> 46:30.690 And then what we do um we add the specific filter. 46:30.850 --> 46:38.130 So the keyword and the value should be this, this value from our um agent to just one to choose one 46:38.130 --> 46:38.690 keyword. 46:38.930 --> 46:42.170 When we execute this step, we should get the entire content. 46:42.170 --> 46:43.250 That's great. 46:43.530 --> 46:48.450 So row number two keyword agents post title. 46:48.570 --> 46:49.330 We've got this. 46:49.370 --> 46:51.090 We've got the specific post title. 46:51.330 --> 46:52.330 That's correct. 46:52.930 --> 46:57.770 And I can say our content selection part is already created already set up. 46:57.980 --> 47:01.740 However, the problem is I can see we've got four items and it. 47:01.780 --> 47:08.540 Occurs because inside Google Sheets we have four um keywords for a agents. 47:09.020 --> 47:11.500 Usually it doesn't happen like it. 47:11.580 --> 47:16.900 It's not happening because remember we'll have different keywords like you know a lot of keywords and 47:16.900 --> 47:17.420 so on. 47:17.900 --> 47:19.100 And they will be different. 47:19.100 --> 47:21.100 So there will be just one item. 47:22.260 --> 47:26.260 And but for now again we are just creating this automation. 47:26.620 --> 47:33.620 Um, so for the simplicity for now we can um, actually and we can just maintain it also and we can 47:33.620 --> 47:36.780 return only, only first matching row. 47:36.940 --> 47:42.460 So that will um, let our Google Sheets to pick first specific row with the content. 47:42.460 --> 47:47.380 And again, for the purpose of this automation, it's totally fine after we just set it up, you know, 47:47.620 --> 47:49.140 um, let's see what we have. 47:49.420 --> 47:53.700 And this service is receiving too many requests per minute. 47:53.980 --> 47:55.300 Um, let's wait a while. 47:55.540 --> 47:57.380 Um, and again, let's run it. 47:57.740 --> 47:59.820 So maybe now let's try. 48:00.660 --> 48:01.340 Let's see. 48:04.020 --> 48:04.340 Um. 48:04.540 --> 48:05.300 Let's wait. 48:05.300 --> 48:06.340 Hopefully it works. 48:07.140 --> 48:07.340 Um. 48:07.340 --> 48:11.780 All right, I need to wait a few minutes after running it once again. 48:11.780 --> 48:12.420 It's cool. 48:12.420 --> 48:13.780 We've got one item. 48:14.180 --> 48:16.180 The next part is image generation. 48:16.420 --> 48:17.980 And I really enjoy. 48:17.980 --> 48:21.180 And I really like this part, actually, I like to generate images. 48:21.500 --> 48:28.460 Um, and there I just created for you a really nice workflow that creates the best image for your LinkedIn 48:28.460 --> 48:29.100 post. 48:29.660 --> 48:35.780 If we go ahead to our documentation and many times, um, actually we set we actually set the generate 48:35.780 --> 48:36.580 image node. 48:36.580 --> 48:40.580 So here what we have, we've got our URL, we've got the method which is post. 48:41.100 --> 48:42.900 However it will be a little different. 48:42.900 --> 48:44.940 Usually we use JSON format. 48:44.940 --> 48:49.260 But for this case we are specifying um specific parameters. 48:49.260 --> 48:50.260 So let me show you. 48:51.220 --> 48:53.620 Um let me go through um okay. 48:53.980 --> 48:57.870 Authentication Predefined XML type open API. 48:58.070 --> 48:59.230 Let's type it. 49:00.430 --> 49:04.830 We've got our account and here we send the body hover for this case. 49:05.190 --> 49:07.110 Um we've got parameters. 49:07.150 --> 49:07.590 Okay. 49:07.750 --> 49:11.070 The first one parameter as I can see will be the model. 49:11.070 --> 49:12.990 The second one will be the prompt. 49:13.110 --> 49:15.510 Third, the size and fourth quality. 49:15.790 --> 49:17.470 Let's fulfill it very fast. 49:17.670 --> 49:24.910 Um, so first we've got the model and then we've got, uh, what we have uh, prompt size and quality. 49:25.150 --> 49:31.790 Prompt size and quality. 49:33.190 --> 49:36.950 Perfect for the quality we want to pick high, obviously. 49:37.230 --> 49:45.110 Um, I provided the quality note here, um, because for, um, all right, for further, um, for further 49:45.110 --> 49:50.790 testing, we can change the quality every time so it doesn't take you, um, a lot of, you know, credits 49:50.790 --> 49:57.480 for the quality and high image you pay $0.17 for medium you pay for and for low you pay one. 49:57.480 --> 50:03.000 So let's say if you are testing and because obviously we will, we would need to like run this loop 50:03.000 --> 50:05.560 once again like many times probably. 50:05.560 --> 50:11.200 So if you want to test it, you can just set it as low and then just pay $0.01 and make it faster, 50:11.240 --> 50:13.480 whatever for the size. 50:13.720 --> 50:16.480 Um, here, um, let's pick the size. 50:18.080 --> 50:20.000 Um, perfect for the prompt. 50:20.000 --> 50:23.640 What we have, we've got our post image prompt. 50:24.160 --> 50:26.160 So this one and for the value. 50:26.160 --> 50:33.800 So we've got um, GPT image one probably this is the proper, um GPT image one. 50:33.800 --> 50:34.960 This is the proper value. 50:35.000 --> 50:35.600 Perfect. 50:36.040 --> 50:41.920 Um, let's generate uh, actually here we want to pick the post and let's execute the step. 50:41.960 --> 50:46.400 And even before generate image, let's execute the step. 50:48.040 --> 50:52.360 Um, let's click all right executing the step. 50:52.400 --> 50:53.890 And for sure it works. 50:53.930 --> 50:58.090 It's it takes approximately 40s for high quality image. 50:58.290 --> 51:02.290 So we need to wait just a while until it finishes. 51:03.450 --> 51:04.490 Process is done. 51:04.490 --> 51:12.490 We can click on plus and usually we provide here convert convert to file of course from base64 to string 51:12.530 --> 51:16.850 to file we provide the specific variable. 51:17.490 --> 51:18.650 We get binary file. 51:18.650 --> 51:19.450 Let's view it. 51:19.970 --> 51:20.610 Wow. 51:21.050 --> 51:21.770 That's perfect. 51:21.770 --> 51:24.970 Just look like we don't have any truncated text. 51:25.290 --> 51:27.930 Uh, we don't have any, you know, high quality. 51:27.930 --> 51:29.690 So of course everything is perfect. 51:29.770 --> 51:36.090 Even this specific part of the automation, let me show you, will prevent from any, you know, mistakes. 51:36.090 --> 51:39.610 So let's say the text is truncated or it's bad quality. 51:39.650 --> 51:46.610 It will prevent like every error will have because we've got if note and there our OpenAI checks if 51:46.610 --> 51:47.770 the image is correct. 51:48.490 --> 51:54.490 So uh we've got our file and now somehow we need to provide it. 51:54.490 --> 51:58.970 Like get the URL for this case I'm using external platform, which is cloudinary. 51:59.290 --> 52:02.610 Um, and now let's move on. 52:02.650 --> 52:04.650 Get image URL inside our file. 52:04.650 --> 52:05.650 You've got it. 52:05.650 --> 52:06.530 So URL. 52:07.650 --> 52:13.290 I will show you how to set it up and go ahead to cloudinary cloudinary.com. 52:14.090 --> 52:18.170 Um click Get Started, sign up with Google. 52:18.370 --> 52:19.010 Whatever. 52:19.010 --> 52:19.890 Let's sign up. 52:21.130 --> 52:23.090 Um, let's do it very fast. 52:24.170 --> 52:28.290 And after you do this, um, inside home, you should have. 52:28.330 --> 52:28.610 Oops. 52:28.650 --> 52:29.250 What's that? 52:29.290 --> 52:32.250 Inside home you should have your cloud name. 52:32.450 --> 52:33.450 Just copy it. 52:34.090 --> 52:38.010 Um, and inside this URL provide here your your cloud name. 52:39.210 --> 52:40.810 So you've got your cloud name. 52:40.810 --> 52:45.010 That's great method for now is post. 52:45.050 --> 52:50.420 Obviously we post we connect to the application not we get something from the application. 52:51.300 --> 52:53.780 And for the authentication actually what we do. 52:53.820 --> 52:54.540 Let me see. 52:55.100 --> 52:55.900 Um, all right. 52:56.380 --> 53:00.020 Now we need to specify and we need to send the body. 53:01.660 --> 53:05.220 So we send body um, form data. 53:05.940 --> 53:07.940 Um, probably it was form data. 53:07.940 --> 53:08.740 Let me see. 53:09.340 --> 53:10.060 All right. 53:10.100 --> 53:14.500 For the form data here and then binary file file data. 53:14.540 --> 53:15.140 Form data. 53:15.180 --> 53:15.580 All right. 53:15.580 --> 53:17.100 Preset perfect. 53:17.340 --> 53:20.060 So the first case is our binary file. 53:20.420 --> 53:24.140 What we have here um, we've got the file data. 53:26.020 --> 53:29.820 So this is the file data simply the data field name. 53:29.820 --> 53:32.340 Because the field name of this file is data. 53:32.340 --> 53:34.580 So this is the data parameter. 53:35.020 --> 53:37.140 Um this is approximate actually. 53:37.180 --> 53:37.500 Nah. 53:37.500 --> 53:39.620 Then I forgot about it. 53:39.820 --> 53:41.660 This is upload preset okay. 53:41.700 --> 53:42.940 This is upload preset. 53:43.460 --> 53:44.260 Let's see okay. 53:44.300 --> 53:45.180 Upload preset. 53:45.540 --> 53:52.230 Just let's copy it here and in this value you need to provide your preset name. 53:52.830 --> 54:00.350 If you go ahead to Cloudinary, you click on settings, you click on upload right here. 54:00.590 --> 54:03.910 You just you just create your preset, um, name. 54:04.030 --> 54:04.550 Okay. 54:05.110 --> 54:10.950 You click in the right top corner at upload preset, you name it as Na. 54:10.990 --> 54:17.910 Then let's say LinkedIn, I don't know, um, on signing mode you click on unsigned and you click on 54:17.910 --> 54:18.310 save. 54:19.270 --> 54:27.350 Simply copy the name, go here, paste the name and click on Execute Step. 54:28.590 --> 54:29.590 Click on execute step. 54:29.590 --> 54:31.910 Once again what's happening here. 54:33.190 --> 54:34.430 Convert to file. 54:34.470 --> 54:35.710 Execute step. 54:36.670 --> 54:37.550 Nice. 54:37.550 --> 54:38.910 We should get our URL. 54:39.630 --> 54:41.150 Uh we we have our URL. 54:41.350 --> 54:45.110 If you take this URL you open your page, you paste here. 54:45.110 --> 54:46.670 You should get your image. 54:46.870 --> 54:47.350 Great. 54:47.990 --> 54:55.830 So by this way, we store the image in the specific place because we want to have the URL to use the 54:55.830 --> 54:57.230 open AI node. 54:58.270 --> 55:01.710 And we are using this node to analyze image. 55:01.710 --> 55:03.470 That's truly great. 55:03.470 --> 55:07.830 We can use AI to analyze our image and give us a feedback. 55:07.830 --> 55:08.390 All right. 55:08.430 --> 55:09.910 Is this image high quality? 55:10.070 --> 55:16.030 Like if we don't have translated, do we have the translated truncated text or not. 55:16.270 --> 55:18.150 So that's highly professional. 55:18.150 --> 55:18.870 That's great. 55:18.910 --> 55:21.790 We are using GPT for all image URL. 55:21.830 --> 55:27.510 We are using this image URL that, you know, um, we wanted to get from here. 55:27.510 --> 55:30.630 So we have the URL perfect. 55:30.990 --> 55:36.430 And for the text input uh right here we've got the text input. 55:37.870 --> 55:41.230 So uh, I simply provided the following sentence. 55:41.550 --> 55:48.040 Is the image provided high quality without any truncated text respond yes or no. 55:48.080 --> 55:50.800 Don't provide dot at the end of yes or no response. 55:51.680 --> 55:53.000 Let's execute the step. 55:53.800 --> 55:55.120 Waiting waiting waiting. 55:56.320 --> 55:56.760 Um. 55:59.080 --> 55:59.480 Okay. 55:59.560 --> 56:03.800 Is the image provided high quality without any truncated text? 56:03.800 --> 56:05.360 And the response is yes. 56:05.480 --> 56:06.000 Great. 56:06.040 --> 56:07.160 This is our content. 56:07.200 --> 56:09.440 We would need to have only this specific variable. 56:10.040 --> 56:10.800 Nice. 56:11.480 --> 56:19.000 And all of this like all of all of these, um, these two nodes are for the if node will be providing. 56:19.960 --> 56:24.120 So we check if the value here is equal to yes. 56:24.720 --> 56:30.720 And now based on the big letter or small letter at the beginning we just provide, you know another 56:30.720 --> 56:31.440 condition. 56:31.720 --> 56:33.200 We click on or. 56:33.240 --> 56:40.160 So we just prevent future errors you know because it is equal to like refers to the specific sentence. 56:40.160 --> 56:44.040 And also it matters like if we have big letter or small. 56:44.200 --> 56:47.770 So we can just specify another condition for this case. 56:47.770 --> 56:51.170 Content equal to yes with big letter. 56:51.690 --> 56:55.530 We can execute this step and wait. 56:55.570 --> 56:56.850 Yeah we've got the output. 56:56.850 --> 56:57.530 It works. 56:57.770 --> 57:00.370 So this is the true we go through. 57:00.770 --> 57:04.130 If it's false we go back to generate image. 57:04.490 --> 57:08.090 So now let me pick all of these steps and put it like by this way. 57:08.330 --> 57:13.170 So how it works simply if the image is bad quality we go back to this step. 57:13.170 --> 57:14.170 We generate image. 57:14.170 --> 57:14.970 Then we go through. 57:15.010 --> 57:16.690 We go through, we analyze image. 57:16.890 --> 57:22.850 If still it's bad quality again we go through, we generate image until we get something we want. 57:23.250 --> 57:27.770 Then if it's finally good, we um, yeah, it's the true. 57:28.130 --> 57:32.250 So then we go ahead with publish the content on LinkedIn. 57:32.930 --> 57:36.530 For this case, uh, we pick edit fields. 57:37.250 --> 57:41.090 And now for the original version we are using HTTP request. 57:41.570 --> 57:44.050 But actually you've got the alternative. 57:44.050 --> 57:48.290 So for an example, let me pick up like this entire block here. 57:48.730 --> 57:51.970 Um, I won't be setting it up in this video. 57:52.010 --> 57:53.570 I think it will be too long. 57:53.850 --> 57:55.250 It doesn't make any sense. 57:55.610 --> 57:57.970 I provided it here for you already. 57:58.010 --> 57:58.450 This. 57:58.490 --> 57:59.930 These are the alternatives. 57:59.930 --> 58:06.530 So instead of the HTTP request, you can use LinkedIn node for posting on your business account and 58:06.570 --> 58:09.010 HTTP request for your personal account. 58:09.730 --> 58:12.170 But let's move on to setting up the edit node. 58:12.170 --> 58:17.890 And for what I want to use it, I want to combine title and description together, because we'll be 58:17.890 --> 58:25.330 using JSON format for HTTP request, and it requires to have specific format of the content. 58:25.330 --> 58:32.130 So we are using Edit node to just combine everything together again for the value we pick. 58:32.490 --> 58:33.570 Where do we have it? 58:33.610 --> 58:35.370 Our agent for the title. 58:35.610 --> 58:36.330 Perfect. 58:36.570 --> 58:44.780 Then we can provide dot um space and remember to don't provide here any enter like new line breaks and 58:44.780 --> 58:45.340 so on. 58:45.460 --> 58:50.620 Other like in that case if you provide it like it won't work inside HTTP request. 58:50.820 --> 58:56.740 Uh, we can provide a dot and space and with other node which is LinkedIn node. 58:56.780 --> 58:58.180 Other way of connecting it. 58:58.260 --> 59:00.660 We would um, we can actually, you know, do this stuff. 59:00.660 --> 59:05.300 So provide the breaks like provide numbered list like like do all of the formatting. 59:05.300 --> 59:05.940 It's fine. 59:05.940 --> 59:08.820 But for this HTTP request we are not able to do this. 59:09.620 --> 59:12.300 For now we can pick the description. 59:13.220 --> 59:15.140 So put it here okay. 59:15.140 --> 59:17.100 We need to make sure we don't have the. 59:17.460 --> 59:19.460 All right the break execute step. 59:20.580 --> 59:21.420 Let's wait. 59:22.100 --> 59:22.580 All right. 59:22.580 --> 59:24.260 It runs the entire loop. 59:24.260 --> 59:27.700 So now we can preview if other steps work. 59:28.940 --> 59:31.460 Um however for now we've got here the high quality. 59:31.460 --> 59:34.180 So it will take approximately 40s. 59:34.340 --> 59:37.180 But still here it works like we've got web search. 59:37.500 --> 59:39.020 It takes 40s. 59:39.340 --> 59:40.900 All right, so I need to wait. 59:41.910 --> 59:43.630 As you can notice, it worked. 59:43.630 --> 59:46.710 So we have our content in the JSON format. 59:46.710 --> 59:47.550 That's great. 59:47.590 --> 59:52.470 It's great JSON format actually it's proper JSON format we can use for further step. 59:53.110 --> 01:00:00.550 And the further step like the next step is HTTP request will be connecting um, our na den to LinkedIn. 01:00:00.950 --> 01:00:06.470 I'm using Bluetooth, which is a platform that allows me to do this stuff, and I will show you how 01:00:06.470 --> 01:00:07.710 to do this step by step. 01:00:08.110 --> 01:00:10.590 Uh, we've used it in other videos. 01:00:10.750 --> 01:00:12.110 It's great application. 01:00:12.310 --> 01:00:13.990 Um, I can log into potato. 01:00:14.670 --> 01:00:16.830 Um, you've got seven day free trial. 01:00:17.030 --> 01:00:20.270 The link will be in the resources of this material so you can open it. 01:00:20.550 --> 01:00:25.630 And however, if you click on Start Free trial then you go ahead to settings. 01:00:25.630 --> 01:00:26.950 In the left bottom corner. 01:00:27.550 --> 01:00:33.790 You can connect at once to LinkedIn, Facebook, Instagram, TikTok threads, Pinterest, YouTube, 01:00:33.790 --> 01:00:34.590 and so on. 01:00:34.630 --> 01:00:37.190 I'm using it for my social media, so it's cool. 01:00:37.390 --> 01:00:39.070 Um, this is a great platform. 01:00:39.070 --> 01:00:39.200 Form. 01:00:39.800 --> 01:00:41.160 Now let me show you how it works. 01:00:41.440 --> 01:00:44.080 For the potato, actually, you need to pick this URL. 01:00:45.800 --> 01:00:47.600 So simply click here. 01:00:48.120 --> 01:00:50.960 You've got the URL for the authentication. 01:00:50.960 --> 01:00:54.560 You've got the generic credential type header authentication. 01:00:55.320 --> 01:00:56.880 And you have potato. 01:00:57.400 --> 01:00:58.720 Where do we have potato. 01:00:59.960 --> 01:01:03.360 Um also let me show you how we can connect uh your blood. 01:01:03.520 --> 01:01:06.680 Do you provide blood API key. 01:01:07.840 --> 01:01:14.400 And then in the value we've got here expression however in the value what you need to do, um, you 01:01:14.400 --> 01:01:24.920 go here, you pick your, um, you pick your API key right here, right here in the settings, and you 01:01:24.920 --> 01:01:26.440 provide the following sentence. 01:01:26.720 --> 01:01:33.000 I actually, to be honest, I don't I don't remember if you need to provide the key before the API key. 01:01:33.000 --> 01:01:34.160 So do it by this way. 01:01:34.200 --> 01:01:37.320 Or you just can paste like, you know, API key alone. 01:01:37.360 --> 01:01:40.560 For me, I think you need to provide the key before. 01:01:41.040 --> 01:01:43.120 So even right now, let me test it out. 01:01:43.120 --> 01:01:47.760 So we see actually if this step works or not okay so I saved it. 01:01:47.760 --> 01:01:52.280 Now we need to send um body parameters using JSON. 01:01:53.560 --> 01:01:58.920 And then we've got this specific, um the specific um content. 01:01:59.200 --> 01:02:03.040 So what we have inside uh we need to get image URL. 01:02:03.320 --> 01:02:05.880 So we provide media URLs. 01:02:06.120 --> 01:02:07.360 So this is our. 01:02:08.000 --> 01:02:08.560 All right. 01:02:08.560 --> 01:02:09.680 This is our note. 01:02:10.000 --> 01:02:21.280 Um, even let me undo and set this note name as get image URL rename get image URL. 01:02:21.880 --> 01:02:22.520 Great. 01:02:23.040 --> 01:02:26.520 Now it should it should be highlighted on the green. 01:02:26.640 --> 01:02:27.200 Great. 01:02:27.680 --> 01:02:28.280 Um okay. 01:02:28.440 --> 01:02:31.720 For account ID I will be showing you how you can do this. 01:02:31.960 --> 01:02:33.480 Um, you go ahead to potato. 01:02:33.600 --> 01:02:34.600 You just click. 01:02:35.000 --> 01:02:35.640 What's that for? 01:02:35.640 --> 01:02:36.040 LinkedIn. 01:02:36.040 --> 01:02:36.360 Okay. 01:02:36.360 --> 01:02:37.330 You just click. 01:02:37.370 --> 01:02:42.530 I can click on this on disconnect, delete and log in with LinkedIn. 01:02:43.930 --> 01:02:45.090 I can click sign in. 01:02:46.050 --> 01:02:47.090 It's really simple. 01:02:47.370 --> 01:02:54.330 And then I've got my profile connected I click copy account ID then I can provide it here. 01:02:54.850 --> 01:02:56.050 So you did it by this way. 01:02:56.610 --> 01:03:00.810 And right away I can name it as upload to LinkedIn. 01:03:02.290 --> 01:03:03.090 Perfect. 01:03:03.130 --> 01:03:06.010 Let me execute the step and right away I will see. 01:03:06.290 --> 01:03:06.970 All right. 01:03:07.010 --> 01:03:07.930 What's happening. 01:03:08.130 --> 01:03:10.570 Right away I will see if that works. 01:03:11.850 --> 01:03:17.650 Okay, so we've got, um, check your credentials for this specific purpose. 01:03:17.810 --> 01:03:20.170 Probably I'm thinking about right now. 01:03:20.210 --> 01:03:21.690 Um, let's resolve the problem. 01:03:21.890 --> 01:03:22.690 Um, on live. 01:03:23.050 --> 01:03:25.370 So I can copy API key again. 01:03:25.930 --> 01:03:32.210 Now, maybe we need to start the value with the, uh, with the big letter save. 01:03:33.170 --> 01:03:34.410 Hopefully now it works. 01:03:34.970 --> 01:03:35.490 Please. 01:03:35.660 --> 01:03:36.060 No. 01:03:36.500 --> 01:03:39.260 Um, let's see if. 01:03:39.300 --> 01:03:44.940 Do we need, uh, to provide just API key without anything else? 01:03:46.060 --> 01:03:48.860 So copy API key, API key. 01:03:49.460 --> 01:03:51.260 Um, click on save. 01:03:52.140 --> 01:03:53.300 Execute step. 01:03:54.780 --> 01:03:55.860 Yeah it works. 01:03:56.020 --> 01:03:59.700 We had to provide API key without any other elements. 01:04:00.180 --> 01:04:01.060 Um, great. 01:04:01.420 --> 01:04:07.540 Um, if if it's done, we can go ahead and um, click on Publish Posts. 01:04:07.620 --> 01:04:09.420 So as you can see we've got LinkedIn. 01:04:09.740 --> 01:04:12.100 So we can check right now our LinkedIn. 01:04:12.140 --> 01:04:13.740 Let's move on to LinkedIn. 01:04:13.900 --> 01:04:16.780 To my actually no this is my business profile. 01:04:16.780 --> 01:04:19.900 So let's search for DFA Course Academy. 01:04:20.180 --> 01:04:21.460 Um, no, this is my profile. 01:04:21.460 --> 01:04:23.740 What I'm saying, what am I what am I saying? 01:04:24.180 --> 01:04:24.540 Um. 01:04:25.980 --> 01:04:27.020 Nice. 01:04:27.060 --> 01:04:27.780 Perfect. 01:04:27.780 --> 01:04:28.700 We've got the content. 01:04:28.700 --> 01:04:33.100 So, look, are you ready to harness the power of AI agents for business transformation? 01:04:33.100 --> 01:04:34.100 This is a title. 01:04:34.100 --> 01:04:41.340 Then we've got our content, our keywords, like our, you know, um, hashtags and our image. 01:04:41.380 --> 01:04:42.140 Great. 01:04:42.460 --> 01:04:48.580 We created actually, you know, we created our automation to publish, um, posts on LinkedIn. 01:04:48.700 --> 01:04:50.980 And again, remember, it's highly professional. 01:04:51.180 --> 01:04:52.940 We create the best content. 01:04:53.020 --> 01:04:58.140 We use a agent to choose the best content from ten different content ideas. 01:04:58.140 --> 01:04:59.860 We generate images and we check. 01:04:59.860 --> 01:05:02.780 We double check if the image is correct. 01:05:02.820 --> 01:05:10.540 We publish content on LinkedIn, and at the end there is the step to save the data and mark it as done 01:05:10.860 --> 01:05:12.220 as processed. 01:05:12.260 --> 01:05:16.220 Oof, it's quite long automation, quite long video however. 01:05:16.540 --> 01:05:20.300 Yeah like it if you set it up once again I will say it. 01:05:20.300 --> 01:05:26.660 If you set it up once, you've got it for a long time and you've got proven way, actually proven automation 01:05:26.660 --> 01:05:29.500 to generate LinkedIn posts on autopilot. 01:05:29.700 --> 01:05:32.420 If you're watching this video right now, big congratulations. 01:05:32.460 --> 01:05:35.790 Actually, you you are here at this point of this video. 01:05:35.830 --> 01:05:36.230 Wow. 01:05:36.350 --> 01:05:37.790 I'm very surprised. 01:05:37.830 --> 01:05:39.110 Maybe not surprised, however. 01:05:39.110 --> 01:05:39.790 Impressed. 01:05:39.990 --> 01:05:40.670 Perfect. 01:05:41.710 --> 01:05:45.830 Um, now we can, um, update row and sheet. 01:05:46.630 --> 01:05:52.590 We can pick our specific Google Sheets, um, here, sheet one. 01:05:52.990 --> 01:05:55.230 And now we want to actually what we want to do. 01:05:55.430 --> 01:06:03.710 We want to insert get image url URL of an image and change the status to published. 01:06:05.110 --> 01:06:06.430 Let's execute the step. 01:06:06.550 --> 01:06:10.710 So we should get our status to published one of these probably. 01:06:10.910 --> 01:06:11.750 Um here. 01:06:11.750 --> 01:06:12.470 Let's wait. 01:06:13.470 --> 01:06:14.350 What happens? 01:06:14.390 --> 01:06:17.350 Um, the column to match parameter is required. 01:06:18.350 --> 01:06:21.910 Um, the column to match on here. 01:06:21.950 --> 01:06:22.430 Okay. 01:06:22.670 --> 01:06:23.070 Yeah. 01:06:23.110 --> 01:06:24.430 We've got a keyword. 01:06:25.510 --> 01:06:27.990 Um, keywords. 01:06:28.990 --> 01:06:29.190 Uh. 01:06:29.190 --> 01:06:29.710 Let's wait. 01:06:29.710 --> 01:06:29.910 Okay. 01:06:29.950 --> 01:06:30.990 Execute this step. 01:06:32.440 --> 01:06:33.600 What's happening? 01:06:33.840 --> 01:06:34.320 All right. 01:06:34.360 --> 01:06:36.520 It's generating the entire content once again. 01:06:37.600 --> 01:06:39.800 So let's wait and see if that worked. 01:06:40.800 --> 01:06:44.200 I see right now that I forgot to provide the keyword to map. 01:06:44.400 --> 01:06:47.920 So in general we need to map the specific keyword to match. 01:06:48.040 --> 01:06:50.920 And then it updates you know that specific field. 01:06:50.920 --> 01:06:52.760 So status material. 01:06:52.800 --> 01:06:55.000 So now let's click execute step. 01:06:55.840 --> 01:06:57.520 And again we need to wait. 01:06:57.800 --> 01:06:59.360 You know it hurts. 01:06:59.400 --> 01:07:05.880 It's it's really harsh that we need to wait every time to test some steps after the loop until the loop 01:07:05.880 --> 01:07:06.840 is finished. 01:07:07.000 --> 01:07:09.240 But still um this is how it is. 01:07:09.480 --> 01:07:13.840 Um, this trick is pretty nice if you can, like, execute only at once. 01:07:13.840 --> 01:07:16.520 So then you don't need to wait ten times. 01:07:16.960 --> 01:07:20.200 In the past, I need to say I used to do this like I used to. 01:07:20.360 --> 01:07:26.200 Wait, um, until the loop is is like creates, let's say five elements. 01:07:26.520 --> 01:07:30.040 Yeah, but I realized that this option exists, so it's pretty cool. 01:07:30.400 --> 01:07:37.560 Now let's wait until the image is generated and let's see if it works and if it updates our Google Sheets. 01:07:38.640 --> 01:07:41.000 So node is executed successfully. 01:07:41.160 --> 01:07:42.040 Let's move on. 01:07:42.200 --> 01:07:43.600 And yeah we've got it. 01:07:43.600 --> 01:07:45.000 So the content is published. 01:07:45.040 --> 01:07:46.200 We've got image URL. 01:07:46.560 --> 01:07:49.600 So by this way we completed the entire automation. 01:07:49.640 --> 01:07:52.640 However this is not the end because we've got our alternatives. 01:07:52.880 --> 01:07:56.240 And now let me show you how it works right here. 01:07:56.600 --> 01:07:58.720 So in general what you can do. 01:07:59.800 --> 01:08:02.280 Firstly what I recommend you to do is to change. 01:08:02.720 --> 01:08:08.560 Um, if you want to use this LinkedIn note and remember it's for your organization. 01:08:08.560 --> 01:08:11.760 So with this LinkedIn note you can post to your organization. 01:08:12.120 --> 01:08:15.800 However, with this HTTP request you post to your personal profile. 01:08:15.920 --> 01:08:20.320 And now let me show you how you can switch it, how you can, you know, just provide it right there. 01:08:20.720 --> 01:08:26.640 And in general, I created here other um system like customized system message. 01:08:26.640 --> 01:08:30.050 So it returns barely Different content. 01:08:30.450 --> 01:08:32.730 Um, I can just provide a system message here. 01:08:32.770 --> 01:08:35.810 Other other things are pretty the same. 01:08:36.930 --> 01:08:38.650 Um, for now, what I can do. 01:08:39.090 --> 01:08:45.530 Um, here, I just provided the image prompt because, um, let me show you if I execute, um, this 01:08:45.530 --> 01:08:50.090 specific, uh, you know, like this specific, um, workflow. 01:08:50.410 --> 01:08:55.410 That workflow, however, automation, um, it produces for me LinkedIn posts. 01:08:55.410 --> 01:09:01.370 It publishes it on my, um, business profile, but I only provide it, you know, for an example, 01:09:01.370 --> 01:09:07.850 create image prompt a agent here, create LinkedIn post post description agent here for the sake of 01:09:07.890 --> 01:09:09.290 this automation working. 01:09:10.090 --> 01:09:12.890 But now again I will show you how to incorporate it. 01:09:12.890 --> 01:09:15.610 So how to incorporate this note inside this automation. 01:09:15.610 --> 01:09:16.570 So it works. 01:09:16.570 --> 01:09:18.050 So you don't need to use potato. 01:09:18.610 --> 01:09:21.850 So the first thing I've done I changed the description. 01:09:21.850 --> 01:09:23.490 So I pick this description here. 01:09:23.530 --> 01:09:26.130 Just a few I don't know a few seconds ago. 01:09:26.130 --> 01:09:27.610 And I provided it here. 01:09:27.660 --> 01:09:30.180 So again the form is very different. 01:09:30.580 --> 01:09:31.420 The next case. 01:09:31.460 --> 01:09:33.940 Oh like it's generating for us the content. 01:09:33.940 --> 01:09:35.940 It publishes it on LinkedIn. 01:09:35.980 --> 01:09:36.620 Let's check. 01:09:37.460 --> 01:09:40.180 So DFA Course Academy. 01:09:40.900 --> 01:09:43.460 Um let's move on here. 01:09:44.540 --> 01:09:44.940 Um. 01:09:45.940 --> 01:09:46.620 Right now. 01:09:46.660 --> 01:09:47.300 Perfect. 01:09:47.340 --> 01:09:49.100 And now look on this specific content. 01:09:49.100 --> 01:09:50.260 It's different. 01:09:50.340 --> 01:09:52.060 So we've got our breaks. 01:09:52.060 --> 01:09:53.740 We've got, you know, like the title. 01:09:53.780 --> 01:09:55.100 Like it's much different. 01:09:55.140 --> 01:09:56.620 And just look on this graphic. 01:09:56.980 --> 01:09:57.420 Wow. 01:09:57.860 --> 01:09:58.940 Look on this graphic. 01:09:59.100 --> 01:10:00.620 You can you've got the system. 01:10:00.620 --> 01:10:02.180 You can run it on autopilot. 01:10:02.340 --> 01:10:03.260 It's published now. 01:10:03.260 --> 01:10:03.740 Great. 01:10:04.260 --> 01:10:06.820 So maybe better let me show you how to incorporate it. 01:10:07.620 --> 01:10:16.140 So now the point is we've got our step for agent and we've got our step here for generate image. 01:10:17.460 --> 01:10:21.620 And for the sake of this specific case we need to take these two notes. 01:10:22.100 --> 01:10:24.220 So let's copy them face here. 01:10:24.460 --> 01:10:26.790 And we need to remove these nodes. 01:10:26.830 --> 01:10:27.750 These two nodes. 01:10:30.190 --> 01:10:30.670 Um. 01:10:31.310 --> 01:10:32.710 Make it by this way. 01:10:34.790 --> 01:10:36.510 And now, um, okay. 01:10:36.550 --> 01:10:40.670 Connect it for the convert to file. 01:10:41.110 --> 01:10:45.230 Um, what we can do, let's actually execute. 01:10:45.550 --> 01:10:47.550 Uh, we can execute previous nodes. 01:10:48.110 --> 01:10:48.510 All right. 01:10:48.510 --> 01:10:53.270 So let's execute previous nodes and let's wait. 01:10:53.630 --> 01:10:58.310 Uh, what's wrong actually HTTP request JSON chat input. 01:10:58.310 --> 01:10:59.030 All right. 01:10:59.270 --> 01:11:01.550 Let's provide chat input a. 01:11:04.070 --> 01:11:06.670 Um, okay. 01:11:07.270 --> 01:11:07.470 Uh. 01:11:07.470 --> 01:11:08.190 What's happening? 01:11:08.230 --> 01:11:11.390 Could not find a name named um. 01:11:11.470 --> 01:11:12.030 Okay. 01:11:12.190 --> 01:11:13.790 Let's for now what we can do. 01:11:13.830 --> 01:11:15.070 Actually, let's save it. 01:11:15.590 --> 01:11:17.270 Let's refresh the page. 01:11:18.830 --> 01:11:23.670 And now, uh, we can actually type agents. 01:11:25.630 --> 01:11:26.070 Okay. 01:11:26.110 --> 01:11:26.830 It works. 01:11:26.830 --> 01:11:28.630 Now it returns one element. 01:11:28.670 --> 01:11:29.470 We need to wait. 01:11:29.870 --> 01:11:31.230 I could have changed. 01:11:31.510 --> 01:11:32.110 Like here. 01:11:32.110 --> 01:11:33.310 The quality to low. 01:11:33.750 --> 01:11:37.270 Um, it would just, you know, take less credits. 01:11:37.270 --> 01:11:38.470 I forgot about it. 01:11:38.470 --> 01:11:44.990 But in sake of testing the automations, if you have loop, remember to make sure you, you actually, 01:11:44.990 --> 01:11:46.390 you know, change it to low. 01:11:46.390 --> 01:11:48.350 So then you don't pay a lot of money. 01:11:48.870 --> 01:11:55.950 Uh, but still now I want to, like, you know, wait for this image so I can set here the specific 01:11:55.950 --> 01:11:56.550 fields. 01:11:57.750 --> 01:11:58.270 Okay. 01:11:58.310 --> 01:12:04.710 So really, shortly I had to recreate this actually ending of this automation, um, to publish the 01:12:04.710 --> 01:12:06.950 content with LinkedIn note. 01:12:06.950 --> 01:12:12.710 And this is from the fact, um, actually we need to have convert to file node before the LinkedIn note. 01:12:13.070 --> 01:12:19.110 And also we need to have convert to file node after um HTTP request. 01:12:19.110 --> 01:12:25.760 So it's kind of hard to, you know, combine everything together um, to find the ways to connect it. 01:12:25.760 --> 01:12:33.000 That's why I chose to pick the simplest way and to remove some steps inside image generation. 01:12:33.240 --> 01:12:38.840 So for now, it doesn't check if the text on image is truncated or not, or even its high quality. 01:12:38.880 --> 01:12:44.400 However, still with ChatGPT image generation tool, um, you know, like it provides great results. 01:12:44.720 --> 01:12:50.120 But, um, I need to mention I will put this tool, uh, I will put these two templates. 01:12:50.120 --> 01:12:52.160 So this one with LinkedIn note. 01:12:52.160 --> 01:12:57.200 So posting to your personal profile, um, and actually this is the no. 01:12:57.240 --> 01:12:58.800 This is the organization profile. 01:12:58.800 --> 01:13:04.280 So business profile and this template uh, which is actually posting, um, yeah. 01:13:04.280 --> 01:13:05.800 To your personal profile. 01:13:05.800 --> 01:13:09.440 So you will be able to download two specific JSON files. 01:13:10.120 --> 01:13:14.000 But now even let me show you how I connected my LinkedIn note. 01:13:14.320 --> 01:13:16.480 So it's pretty important actually. 01:13:16.520 --> 01:13:19.640 We firstly um connect create new credential. 01:13:20.040 --> 01:13:24.290 So um you pick standard and you connect my account. 01:13:24.690 --> 01:13:26.010 So let me show you. 01:13:26.050 --> 01:13:27.730 You should get your login here. 01:13:27.730 --> 01:13:28.570 So sign in. 01:13:29.610 --> 01:13:30.450 Perfect. 01:13:31.450 --> 01:13:38.130 And then what you do you go to LinkedIn and you open your page. 01:13:38.290 --> 01:13:41.010 Actually you know your business page. 01:13:41.690 --> 01:13:44.530 And then you just pick this specific code. 01:13:44.530 --> 01:13:48.410 So this is your ID go back here. 01:13:48.610 --> 01:13:50.370 You provided an organization. 01:13:50.370 --> 01:13:51.610 You are. 01:13:52.610 --> 01:13:56.930 And for the text I picked um create LinkedIn post description. 01:13:56.930 --> 01:13:59.370 So this is this variable. 01:13:59.370 --> 01:14:01.730 So create LinkedIn post description. 01:14:01.730 --> 01:14:05.810 This is this variable for media category I picked image. 01:14:05.810 --> 01:14:07.570 So the post contains an image. 01:14:07.570 --> 01:14:09.690 And then I've got a data. 01:14:09.730 --> 01:14:14.970 And it's pretty important because actually we need to have um this specific note. 01:14:14.970 --> 01:14:19.050 So convert to file because we are providing an image okay. 01:14:19.090 --> 01:14:23.770 So we are just specifying okay this is binary field data and so on. 01:14:23.890 --> 01:14:27.410 So that's how you connect your, uh, LinkedIn profile. 01:14:27.450 --> 01:14:32.010 Actually your LinkedIn note to an and again, um, let's test it out. 01:14:32.010 --> 01:14:33.490 So let's execute this step. 01:14:34.290 --> 01:14:35.450 So see if that works. 01:14:35.450 --> 01:14:38.170 So I can execute the entire automation. 01:14:38.530 --> 01:14:44.290 And after it's executed and we see that LinkedIn note is working properly. 01:14:44.770 --> 01:14:50.530 Um, then I will show you how this entire automation works that we set up in this video. 01:14:51.290 --> 01:14:57.170 So as you can notice note executed successfully, let's move on to our profile. 01:14:58.050 --> 01:14:59.610 Um, and let's look. 01:14:59.850 --> 01:15:00.170 Yeah. 01:15:00.210 --> 01:15:05.410 Now agents are transforming the way businesses and businesses operate. 01:15:05.410 --> 01:15:06.730 And the future is here. 01:15:07.090 --> 01:15:07.970 Perfect image. 01:15:07.970 --> 01:15:08.570 Great. 01:15:08.690 --> 01:15:10.370 Uh, it works for now. 01:15:10.490 --> 01:15:15.930 Um, let's run this automation that uses to post the content, and it checks for the image. 01:15:16.210 --> 01:15:22.220 Remember about, um, disabling the execute once option. 01:15:23.620 --> 01:15:26.900 Also to change the quality to high. 01:15:27.380 --> 01:15:29.500 Make sure you you do. 01:15:29.500 --> 01:15:30.420 You do it right. 01:15:30.460 --> 01:15:31.700 You can open chat. 01:15:32.260 --> 01:15:43.580 And let's say I provide a topic which is um, maybe let's go ahead and I then automations, uh, make 01:15:43.620 --> 01:15:47.500 sure you provide you you type it correctly. 01:15:47.660 --> 01:15:48.100 Okay. 01:15:48.620 --> 01:15:50.740 Now what it does it transform. 01:15:50.780 --> 01:15:54.660 It transformed our text and it runs through our loop. 01:15:55.220 --> 01:15:58.900 Um, so here, let me see how many items we have. 01:15:58.940 --> 01:15:59.420 Ten. 01:15:59.620 --> 01:16:00.940 So we should have ten loops. 01:16:00.940 --> 01:16:01.860 Iterations. 01:16:02.580 --> 01:16:03.580 Now we are waiting. 01:16:03.740 --> 01:16:07.460 It saves the data inside our Google Sheets. 01:16:08.260 --> 01:16:09.460 Um, let's open it. 01:16:09.660 --> 01:16:11.700 So I've got like this Google sheet. 01:16:12.100 --> 01:16:12.500 Um. 01:16:13.380 --> 01:16:15.980 All right, let's, uh, look here. 01:16:16.260 --> 01:16:21.190 A lot of, you know, like data here, so it should be appearing right there. 01:16:23.030 --> 01:16:23.670 Let's wait. 01:16:23.670 --> 01:16:23.990 Okay. 01:16:24.070 --> 01:16:24.630 Nice. 01:16:24.670 --> 01:16:26.390 It appears now. 01:16:26.990 --> 01:16:29.150 Row 191. 01:16:29.750 --> 01:16:30.110 Um. 01:16:31.110 --> 01:16:31.670 So let's wait. 01:16:31.710 --> 01:16:32.110 Nice. 01:16:32.150 --> 01:16:32.590 Great. 01:16:33.710 --> 01:16:34.670 Now we are waiting. 01:16:35.430 --> 01:16:36.950 Um, five loop iterations. 01:16:36.950 --> 01:16:38.390 We are waiting up to ten. 01:16:38.910 --> 01:16:41.150 Now it chooses the keyword for us. 01:16:41.150 --> 01:16:44.030 So on keyword, it used web search. 01:16:44.270 --> 01:16:45.110 That's great. 01:16:45.710 --> 01:16:46.310 Perfect. 01:16:46.350 --> 01:16:47.030 It gave. 01:16:47.070 --> 01:16:50.510 As you can notice, it gave ten items to check. 01:16:51.150 --> 01:16:52.470 And we get one item. 01:16:52.910 --> 01:16:53.470 Uh, what? 01:16:53.470 --> 01:16:57.190 It chose na then automation certification. 01:16:58.430 --> 01:16:58.910 Wow. 01:16:59.270 --> 01:16:59.670 Wow. 01:17:00.310 --> 01:17:02.710 Um, where do we have it? 01:17:02.710 --> 01:17:03.150 This one? 01:17:03.150 --> 01:17:03.910 This one row. 01:17:04.150 --> 01:17:09.870 It should be highlighted on as published, uh, in a moment. 01:17:11.310 --> 01:17:13.150 So let's wait. 01:17:13.150 --> 01:17:14.310 Actually, I'm not sure. 01:17:14.350 --> 01:17:14.790 Here. 01:17:14.830 --> 01:17:15.470 Probably. 01:17:15.550 --> 01:17:17.110 Yeah, I provided append row. 01:17:17.150 --> 01:17:20.990 It should be update row, update row as we have here. 01:17:21.190 --> 01:17:26.310 Um, as we have here, it should be this form so it won't, you know, update this row. 01:17:26.830 --> 01:17:31.270 Um, however, um, you know how it looks like, how it works. 01:17:31.270 --> 01:17:33.310 And it worked for this specific case. 01:17:33.310 --> 01:17:34.670 So we've got the proof. 01:17:35.070 --> 01:17:36.430 Now we generate a match. 01:17:36.430 --> 01:17:40.790 I'm very curious if the image, like, will be sufficient enough. 01:17:41.150 --> 01:17:43.790 Um, because remember, like I like this loop. 01:17:43.790 --> 01:17:44.550 I like this loop. 01:17:44.550 --> 01:17:46.390 I like this part because it checks. 01:17:46.430 --> 01:17:47.030 All right. 01:17:47.070 --> 01:17:48.310 The moment of truth. 01:17:48.910 --> 01:17:51.030 Um, if image. 01:17:51.270 --> 01:17:51.950 Yeah. 01:17:52.150 --> 01:17:54.990 Like image is not proper for us. 01:17:55.550 --> 01:17:56.150 Wow. 01:17:56.790 --> 01:17:57.550 All right. 01:17:57.590 --> 01:17:59.030 Even the quality is high. 01:17:59.310 --> 01:18:04.870 So, you know, like, that's why I spend a lot of time on this automation I didn't want to provide, 01:18:04.910 --> 01:18:10.630 you know, like the notes for getting one idea for, you know, generating image. 01:18:10.830 --> 01:18:12.230 Everyone could have done it. 01:18:12.230 --> 01:18:13.550 Everyone could have done it. 01:18:13.750 --> 01:18:15.790 Everyone is doing it by this way. 01:18:15.920 --> 01:18:17.120 But we are different. 01:18:17.120 --> 01:18:19.160 We are just doing something better. 01:18:19.520 --> 01:18:22.320 Um, so this is very comprehensive automation. 01:18:23.000 --> 01:18:24.000 Let's wait. 01:18:24.160 --> 01:18:25.440 Um, all right. 01:18:25.480 --> 01:18:25.960 Here. 01:18:26.440 --> 01:18:27.160 Um, yes. 01:18:27.160 --> 01:18:28.040 No content? 01:18:28.080 --> 01:18:28.560 No. 01:18:28.840 --> 01:18:29.960 So it stopped. 01:18:30.480 --> 01:18:31.800 Um, but I'm very curious. 01:18:31.800 --> 01:18:34.040 What what we had view. 01:18:34.840 --> 01:18:35.200 Wow. 01:18:35.240 --> 01:18:39.520 Look look look look, guys, look, we've got text, which is just wrong. 01:18:39.800 --> 01:18:40.840 This text is wrong. 01:18:41.000 --> 01:18:42.000 So that's why we've got. 01:18:42.040 --> 01:18:43.400 No, um. 01:18:44.440 --> 01:18:45.720 This is the moment of truth. 01:18:45.720 --> 01:18:46.760 There are no cuts. 01:18:46.800 --> 01:18:49.200 We are, um, maybe this one image. 01:18:50.360 --> 01:18:51.080 Let's see. 01:18:51.120 --> 01:18:51.960 Nice. 01:18:52.000 --> 01:18:56.280 It's processed, but the service was not able to process your request. 01:18:56.440 --> 01:18:58.280 Why account? 01:18:58.320 --> 01:18:58.880 No. 01:18:59.800 --> 01:19:00.360 Wow. 01:19:01.040 --> 01:19:06.840 I you know, in this video, I connected every time when we use potato. 01:19:07.080 --> 01:19:13.840 Um, I deleted my credential, I deleted my credential, and I again created it in this video. 01:19:14.120 --> 01:19:17.290 Um, And so the account ID, I will show you the proof. 01:19:17.330 --> 01:19:18.930 Account ID is different. 01:19:19.810 --> 01:19:24.690 So it's so it's 3159 and it changes every time we do this stuff. 01:19:25.090 --> 01:19:28.210 Um okay I will run the automation once again. 01:19:28.450 --> 01:19:31.130 Um, and also change this part. 01:19:31.610 --> 01:19:38.010 So what we have we've got update row um select column. 01:19:38.890 --> 01:19:41.370 Um okay. 01:19:42.250 --> 01:19:44.610 So finally I can see it worked. 01:19:44.650 --> 01:19:47.730 Uh, we've got the only small problem with, um, Google Sheets. 01:19:47.730 --> 01:19:52.890 However, you know, we need to provide first instead of item, and it should work. 01:19:53.130 --> 01:19:57.330 But for now and what we have, let's see what image we have. 01:19:57.610 --> 01:19:58.130 View. 01:19:58.730 --> 01:19:59.250 Whatever. 01:19:59.250 --> 01:20:00.850 Let's look on the post. 01:20:01.010 --> 01:20:02.610 Um, we published. 01:20:02.730 --> 01:20:05.290 So here let's take a look. 01:20:06.570 --> 01:20:09.490 Um, we need to refresh. 01:20:12.050 --> 01:20:13.380 Um, Okay. 01:20:14.020 --> 01:20:15.060 What's wrong? 01:20:15.300 --> 01:20:16.300 I don't know, actually. 01:20:16.700 --> 01:20:17.260 Um. 01:20:17.420 --> 01:20:18.420 Let's see. 01:20:18.820 --> 01:20:19.940 Um, wait. 01:20:20.820 --> 01:20:22.500 Let's move on here. 01:20:23.180 --> 01:20:30.940 So it should publish the content to our, um, LinkedIn profile, but I can't see the posts. 01:20:31.540 --> 01:20:33.780 Um, let's refresh again. 01:20:34.540 --> 01:20:36.540 So now I can see that it works. 01:20:36.540 --> 01:20:39.020 Finally, we tested our automation. 01:20:39.020 --> 01:20:45.380 So again, we've got an items like it, chose the best item for us, created image view automation. 01:20:45.380 --> 01:20:45.780 Wow. 01:20:45.900 --> 01:20:46.900 Really high quality. 01:20:47.620 --> 01:20:49.660 Uh, we've got a small problem here. 01:20:49.900 --> 01:20:54.260 So, um, like, the solution is to provide I had here the item. 01:20:54.500 --> 01:20:59.820 So the solution, if you have multiple items you provide first and now it should work. 01:21:00.100 --> 01:21:02.540 But for now let's check our post. 01:21:03.100 --> 01:21:05.700 Um, so let's go ahead to my profile. 01:21:06.060 --> 01:21:09.220 Firstly this is my profile name. 01:21:09.380 --> 01:21:09.780 Wow. 01:21:10.740 --> 01:21:11.620 Great. 01:21:11.980 --> 01:21:15.940 Okay, so for sure, it worked perfect. 01:21:16.340 --> 01:21:17.300 Um, yeah. 01:21:17.300 --> 01:21:22.140 So that's how you connect, um, you create the perfect LinkedIn automation. 01:21:22.540 --> 01:21:23.740 It took a lot of time. 01:21:23.900 --> 01:21:26.900 Um, I know that, like, this video was quite long. 01:21:26.940 --> 01:21:27.340 However. 01:21:27.380 --> 01:21:27.940 Thank you. 01:21:27.940 --> 01:21:30.940 If you're watching this video right now, thank you for your engagement. 01:21:31.100 --> 01:21:34.140 I really appreciate it that you watch these videos to the end. 01:21:34.260 --> 01:21:35.740 Um, it means a lot to me. 01:21:35.780 --> 01:21:39.860 I'm putting a lot of effort with Damian to create a lot of great automations. 01:21:39.860 --> 01:21:42.260 And again, thank you so, so much. 01:21:43.180 --> 01:21:50.220 Um, the last thing um, I want to mention is that you can take this specific part and you can put it 01:21:50.220 --> 01:21:54.580 here instead of these notes and do it by this way. 01:21:54.580 --> 01:21:59.700 So then you create the keyword and you can run this automation every day, um, you know, every hour 01:21:59.740 --> 01:22:01.620 or every minute if you wish. 01:22:01.940 --> 01:22:05.740 Um, but still the point is, um, you can use different triggers and so on. 01:22:05.780 --> 01:22:06.940 Thank you for watching this video. 01:22:06.940 --> 01:22:11.260 I hope you enjoyed it and I will see you in the next advanced automation.