WEBVTT 00:01.400 --> 00:02.200 Welcome back. 00:02.840 --> 00:09.720 In this lesson we are going to talk about webhooks, which is a way to receive data in real time and 00:09.720 --> 00:12.040 trigger workflows automatically. 00:12.760 --> 00:17.320 But before we dive in, let's quickly recap the key concepts once again. 00:18.760 --> 00:20.000 So what is an API? 00:20.760 --> 00:26.880 An API stands for Application Programming Interface, which allows different apps to talk to each other, 00:27.360 --> 00:31.720 just like a waiter delivering orders between customers and the kitchen. 00:33.040 --> 00:35.720 Next, what is an HTTP request? 00:36.640 --> 00:43.560 It is a way to talk to other websites and services by sending or receiving data over the internet. 00:44.400 --> 00:48.560 Now why do we need to use the HTTP request node in N810? 00:49.200 --> 00:54.760 We need to use this node to make API calls like asking a service for data. 00:55.120 --> 00:59.880 So in that case we use get method or sending new data to a service. 01:00.640 --> 01:02.880 So we have to use a post method. 01:04.520 --> 01:06.690 Now that we understand API requests. 01:06.730 --> 01:12.930 Let's talk about webhooks, which work differently and are often called reverse APIs. 01:13.970 --> 01:21.050 So in short, a webhook is a way for apps to send data to an A-10 automatically when something happens. 01:21.410 --> 01:28.210 So without needing to check for updates, instead of constantly checking for updates like refreshing 01:28.210 --> 01:30.090 your email inbox every few minutes. 01:30.370 --> 01:35.250 Webhooks notify you automatically when an event happens. 01:38.210 --> 01:41.090 Think of webhooks like a doorbell. 01:41.490 --> 01:46.290 If you are expecting a delivery, you could go check the door every few minutes. 01:47.930 --> 01:52.050 But instead, you could just wait for the doorbell to ring. 01:52.330 --> 01:56.330 And when the delivery arrives, collect the parcel. 01:58.530 --> 02:00.410 And this is called a webhook event. 02:00.850 --> 02:07.650 Basically, webhooks work the same way in N810 because without a webhook, N810 would have to check 02:07.650 --> 02:16.170 every ten minutes for new messages Is in a chat app like WhatsApp or telegram, but with a webhook. 02:16.450 --> 02:21.730 As soon as new message is sent, it instantly triggers a workflow in the A-10. 02:23.050 --> 02:30.050 So use webhooks when you need real time updates, and use API requests when you need to fetch data on 02:30.050 --> 02:30.610 demand. 02:31.210 --> 02:38.610 For example, instead of manually checking stripe for new payments, stripe can send an automatic webhook 02:38.650 --> 02:45.730 to an A-10 whenever a payment is made, so this instantly starts a workflow without any delays. 02:47.730 --> 02:54.810 All right, so now let's talk about how webhooks work in A-10 and why they make automation so much easier. 02:56.010 --> 03:03.450 Webhooks start workflows instantly, which means instead of waiting or constantly checking for updates, 03:03.770 --> 03:08.290 Enitan triggers your workflow the moment something happens. 03:10.170 --> 03:16.140 Next, uses a webhook URL when you set up a webhook in N810. 03:16.580 --> 03:18.780 It generates a unique URL. 03:19.380 --> 03:24.220 This is where another app can send data whenever an event occurs. 03:24.620 --> 03:29.780 Now no more manual checking with regular API calls. 03:29.820 --> 03:33.780 N810 would have to keep asking a service if there is new data. 03:34.140 --> 03:37.500 But with webhooks the data is pushed automatically. 03:37.780 --> 03:42.220 So N810 doesn't need to check over and over again. 03:43.940 --> 03:47.740 Now in N810 you can connect two workflows using webhooks. 03:48.140 --> 03:51.220 Let's jump into N810 so I can demonstrate it to you. 03:51.660 --> 03:53.660 Uh, this particular scenario. 03:54.180 --> 03:55.620 This is the first workflow. 03:56.260 --> 03:57.540 LinkedIn scraper. 03:59.540 --> 04:03.940 So this workflow sends data using the HTTP request node. 04:04.340 --> 04:08.540 So this is like passing information from one workflow to another. 04:08.820 --> 04:12.980 So it sends a Post request to a webhook URL. 04:14.500 --> 04:19.540 And this is the second workflow which receives the data using a webhook node. 04:20.270 --> 04:28.510 So as soon as the webhook gets new data and then instantly starts the workflow and processes all the 04:28.510 --> 04:28.990 data. 04:31.110 --> 04:33.750 So usually the webhook starts the automation. 04:35.510 --> 04:46.590 So if you want to connect two separate workflows into one bigger system, usually the HTTP request node 04:47.150 --> 04:50.110 is the last node in your first workflow. 04:50.990 --> 04:55.070 So in that case to trigger elite qualifier. 04:58.630 --> 05:03.150 And the webhook node is the first node of the second workflow. 05:04.990 --> 05:12.590 So in that case it receives all the data about a LinkedIn user. 05:13.150 --> 05:21.110 Now if you want to set up a webhook in an A-10 from scratch, you just simply click on Add node button. 05:22.150 --> 05:23.230 Search for webhook. 05:26.600 --> 05:34.680 Then if your automation is production ready, you just need to copy this URL and paste it to the HTTP 05:34.680 --> 05:38.280 request node of the of the first workflow. 05:39.320 --> 05:42.680 But for test we copy this URL. 05:43.840 --> 05:46.480 So let's go back to our first workflow. 05:51.640 --> 06:01.280 So you need to copy the webhook URL generated by N810 and paste this URL into the service you are using, 06:02.120 --> 06:03.680 like a stripe or slack. 06:04.920 --> 06:07.080 Or if you want to connect two workflows. 06:09.440 --> 06:15.040 Then you have to paste it into the HTTP request node right here. 06:19.560 --> 06:27.280 Keep in mind that some applications like Stripe or Slack, let you create webhooks manually by pasting 06:27.280 --> 06:35.400 the webhook URL into their settings, but others, like certain CRMs or custom built systems, may require 06:35.400 --> 06:36.680 a bit of configuration. 06:37.160 --> 06:45.960 So if N810 webhook note, you can receive and process this data easily by triggering any automation 06:45.960 --> 06:46.480 you need. 06:47.560 --> 06:50.840 All right, let's quickly recap what we covered in this lesson. 06:51.680 --> 06:59.040 So instead of constantly checking apps, notify N810 the moment something happens thanks to webhooks. 07:01.760 --> 07:08.920 The webhook node generates a URL so all the apps send data to this address whenever an event occurs. 07:10.000 --> 07:17.680 Webhooks trigger workflows automatically, which means as soon as data arrives and it can start processing 07:17.720 --> 07:18.720 it immediately. 07:20.040 --> 07:22.440 And webhooks work with many apps. 07:23.280 --> 07:30.800 Some, like Stripe or Slack, let you paste a webhook URL, but others, like CRMs, may need extra 07:30.800 --> 07:31.360 setup. 07:32.440 --> 07:35.080 I hope it was helpful and see you in the next one.