WEBVTT 00:00.040 --> 00:00.520 Hi everyone. 00:00.520 --> 00:01.320 Welcome back. 00:02.400 --> 00:05.200 In the last lesson we explored webhooks. 00:05.720 --> 00:12.360 Learning how they help trigger workflows in real time without constantly checking for updates. 00:12.920 --> 00:15.880 Today we're going deeper into core nodes in N810. 00:16.920 --> 00:23.560 Some nodes are used in almost every automation, so mastering these core nodes will help you create 00:23.560 --> 00:25.720 cleaner, more efficient workflows. 00:26.400 --> 00:33.200 By the end of this lesson, you will know the most frequently used core nodes in N810 how to modify, 00:33.240 --> 00:36.000 clean, filter and aggregate data. 00:36.200 --> 00:38.920 How to manipulate multiple data items at once. 00:39.720 --> 00:42.680 How to apply these nodes in real world automation. 00:43.080 --> 00:49.400 We will go through them quickly to provide an overview, as we will use these these nodes in practice 00:49.440 --> 00:50.760 in the upcoming lessons. 00:51.280 --> 00:53.080 First, the Edit Fields node. 00:53.440 --> 00:58.560 Often called the set node, is a must have when working with data in N810. 00:59.240 --> 01:06.300 This node helps you organize data, so clean format and structure information before passing it to other 01:06.300 --> 01:06.820 nodes. 01:07.340 --> 01:08.860 Here is what you can do with it. 01:09.420 --> 01:10.500 Rename fields. 01:10.660 --> 01:12.900 Change field names to make them more readable. 01:13.860 --> 01:15.020 Format text. 01:16.300 --> 01:18.300 Convert text to proper case. 01:18.460 --> 01:21.580 Uppercase or lowercase to maintain consistency. 01:22.500 --> 01:24.140 Remove unnecessary fields. 01:24.620 --> 01:26.660 Keep only the data you actually need. 01:27.140 --> 01:29.620 Making workflows cleaner and faster. 01:30.020 --> 01:31.020 Add new fields. 01:31.660 --> 01:35.860 Create additional fields with calculated values or custom formatting. 01:36.620 --> 01:41.540 Let's say you receive customer data from a form, but names are all in lowercase. 01:41.660 --> 01:44.620 You don't want messy data in your CRM, right? 01:45.140 --> 01:50.060 With the Edit Fields node, you can automatically capitalize names before saving them. 01:50.460 --> 01:54.220 Always clean and format your data early in the workflow. 01:54.620 --> 02:02.760 This prevents issues later when processing or sending data to apps like Google Sheets, CRMs or databases. 02:02.880 --> 02:09.040 So the Edit Fields node allows you to add, remove or modify fields in your data. 02:09.480 --> 02:16.680 For example, if you're working with customer data, you can use this node to combine first and last 02:16.720 --> 02:18.920 names into a single full name field. 02:19.760 --> 02:22.520 Remove unnecessary fields to keep your data clean. 02:23.440 --> 02:28.040 Format data for example converting text to uppercase or lowercase. 02:28.200 --> 02:34.000 Format data for example converting text to uppercase or lowercase. 02:34.160 --> 02:38.520 Clean data is crucial for smooth workflows, so edit fields. 02:38.560 --> 02:45.680 Node helps you ensure that only the relevant data moves through your workflow, reducing complexity 02:45.680 --> 02:46.480 and errors. 02:46.720 --> 02:54.080 The best practice is to use this node when you need to clean, rename, or restructure data before passing 02:54.080 --> 02:55.200 it to other nodes. 02:55.520 --> 02:59.040 Ensuring workflows remain organized and efficient. 02:59.080 --> 03:01.820 Next is, uh, is the aggregate node. 03:02.540 --> 03:07.260 This node is perfect for combining data from multiple items into a single output. 03:08.340 --> 03:13.620 Group data combine multiple items into one based on a specific field. 03:13.860 --> 03:17.020 For example, all signups from the same company. 03:18.100 --> 03:19.380 Remove duplicates. 03:19.540 --> 03:21.140 Keep only unique values. 03:21.340 --> 03:22.500 Summarize numbers. 03:23.300 --> 03:26.420 Find totals, averages, or other stats. 03:26.460 --> 03:27.100 For example. 03:27.140 --> 03:28.060 Total sales. 03:29.180 --> 03:32.820 Merge multiple values instead of separate rows. 03:33.060 --> 03:34.900 Store them as a single list. 03:35.340 --> 03:36.260 What does it do? 03:36.700 --> 03:43.380 The aggregate node takes multiple items, like a list of emails, and helps you combine them into one. 03:43.980 --> 03:50.500 For example, if you have a list of customer emails, you can aggregate them into a single list for 03:50.500 --> 03:51.580 easier processing. 03:52.140 --> 03:57.740 Or imagine you're handling a list of customer orders or survey responses. 03:58.020 --> 04:04.950 Instead of processing each one separately, you might want to group them together or summarize the data 04:04.990 --> 04:08.270 before the next action within the workflow. 04:08.310 --> 04:15.590 For example, instead of sending ten separate slack messages for ten new signups, you can combine them 04:15.590 --> 04:18.510 into one message with a list of all emails. 04:19.270 --> 04:25.590 Or instead of storing each individual sales transaction, you can calculate the total revenue for the 04:25.590 --> 04:25.990 day. 04:26.950 --> 04:28.230 Why is it useful? 04:28.550 --> 04:35.550 This note is especially helpful when you are dealing with large data sets or need to summarize data. 04:35.830 --> 04:42.830 For instance, you can aggregate all signups from a week and send a single slack message with the results. 04:42.990 --> 04:49.670 Now, the best practice is to use the aggregate node to simplify workflows by grouping, summarizing, 04:49.670 --> 04:55.630 or deduplicating data before passing it to other nodes, which help reduce redundancy. 04:58.030 --> 05:03.690 Now let's talk about one of the most essential notes in automation the if node. 05:04.450 --> 05:08.530 The if node helps you add logic and decision making to your workflows. 05:08.930 --> 05:11.170 Instead of running every step blindly. 05:11.530 --> 05:15.690 This node checks conditions and determines what should happen next. 05:16.370 --> 05:17.410 What does it do? 05:17.690 --> 05:21.770 The if node acts like a traffic controller for your workflow. 05:21.970 --> 05:25.490 You can use this node to check if a condition is met. 05:25.730 --> 05:30.010 If true, the workflow follows the yes so true path. 05:30.290 --> 05:32.410 It routes data based on conditions. 05:33.250 --> 05:36.890 If false, it follows the no so false path. 05:37.410 --> 05:43.930 Also, it helps you filter and control execution flow and consequently prevents unnecessary steps from 05:43.930 --> 05:44.450 running. 05:44.690 --> 05:46.890 If they don't meet certain criteria. 05:47.370 --> 05:55.330 So the real world examples could be for example lead qualification, invalid emails ends with add Company.com 05:55.890 --> 05:57.770 send them to the sales team. 05:58.790 --> 06:06.510 otherwise sent them to the marketing team for follow up or for automated email replies, like if a customer's 06:06.510 --> 06:15.590 message contains the word refund, route it to support, otherwise send a standard response. 06:16.830 --> 06:19.190 Now why is it useful? 06:20.990 --> 06:29.270 Workflows often need to branch out based on conditions instead of creating separate workflows for every 06:29.310 --> 06:29.870 case. 06:31.230 --> 06:38.350 The if node keeps everything streamlined by managing different outcomes in a single automation. 06:38.470 --> 06:40.150 Next, we have the switch node. 06:40.950 --> 06:43.270 It's like an upgraded version of the if node. 06:43.550 --> 06:51.550 So instead of just splitting data into true or false, it allows you to define multiple conditions and 06:51.550 --> 06:53.750 route data into different paths. 06:54.390 --> 06:55.350 How it works. 06:55.550 --> 07:00.730 You can use this node to check a field's value, you can evaluate a data field. 07:00.930 --> 07:03.250 For example, status or category. 07:03.690 --> 07:07.610 It's also helpful for comparing against multiple conditions. 07:08.370 --> 07:14.370 Basically, you can define multiple possible values and set unique actions for each. 07:15.090 --> 07:21.010 It will test data accordingly so each match directs the workflow down a different branch. 07:21.570 --> 07:28.450 Now why use it instead of stacking multiple if nodes which can get messy by the way. 07:28.890 --> 07:32.650 The switch node keeps things organized and efficient. 07:33.050 --> 07:40.930 For example, in an order management system, you can route pending orders for approval, send shipped 07:41.730 --> 07:45.970 orders to customers, or handle canceled orders differently. 07:46.650 --> 07:52.970 And the best practice is to use the switch node when dealing with multiple possible outcomes. 07:53.650 --> 07:57.590 To keep workflows clean and avoid unnecessary complexity. 07:57.790 --> 08:00.550 The next very useful node in an A10 is. 08:00.550 --> 08:07.830 The merge node is perfect when you need to combine data from different sources in your workflow. 08:08.390 --> 08:12.670 Unlike the aggregate node, which groups multiple items into one. 08:13.150 --> 08:20.070 The merge node allows you to bring together data from two separate sources and align them based on a 08:20.070 --> 08:20.990 matching field. 08:21.150 --> 08:22.790 Let's explain how it works. 08:23.670 --> 08:27.670 First of all, you can use this node to join data from two inputs. 08:28.710 --> 08:32.630 It takes two different sets of data and merges them into one. 08:33.750 --> 08:35.390 Multiple merge strategies. 08:36.230 --> 08:42.790 You can merge by a common key position the first item with the first item or combine. 08:42.790 --> 08:46.630 Everything keeps workflows organized. 08:48.710 --> 08:55.710 Instead of manually mapping data between sources, this node does the heavy lifting for you and I use 08:55.710 --> 08:57.650 it basically? 08:58.010 --> 09:05.130 Often workflows involve fetching data from multiple places instead of handling them separately. 09:05.370 --> 09:08.490 The merge node lets you combine them seamlessly. 09:08.650 --> 09:13.370 For example, you could use this node for combining CRM and payment data. 09:14.050 --> 09:23.930 Let's say a customer's contact details come from a CRM and their payment history comes from stripe. 09:24.570 --> 09:30.010 The merge node links them together by email, creating a complete customer profile. 09:30.650 --> 09:33.330 Or you want to sync leads with LinkedIn profiles. 09:34.250 --> 09:36.970 You collect leads from a form, name, and email. 09:37.890 --> 09:44.850 Later, you fetch the LinkedIn profiles using an API, and thanks to the merge node, you can match 09:44.850 --> 09:46.170 them by name or email. 09:47.650 --> 09:50.090 Enriching your lead data automatically. 09:50.810 --> 09:58.070 Best practice use the merge node when dealing with two data sources that need to be aligned. 09:58.110 --> 10:00.310 Ensuring the workflow process is complete. 10:01.950 --> 10:05.870 Now, sometimes you don't want everything to run instantly. 10:06.590 --> 10:12.430 Maybe you need to pause between steps, wait for a response, or ensure actions happen at the right 10:12.470 --> 10:12.910 time. 10:13.470 --> 10:15.230 That's where the weight loader comes in. 10:15.390 --> 10:18.910 And what this node does delays workflow execution. 10:19.550 --> 10:25.430 So instead of running the next step immediately, it waits for a specified time. 10:26.070 --> 10:33.790 It allows for flexible timing options, which means you can set a delay of minutes, hours, days, 10:33.790 --> 10:35.510 or even a specific date and time. 10:36.630 --> 10:37.910 Wait for conditions. 10:38.910 --> 10:41.830 Hold execution until another event happens. 10:41.830 --> 10:46.470 For example, wait until a payment is received before sending a confirmation email. 10:47.030 --> 10:51.470 Practical use cases could be, for example, follow ups and reminders. 10:51.670 --> 10:59.250 So imagine a scenario where a customer signs up and you can set up your workflow to wait 24 hours. 10:59.290 --> 11:02.250 Send a follow up email or some API's. 11:02.290 --> 11:04.690 Limit how often you can send requests. 11:04.930 --> 11:11.250 So instead of triggering 100 API calls at once, space them out every few seconds. 11:12.330 --> 11:16.770 The best practice is to use the wait node whenever you need to delay an action. 11:17.050 --> 11:22.330 Whether it's sending emails, triggering notifications, or pacing API calls. 11:24.770 --> 11:28.090 Now most of the time anything's built in nodes are enough. 11:28.290 --> 11:31.730 But what if you need to manipulate data in a unique way? 11:32.330 --> 11:34.690 That's where you should use the code node. 11:35.450 --> 11:37.970 So what exactly does it do? 11:38.690 --> 11:40.930 It runs JavaScript inside an A-10. 11:41.250 --> 11:48.290 Therefore, you can use it to modify, transform or generate data before passing it to the next node. 11:49.090 --> 11:51.690 This node works with JSON and APIs. 11:52.050 --> 11:53.610 Parse API responses. 11:53.970 --> 11:59.380 Clean up messy data or create custom formats expands workflow capabilities. 12:00.180 --> 12:04.780 If a built in node doesn't do what you need, you can code your own logic. 12:05.060 --> 12:11.300 We already covered the HTTP request and webhook nodes, but let's revise them because they are really 12:11.300 --> 12:12.100 important. 12:13.500 --> 12:19.940 The HTTP request node is one of the most important nodes you need to use this node if your workflow 12:19.980 --> 12:22.340 needs to interact with external services. 12:22.700 --> 12:29.740 It allows you to send and receive data from APIs, making it one of the most powerful nodes in Naa10. 12:30.460 --> 12:31.380 What does it do? 12:31.660 --> 12:39.500 In short, connects to any API, so fetch, update or delete data from third party services. 12:40.020 --> 12:42.020 Works with multiple request types. 12:42.220 --> 12:46.980 You can choose between different methods, get post, and more. 12:47.660 --> 12:54.520 It handles authentication and headers, so supports API keys, OAuth and custom headers. 12:54.800 --> 12:58.040 Good examples could be fetching customer data. 12:58.760 --> 13:05.800 You need to use a Get request to retrieve customer details from a CRM, or sending data to a service. 13:06.640 --> 13:12.360 In that case, you need to use a Post request to create a new record in an external database. 13:12.720 --> 13:20.200 And the best practice is use the HTTP request node whenever you need to pull or send data to a service 13:20.200 --> 13:22.840 that doesn't have a built in integration in N810. 13:24.240 --> 13:31.360 Now we've already covered webhooks, but since it's a core trigger node, it's equally important as 13:31.400 --> 13:32.840 HTTP request node. 13:33.640 --> 13:36.320 Instead of constantly checking for new data. 13:36.400 --> 13:39.360 Quick note let's services push data to N810. 13:40.240 --> 13:47.360 This note triggers workflows instantly, therefore listens for incoming data and starts the automation 13:47.360 --> 13:49.040 as soon as an event occurs. 13:49.640 --> 13:59.740 It also generates a unique URL so can be used in external apps like stripe, slack, CRMs, or Zapier. 14:00.740 --> 14:09.100 Supports different request types, accepts get, post put, and more. 14:09.940 --> 14:17.900 Interesting examples could be when you want to receive a stripe payment event, a customer makes a payment. 14:18.420 --> 14:24.900 In that particular scenario, stripe sends a webhook to Naa10 to process the order. 14:25.740 --> 14:28.420 Or let's say you want to automate slack messages. 14:29.620 --> 14:35.780 So a form is submitted which triggers a webhook that sends a notification to a slack channel. 14:36.460 --> 14:43.460 Always use the webhook node when you need real time automation, like triggering workflows from external 14:43.700 --> 14:44.820 apps and services. 14:45.060 --> 14:47.100 All right, that's it for today's lesson. 14:47.220 --> 14:51.460 I hope you have learned something useful about the most important notes in N810. 14:52.100 --> 14:53.180 See you in the next lesson. 14:53.180 --> 14:53.700 Bye bye.