WEBVTT 00:00.240 --> 00:04.520 Now is the time to create an AI agent that can manage your Google Calendar. 00:04.560 --> 00:11.120 Send the emails via Gmail and in general, just by the way, plan on all of your meetings with clients 00:11.120 --> 00:12.280 or other people. 00:12.480 --> 00:18.240 Nevertheless, what's very special in this material is that we'll be using deep C, R1 model and deep 00:18.520 --> 00:19.360 chat model. 00:19.640 --> 00:22.280 So we'll be basing on these models. 00:22.280 --> 00:23.920 We'll train how to use them. 00:24.160 --> 00:29.040 And also I will show you how to use deep R1 with the HTTP request. 00:29.040 --> 00:31.840 So we'll be setting entire HTTP request. 00:32.120 --> 00:34.520 And there I will show you how you can do this stuff. 00:34.520 --> 00:41.560 What are the differences between just setting up deep Sea here as a note and as a HTTP request? 00:41.720 --> 00:46.520 Even before we get started, let me show you how it works so I can open the chat, which is the trigger. 00:46.760 --> 00:48.160 And there I can type. 00:48.160 --> 01:00.620 For an example I would like to schedule a meeting with let's say Christian and his email is Christian. 01:00.940 --> 01:03.380 Udemy gmail.com. 01:04.100 --> 01:14.220 Let's say at 5 p.m. tomorrow and the meeting should last. 01:14.660 --> 01:16.300 Let's say two hours. 01:17.820 --> 01:18.140 Yeah. 01:18.140 --> 01:19.380 So I can just type it. 01:19.380 --> 01:25.780 Also I could for an example just just type like I would like to schedule the meeting, send the email 01:25.780 --> 01:31.020 to the Christian asking if he if he wants to get this meeting together with me. 01:31.060 --> 01:33.020 Nevertheless, right now I'm just saying. 01:33.060 --> 01:36.820 All right, schedule a meeting with Christian at this specific hour. 01:36.860 --> 01:38.140 This is his email. 01:38.140 --> 01:38.820 So we know. 01:38.860 --> 01:39.260 Yeah. 01:39.460 --> 01:40.740 And we can send this message. 01:40.740 --> 01:41.740 And what happens? 01:41.860 --> 01:48.700 It goes through our planner, a agent that creates the prompt actually with deep sea air one. 01:49.580 --> 01:53.700 And for this agent that actually, you know, does all of the things. 01:54.020 --> 02:00.920 So it uses deep chat model and then It's, um, it actually schedules for me the meeting inside the 02:00.920 --> 02:05.240 Google calendar and sends an email to the client person. 02:05.280 --> 02:07.200 Actually, we've got the meeting. 02:07.480 --> 02:08.240 Um, but hey. 02:08.280 --> 02:10.400 Alright, the meeting is at this specific hour. 02:10.440 --> 02:11.600 At this specific day. 02:11.960 --> 02:16.840 We are waiting some time because actually we are using deep reasoner model. 02:17.280 --> 02:21.520 So that means it thinks actually it takes more time to process. 02:21.960 --> 02:25.080 And also we've got the prompt we'll cover everything in this video. 02:25.200 --> 02:28.000 So we've got the mission operating scope workflow. 02:28.120 --> 02:34.240 So what this agent does it creates the prompt to our second agent. 02:34.640 --> 02:37.320 And then you know everything works by this way. 02:38.320 --> 02:39.680 Um so let's wait a while. 02:40.960 --> 02:42.640 So the entire workflow works. 02:42.640 --> 02:46.720 And now let's take a look of the prompt our planner agent gave. 02:46.920 --> 02:52.800 So here after we do this, after we run this agent, it gives the prompt for the assistant. 02:52.800 --> 02:57.550 So for example we've got schedule a two hour meeting with Christian there. 02:57.590 --> 02:58.070 The email. 02:58.070 --> 03:00.830 So what it does, it gives the entire prompt. 03:00.830 --> 03:04.430 And then we are using this agent that does everything for us. 03:04.430 --> 03:10.270 So it should schedule a Google calendar, a meeting and then send the email on Gmail. 03:10.750 --> 03:12.510 Um, for this case, let's see. 03:12.550 --> 03:16.390 We've got the meeting right here at the specific hour as I wanted. 03:16.750 --> 03:23.630 And also we've got this entire email to our person that we scheduled the meeting with. 03:24.190 --> 03:25.590 Um, so for sure it works. 03:25.590 --> 03:27.230 We'll build it step by step. 03:27.550 --> 03:34.630 Um, and this video will be a great practice for just connecting your agents with Deepshikha model. 03:34.630 --> 03:39.630 And also I will show you how to set up HTTP request, which is really useful. 03:39.630 --> 03:41.710 And in general, let's dive in. 03:42.710 --> 03:47.590 So when we are inside and then let's click in the right top corner on Create Workflow. 03:47.590 --> 03:51.110 And let's start with creating our entire agent. 03:51.510 --> 03:53.630 And the first step will be our trigger. 03:53.630 --> 03:59.850 So we indicate that we would like to trigger this entire automation whenever we've got chat message. 04:00.410 --> 04:02.770 You could, for example, choose also the form. 04:02.810 --> 04:07.050 However, for that circumstance I would like to process with the chat message. 04:08.170 --> 04:12.690 And then what we can do we can go ahead to our first agent. 04:13.770 --> 04:21.250 So we just search for this agent and then um we just click on define below and we provide the prompt. 04:21.250 --> 04:23.770 And there we click on add option. 04:23.930 --> 04:25.890 And we provide the system message. 04:25.890 --> 04:29.330 So we'll need these two fields and fulfilled. 04:29.930 --> 04:33.730 When you go ahead to our file that will be in the resources of this material. 04:33.930 --> 04:37.610 You will find everything every information inside. 04:37.610 --> 04:42.010 So we've got the prompt we'll be using and the system message that is pretty white. 04:42.170 --> 04:43.530 Also other things. 04:43.650 --> 04:44.370 Um, yeah. 04:44.410 --> 04:46.370 For this entire automation. 04:46.570 --> 04:52.490 Additionally, I will provide for you the JSON file so we can just download it and import inside. 04:52.870 --> 04:53.230 Yeah. 04:53.270 --> 04:54.790 Inside this workflow. 04:55.270 --> 04:59.110 So after you downloaded your file, you go ahead to the right top corner. 04:59.110 --> 05:01.630 You click on the three dots import from file. 05:01.870 --> 05:08.310 And after you click on the deep sea Corona agent, the entire workflow is provided inside Nadine. 05:08.870 --> 05:11.830 But now let's continue with creating that from start to finish. 05:11.830 --> 05:17.230 So we have again our agent and inside we provide a prompt and let's execute previous nodes. 05:17.910 --> 05:27.110 So for example I can type the following sentence schedule for me a meeting with Christian and something 05:27.110 --> 05:34.070 very similar to kind of, you know, um, yeah, train this entire automation and use the data inside 05:34.070 --> 05:34.710 this workflow. 05:34.710 --> 05:37.310 So schedule for me a meeting with Christian. 05:37.750 --> 05:50.430 Um, his email is let's provide some basic information, um, at, let's say 5 p.m., um, on let's 05:50.430 --> 05:58.010 say, I don't know, maybe June 16 or 14, 2025. 05:58.050 --> 05:58.610 All right. 05:59.130 --> 06:06.730 And let's say for one hour now, we can just simply run it, and then we'll be able to use this data 06:06.730 --> 06:08.090 inside our agent. 06:08.130 --> 06:09.370 So let's go over here. 06:09.570 --> 06:14.090 And as you can see our prompt is properly even fulfilled. 06:14.210 --> 06:16.210 So we just drag and drop this one variable. 06:16.210 --> 06:17.330 So chat input. 06:17.330 --> 06:21.210 And by this way we give the information to the model. 06:21.810 --> 06:27.490 Um for the system message um kind of here we'll be using this entire system message. 06:27.610 --> 06:29.930 You can go ahead to the file and just copy it. 06:30.850 --> 06:32.490 So let me show you how it looks like. 06:32.930 --> 06:34.370 Let's provide expression. 06:34.370 --> 06:36.250 And now inside we've got the mission. 06:36.250 --> 06:41.850 So we are an AI tasked with drafting clear practical prompts that help a personal assistant complete 06:41.850 --> 06:43.250 any job at hand. 06:43.930 --> 06:47.690 And we've got the operation scope, so no external tools or references. 06:47.730 --> 06:49.170 Keep every instruction brief. 06:49.280 --> 06:56.560 ordered an unmistakable then jobs can be simple or complex, but your wording must remain straightforward. 06:57.280 --> 07:00.160 So we have the workflow and illustrative scenarios. 07:00.200 --> 07:02.400 Even I provided there some examples. 07:02.400 --> 07:08.920 So for an example user requests book a doctor's appointment for next week and prompt to produce. 07:08.960 --> 07:11.200 Find open slots with the doctor next week. 07:11.240 --> 07:15.000 Pick a time that doesn't clash with existing events. 07:15.040 --> 07:17.680 Book the slot for phone or online. 07:17.880 --> 07:20.440 Confirm and add the appointment to the calendar. 07:20.640 --> 07:22.360 So what do we do with this agent? 07:22.400 --> 07:25.480 We actually create a prompt for the next agent. 07:25.920 --> 07:31.680 Obviously, if you want to read this entire description system message and you can stop the video, 07:31.680 --> 07:33.280 read it, it's your choice. 07:33.280 --> 07:38.200 However, you know, I don't want to waste too much, too much time on explaining all of the things 07:38.880 --> 07:42.360 we have inside this message because again, it's pretty white. 07:42.600 --> 07:48.260 And also we've got something like the Operation Operating checklist and we've got closing reminders 07:48.260 --> 07:51.420 and also what's very important, we provide a variable for the date. 07:52.020 --> 07:53.540 So current date and time. 07:53.900 --> 08:01.420 Nevertheless what we can do for now we need to add the chat model, chat model and their um memory. 08:02.140 --> 08:05.180 For the chat model we'll be using Deepsea. 08:05.380 --> 08:07.180 Deepsea chat model. 08:07.500 --> 08:10.580 And there in general we need to create our new credential. 08:10.860 --> 08:13.260 So for this case let me show you how to do this. 08:14.020 --> 08:16.220 Just simply type Deepsea API. 08:16.540 --> 08:18.300 Click on Deepsea API docs. 08:18.860 --> 08:22.940 And there in the right top corner click on Deepsea platform. 08:24.340 --> 08:28.340 When you are here uh you should actually provide some balance. 08:28.340 --> 08:31.660 So there I've got for an example $2 and Deepsea. 08:31.820 --> 08:39.340 Why we are even covering Deepsea instead for an example of um, let's say ChatGPT and models. 08:39.780 --> 08:45.100 Deepsea is one of the cheapest models available right now on the internet. 08:45.100 --> 08:51.480 So if you actually consider using some pretty nice models, you can use Deepsee because again, it's 08:51.480 --> 08:53.480 very efficient and very affordable. 08:54.000 --> 09:00.200 However, for now we can click on API keys, create new API key, and for an example type test. 09:00.240 --> 09:04.520 And then and then just copy this API key. 09:05.240 --> 09:10.560 Go ahead to your workflow and just paste it right there and click on save. 09:10.760 --> 09:13.120 I've got my API key so I can continue. 09:13.160 --> 09:14.160 I can close it. 09:15.160 --> 09:18.240 And for this case I will be using Deepsee Reasoner. 09:18.240 --> 09:26.840 So the model that actually thinks that, you know um, yeah, uses our thinking and reasoning and capabilities. 09:27.760 --> 09:29.720 Um, so I've got my Deepsee care1. 09:29.920 --> 09:33.320 And additionally what I can provide is the simple memory. 09:33.680 --> 09:39.520 This extension allows our agent to remember actually past interactions. 09:39.680 --> 09:43.320 Um, we've got inside our automation, inside our chart. 09:43.360 --> 09:46.540 So how many past interactions the model receives as context? 09:46.740 --> 09:50.420 It's cool because, uh, yeah, I like the model. 09:50.460 --> 09:52.380 The model to know what I'm typing. 09:52.940 --> 09:54.980 Um, and just it's very useful. 09:54.980 --> 09:59.900 Note for now, I can what I can do, I can click on test the step. 10:00.300 --> 10:03.300 So just use our model to create a prompt. 10:04.500 --> 10:09.860 Bear in mind that it takes some time because we are using Deepsee R1 instead of deepsee chat. 10:09.900 --> 10:13.620 So this reasoning model needs to have some space to work. 10:14.220 --> 10:18.540 Um, so it can take up, let's say up to three minutes or so. 10:19.020 --> 10:22.020 However, we've got our response from our model. 10:22.020 --> 10:25.220 So entire prompt we can use for now. 10:25.260 --> 10:26.260 Um it's perfect. 10:26.660 --> 10:29.060 Let's process with the next agent. 10:29.060 --> 10:30.100 And now what we can do. 10:30.140 --> 10:35.020 We can click on this agent and just hold Ctrl button. 10:35.100 --> 10:39.300 And then just click on other nodes and click on Ctrl D. 10:39.740 --> 10:43.200 So we just copy this a agent? 10:43.480 --> 10:47.040 For now, what we can do and we can connect them. 10:47.880 --> 10:50.080 And in general let's rename them. 10:50.080 --> 10:52.320 So let's go over here and click on rename. 10:52.560 --> 10:57.000 So we've got our um planner agent. 10:57.640 --> 11:01.600 And this will be um executive agent. 11:02.360 --> 11:10.760 So we've got executive um, so simply now we can see that this agent is for planning and this for just, 11:11.120 --> 11:13.720 just making and executing tasks. 11:14.760 --> 11:17.080 Uh, for this case, we can use the Leipzig chart. 11:18.120 --> 11:21.800 And then what we can do, we can just delete this memory option. 11:22.040 --> 11:23.920 It's not necessary for now. 11:24.120 --> 11:25.720 And we can add our tools. 11:26.000 --> 11:29.000 The first tool will be our Gmail node. 11:29.160 --> 11:29.920 All right. 11:29.960 --> 11:33.800 We would like to use the Gmail to send the message. 11:34.280 --> 11:39.000 And for this case um we've got the resource which is message operation sent. 11:39.040 --> 11:45.870 We've got a tool so we can just simply open, and here we can just simply open two curly brackets. 11:46.550 --> 11:52.230 And now we'll be providing the specific variable which is dollar sign. 11:52.670 --> 11:55.190 And we will be using from I. 11:55.830 --> 12:03.990 So this entire code allows us to ask I for getting for us the email of the person from our chat. 12:04.150 --> 12:09.350 Because you need to remember actually here we don't have any variable for the email. 12:09.550 --> 12:11.510 The email is somewhere there. 12:11.670 --> 12:14.070 So we've got the email. 12:14.110 --> 12:20.190 However, still we can just provide this entire output because we need to have clear value right there. 12:20.350 --> 12:24.750 So we can just type from I and there inside type something like this. 12:25.070 --> 12:29.270 So let's say we've got email address okay. 12:29.710 --> 12:32.710 And I should guess what we have inside. 12:32.710 --> 12:34.230 Like what should be inside okay. 12:34.870 --> 12:36.750 And we can just copy it again. 12:36.990 --> 12:40.450 However now inside this the the, um, yeah. 12:40.490 --> 12:46.730 Inside the brackets, we can type the subject and they're inside the message. 12:47.770 --> 12:53.810 We can go ahead and type actually our message. 12:56.130 --> 12:57.170 So it's very cool. 12:57.170 --> 13:02.050 It's not that easy to set up because if you have never used like, uh, yeah. 13:02.330 --> 13:06.130 Um, this, this entire comment, um, you may have some problems. 13:06.130 --> 13:09.010 However, you will see, it's not that complicated. 13:09.730 --> 13:15.010 Um, let's go back to canvas and the similar thing we'll be doing with Google Calendar so we can pick 13:15.010 --> 13:16.010 Google Calendar. 13:17.410 --> 13:20.770 Where do we have the Google Calendar right here and now. 13:20.770 --> 13:21.650 What we can do. 13:21.770 --> 13:25.330 We need to do the same stuff with start and end date. 13:25.570 --> 13:28.570 Additionally, we can firstly pick the calendar. 13:28.690 --> 13:31.690 So this is my email hover for now. 13:31.690 --> 13:34.970 Again what we do we provide two curly brackets. 13:35.290 --> 13:35.890 Let's delete it. 13:35.890 --> 13:37.650 Firstly two curly brackets. 13:37.750 --> 13:41.670 We provide our dollar sign and we type from I. 13:41.830 --> 13:49.430 We can just simply choose the method and then just go over with Start date and just paste it. 13:49.430 --> 13:52.950 Just copy it paste it here and just type end date. 13:54.950 --> 13:57.070 So we'll see if that works. 13:57.390 --> 14:04.630 But for now the last step is to customize our agent because we need to remember we duplicated like this 14:04.670 --> 14:05.150 agent. 14:05.150 --> 14:07.670 And we've got the instructions from the previous one. 14:07.670 --> 14:08.710 So let's delete it. 14:08.750 --> 14:10.950 We don't need to have like system message. 14:11.270 --> 14:19.670 Um so in general we can also type connected chart trigger note without um the system message. 14:20.590 --> 14:23.150 Um and for this case like let's delete it. 14:23.670 --> 14:26.310 For this case we can test this step. 14:26.310 --> 14:27.790 So let's test the step. 14:28.510 --> 14:30.630 Obviously we need to provide the variable. 14:30.630 --> 14:34.110 So instead of connected chart trigger note will have defined below. 14:34.390 --> 14:36.650 And we need to take our um. 14:36.650 --> 14:36.890 Here. 14:36.890 --> 14:38.650 We've got the output from planner. 14:38.970 --> 14:43.730 We don't want to have an output that we had with the connected chart trigger node, because we are taking 14:43.730 --> 14:45.050 just chart input. 14:45.090 --> 14:48.970 Nevertheless, for here we want to have the output from the previous agent. 14:49.370 --> 14:51.250 So again let's click on the step. 14:51.250 --> 14:54.930 And now let's wait until it finishes its job. 14:56.010 --> 14:57.050 So it's done. 14:57.050 --> 14:59.450 And now let's see how it performed. 14:59.490 --> 15:01.170 Let's go ahead to the Google Calendar. 15:01.530 --> 15:05.250 And we've got there our meeting from 5:00 PM to 6:00 pm. 15:05.730 --> 15:14.250 Uh, when we go ahead to our automation, you can see at 5:00 pm on June 14th, 2025, it's nice. 15:14.410 --> 15:17.170 However, the point is, let's see what happens right there. 15:17.530 --> 15:20.090 So it didn't actually, uh, yeah. 15:20.130 --> 15:23.610 It didn't, um, provided the message inside our Gmail. 15:23.650 --> 15:26.690 However, it scheduled the meeting inside the Google Calendar. 15:27.050 --> 15:28.850 So now let's see what's wrong. 15:29.290 --> 15:32.770 So actually I forgot to change the email type to the text. 15:32.970 --> 15:35.600 So everything else is set up correctly. 15:35.600 --> 15:37.160 So let's again what we can do. 15:37.160 --> 15:42.520 Again, we can run the executive agent and see now what happens. 15:42.840 --> 15:44.760 So it should work without a doubt. 15:44.880 --> 15:47.520 However, let's wait again. 15:47.560 --> 15:50.440 It should actually send a message via our Gmail. 15:50.960 --> 15:58.400 So for now actually see in the message I don't have the actually text for sending the email to the person 15:58.400 --> 16:00.400 we are scheduling the meeting with. 16:00.720 --> 16:07.800 So in general to test out if that works, if we don't have any problems in the Gmail node, let's type 16:07.800 --> 16:08.520 the same prompt. 16:08.560 --> 16:11.920 However, let's change for an example the time. 16:11.920 --> 16:20.160 So 7:00 pm and there send the email confirmation to that person. 16:21.640 --> 16:25.120 So we simply test if the entire workflow works. 16:26.320 --> 16:29.760 So after testing our workflow once again we can see it works. 16:29.760 --> 16:32.480 So it sent our email to the customer. 16:32.480 --> 16:36.300 So you need to remember also to be specific when you're typing the message. 16:36.580 --> 16:39.060 You know, to your entire agent. 16:39.460 --> 16:40.940 However, for now it's cool. 16:40.940 --> 16:47.700 And now we can process with the HTTP request because I will be showing you how to exactly how to connect 16:47.700 --> 16:49.500 Dpsk with HTTP request. 16:49.500 --> 16:55.860 And there we've got some differences between connecting IPsec with our agent and HTTP request. 16:55.860 --> 17:00.020 So for now what we can do, we can click right click on the workflow and add the node. 17:00.660 --> 17:02.820 We'll be using HTTP request. 17:03.180 --> 17:07.580 So let's go ahead here and provide the method which is post. 17:08.340 --> 17:15.420 And inside our document I provided for you all of the important information also for them. 17:15.460 --> 17:20.900 For an example, for the Gmail note and calendar note, you've got like these code snippets. 17:21.100 --> 17:27.020 However, for Deep Sea Urban Planner HTTP request, I provided for you the data because we'll be using 17:27.060 --> 17:28.420 URL, which is this one. 17:28.420 --> 17:29.540 We can just copy it. 17:30.340 --> 17:31.480 Let's go over here. 17:31.880 --> 17:32.840 Provide it there. 17:33.000 --> 17:34.760 And now let's see what we need to do. 17:34.800 --> 17:37.960 We need to enable the headers provide the authorization. 17:37.960 --> 17:39.680 So our API key. 17:39.840 --> 17:44.560 Send the body and specify the JSON body to connect our HTTP request. 17:45.040 --> 17:50.080 And then you can find this information inside the Deepsee documentation. 17:50.240 --> 17:51.720 So you've got everything here. 17:52.000 --> 17:57.480 The exact URL you need to use um model you can use actually you know, all of the variables. 17:58.200 --> 18:01.200 Um, so, you know, you can go over here and just look. 18:01.240 --> 18:03.240 Also we'll be using this JSON code. 18:03.560 --> 18:09.040 So this is just a disclaimer that remember actually to every time, whenever you've got some problems 18:09.040 --> 18:13.240 to go to the documentation, documentation because you've got all of the data inside there. 18:13.600 --> 18:18.320 For the simplicity, I provided, um, information inside the file. 18:18.320 --> 18:23.040 So we don't need to search it, search for it manually, or just rewrite from the video. 18:23.080 --> 18:24.800 You can just copy and paste it. 18:25.200 --> 18:27.600 So let's for now um, yeah. 18:27.640 --> 18:37.420 Send the headers There in the name type, authorization and authorization, authorization and in the 18:37.420 --> 18:37.660 value. 18:37.700 --> 18:39.260 Let's type the bearer. 18:40.100 --> 18:45.940 And here we need to provide our API key that we can copy from our Deepsee platform. 18:45.940 --> 18:50.540 So remember from here um, let me for an example copy this API key. 18:51.500 --> 18:52.060 All right. 18:52.140 --> 18:54.860 We need to set the body using JSON. 18:55.060 --> 19:00.220 And in general let's provide uh where do we have that okay. 19:00.260 --> 19:00.780 Here. 19:00.820 --> 19:02.580 Let's provide our JSON code. 19:02.980 --> 19:07.940 I won't go more in depth when it comes to explaining what happens here. 19:08.140 --> 19:12.260 However, what we've got, um, inside, um, we've got our message. 19:12.380 --> 19:14.100 So here we have the content. 19:14.420 --> 19:20.060 Um, you're a helpful assistant who is tasked with creating a step by step plan of action for a personal 19:20.060 --> 19:20.780 assistant. 19:20.780 --> 19:24.700 So in general, what we have inside, we've got a content for the system. 19:24.700 --> 19:28.290 So this is the system message there the content for the user. 19:28.290 --> 19:29.530 So this is the prompt. 19:29.850 --> 19:30.370 Okay. 19:30.930 --> 19:35.330 And there we've got some specific fields and variables. 19:35.890 --> 19:43.370 And what are the differences between connecting deep skiff node as we as we've done here and HTTP request 19:43.650 --> 19:45.330 with HTTP request. 19:45.370 --> 19:48.970 You have more control over your model. 19:49.170 --> 19:52.490 So inside for example you can see you've got frequency penalty. 19:52.530 --> 19:54.970 You've got max tokens you want to use. 19:55.290 --> 19:58.730 You can enable actually and change the temperature. 19:58.810 --> 20:02.730 So it allows your model to be more predictable or less predictable. 20:03.050 --> 20:04.970 Um you've got top P you know. 20:05.090 --> 20:05.610 Um yeah. 20:05.650 --> 20:06.410 Metric. 20:06.450 --> 20:08.490 You've got the tools, you've got the tool choice. 20:08.610 --> 20:15.490 So everything you have explained inside the documentation and the and the HTTP request is more for developers, 20:15.490 --> 20:21.370 the people that are that want to have, you know, like let's say temperature at, I don't know, at 20:21.370 --> 20:30.630 higher value and just just experiment with different fields for 95% of cases, you want to use this 20:30.630 --> 20:31.070 node. 20:31.830 --> 20:35.750 So yeah, with our agent it's easy to set up. 20:35.750 --> 20:37.070 It's really effective. 20:37.110 --> 20:41.950 Nevertheless, in this video I wanted to show you how you can exactly set up the HTTP request. 20:42.110 --> 20:49.750 So for now, what we can do, um, in general we can go ahead and we can, um, delete this node. 20:50.350 --> 20:54.790 Let's connect it right here, open the chart and now provide some message. 20:54.790 --> 20:58.470 So for example this one very simply. 20:58.470 --> 21:01.750 So we just want to make sure that our HTTP request works. 21:02.430 --> 21:04.390 Um we are waiting for now. 21:04.830 --> 21:06.670 So yeah let's wait a while. 21:07.630 --> 21:11.070 And after some time we can see uh yeah it works. 21:11.070 --> 21:14.430 We've got our content and we've got all of the information. 21:14.430 --> 21:17.190 So we successfully connected HTTP request. 21:17.710 --> 21:20.390 And for this video I can say this is pretty everything. 21:20.510 --> 21:22.070 Thank you for watching this material. 21:22.070 --> 21:25.150 I hope you enjoyed it and I will see you in the next lesson.