WEBVTT 00:00.960 --> 00:09.200 In today's lesson, we are going to talk about two super useful features in any ten being data and editing 00:09.240 --> 00:10.280 output data. 00:10.640 --> 00:16.480 So by the end of this video, you will know how to pin data and why it speeds up workflow building. 00:16.800 --> 00:25.040 How to edit output data to test different scenarios and how to use past execution data for debugging. 00:25.760 --> 00:26.960 Let's jump right in. 00:28.640 --> 00:34.600 When you are building a workflow, you don't want to rerun everything from scratch every time, especially 00:34.600 --> 00:39.240 if some nodes take a while to execute or depend on external services. 00:39.640 --> 00:47.360 So this is where ping data comes in because it saves time by avoiding unnecessary executions. 00:48.120 --> 00:53.800 It prevents making multiple API calls when testing so you can save a lot of money. 00:54.040 --> 01:00.120 If you are using base services and lets you build and test faster with saved data. 01:00.960 --> 01:08.890 For example, if you are using a webhook node instead of sending a request manually Manually each time 01:08.890 --> 01:12.330 you can pin the response and continue testing the next steps. 01:14.690 --> 01:16.170 So how do you pin data? 01:16.890 --> 01:21.450 In this example, I've sent a message in telegram. 01:22.530 --> 01:26.450 So we already have data in the flow. 01:29.930 --> 01:33.250 So after a node runs you need to click. 01:35.850 --> 01:40.490 This pin icon in the output panel. 01:42.930 --> 01:46.930 And you can also simply unpin data. 01:50.610 --> 01:51.650 As by clicking here. 01:56.130 --> 02:01.050 So the blue pin indicator shows that the node's data is locked. 02:01.650 --> 02:08.210 And now every time you run the workflow, the pinned output is used instead of running the node again. 02:10.330 --> 02:14.330 So in that case we have first name and second name. 02:17.700 --> 02:19.500 Now let's go back to our representation. 02:21.700 --> 02:24.860 Lets you manually modify a node's output. 02:25.260 --> 02:27.940 So it's useful for testing different data scenarios. 02:28.340 --> 02:32.060 And you can avoid unnecessary API calls by simulating responses. 02:33.740 --> 02:36.500 Now you can use fast execution data. 02:36.940 --> 02:44.020 So let's say your workflow failed at some point and you need to debug it without recreating the issue. 02:44.820 --> 02:48.380 So you can go to execution History in N810. 02:50.460 --> 02:52.820 Now let's jump into N810 so I can show you. 02:54.460 --> 02:57.580 So in every workflow you have access to editor. 02:58.100 --> 03:02.940 So this is our canvas and two executions. 03:03.260 --> 03:05.700 So you can check the history of the executions. 03:07.500 --> 03:10.500 Actually you can check every execution of the workflow. 03:11.940 --> 03:15.300 So you can select a specific time of the execution. 03:16.460 --> 03:19.260 And you can find the node where the error occurred. 03:21.060 --> 03:22.260 So in this example. 03:27.420 --> 03:31.740 An error was caused by HTTP request node. 03:32.940 --> 03:35.380 When we try to create an audio. 03:41.540 --> 03:45.180 So you can see all the details and find what causes the error. 03:49.780 --> 03:57.820 It really helps with debugging so you can easily fix errors without waiting for new data. 04:00.980 --> 04:02.820 Now let's go back to our presentation. 04:04.220 --> 04:06.420 So you can navigate to Execution History. 04:06.860 --> 04:09.060 Find the node and copy JSON data. 04:09.340 --> 04:12.980 You can pass it into the nodes Edit output section. 04:15.820 --> 04:18.820 And you can copy error data to debug without. 04:19.540 --> 04:27.620 So imagine you have a workflow that listens to a webhook and processes the data and sends a slack message. 04:28.710 --> 04:31.390 Then it updates a record in Google Sheets. 04:31.710 --> 04:39.430 So to speed up testing, you can pin the webhook output to avoid manually triggering it every time. 04:40.310 --> 04:41.510 Edit output. 04:42.550 --> 04:49.990 So to test different responses like handling missing fields, and then you can even use mock data to 04:50.030 --> 04:51.830 simulate various user inputs. 04:53.190 --> 04:54.710 And this saves a lot of time. 04:59.670 --> 05:00.790 Now why you should care. 05:01.950 --> 05:10.790 Because big data makes workflow building faster and prevents unnecessary API calls and editing output. 05:10.830 --> 05:14.190 Lets you test different scenarios without new data. 05:14.630 --> 05:18.910 Also, using past execution data helps debug errors quicker. 05:20.190 --> 05:25.190 So if you start using these features, you'll build workflows faster and debug smarter. 05:28.030 --> 05:28.430 All right. 05:28.430 --> 05:29.870 That's it for today's lesson. 05:30.550 --> 05:33.510 Now you know how to pin data and edit outputs. 05:34.710 --> 05:35.790 See in the next lesson.