Hi everyone.
Welcome back.
In the last lesson we explored webhooks.
Learning how they help trigger workflows in real time without constantly checking for updates.
Today we're going deeper into core nodes in N810.
Some nodes are used in almost every automation, so mastering these core nodes will help you create
cleaner, more efficient workflows.
By the end of this lesson, you will know the most frequently used core nodes in N810 how to modify,
clean, filter and aggregate data.
How to manipulate multiple data items at once.
How to apply these nodes in real world automation.
We will go through them quickly to provide an overview, as we will use these these nodes in practice
in the upcoming lessons.
First, the Edit Fields node.
Often called the set node, is a must have when working with data in N810.
This node helps you organize data, so clean format and structure information before passing it to other
nodes.
Here is what you can do with it.
Rename fields.
Change field names to make them more readable.
Format text.
Convert text to proper case.
Uppercase or lowercase to maintain consistency.
Remove unnecessary fields.
Keep only the data you actually need.
Making workflows cleaner and faster.
Add new fields.
Create additional fields with calculated values or custom formatting.
Let's say you receive customer data from a form, but names are all in lowercase.
You don't want messy data in your CRM, right?
With the Edit Fields node, you can automatically capitalize names before saving them.
Always clean and format your data early in the workflow.
This prevents issues later when processing or sending data to apps like Google Sheets, CRMs or databases.
So the Edit Fields node allows you to add, remove or modify fields in your data.
For example, if you're working with customer data, you can use this node to combine first and last
names into a single full name field.
Remove unnecessary fields to keep your data clean.
Format data for example converting text to uppercase or lowercase.
Clean data is crucial for smooth workflows, so edit fields.
Node helps you ensure that only the relevant data moves through your workflow, reducing complexity
and errors.
The best practice is to use this node when you need to clean, rename, or restructure data before passing
it to other nodes.
Ensuring workflows remain organized and efficient.
Next is, uh, is the aggregate node.
This node is perfect for combining data from multiple items into a single output.
Group data combine multiple items into one based on a specific field.
For example, all signups from the same company.
Remove duplicates.
Keep only unique values.
Summarize numbers.
Find totals, averages, or other stats.
For example.
Total sales.
Merge multiple values instead of separate rows.
Store them as a single list.
What does it do?
The aggregate node takes multiple items, like a list of emails, and helps you combine them into one.
For example, if you have a list of customer emails, you can aggregate them into a single list for
easier processing.
Or imagine you're handling a list of customer orders or survey responses.
Instead of processing each one separately, you might want to group them together or summarize the data
before the next action within the workflow.
For example, instead of sending ten separate slack messages for ten new signups, you can combine them
into one message with a list of all emails.
Or instead of storing each individual sales transaction, you can calculate the total revenue for the
day.
Why is it useful?
This note is especially helpful when you are dealing with large data sets or need to summarize data.
For instance, you can aggregate all signups from a week and send a single slack message with the results.
Now, the best practice is to use the aggregate node to simplify workflows by grouping, summarizing,
or deduplicating data before passing it to other nodes, which help reduce redundancy.
Now let's talk about one of the most essential notes in automation the if node.
The if node helps you add logic and decision making to your workflows.
Instead of running every step blindly.
This node checks conditions and determines what should happen next.
What does it do?
The if node acts like a traffic controller for your workflow.
You can use this node to check if a condition is met.
If true, the workflow follows the yes so true path.
It routes data based on conditions.
If false, it follows the no so false path.
Also, it helps you filter and control execution flow and consequently prevents unnecessary steps from
running.
If they don't meet certain criteria.
So the real world examples could be for example lead qualification, invalid emails ends with add Company.com
send them to the sales team.
otherwise sent them to the marketing team for follow up or for automated email replies, like if a customer's
message contains the word refund, route it to support, otherwise send a standard response.
Now why is it useful?
Workflows often need to branch out based on conditions instead of creating separate workflows for every
case.
The if node keeps everything streamlined by managing different outcomes in a single automation.
Next, we have the switch node.
It's like an upgraded version of the if node.
So instead of just splitting data into true or false, it allows you to define multiple conditions and
route data into different paths.
How it works.
You can use this node to check a field's value, you can evaluate a data field.
For example, status or category.
It's also helpful for comparing against multiple conditions.
Basically, you can define multiple possible values and set unique actions for each.
It will test data accordingly so each match directs the workflow down a different branch.
Now why use it instead of stacking multiple if nodes which can get messy by the way.
The switch node keeps things organized and efficient.
For example, in an order management system, you can route pending orders for approval, send shipped
orders to customers, or handle canceled orders differently.
And the best practice is to use the switch node when dealing with multiple possible outcomes.
To keep workflows clean and avoid unnecessary complexity.
The next very useful node in an A10 is.
The merge node is perfect when you need to combine data from different sources in your workflow.
Unlike the aggregate node, which groups multiple items into one.
The merge node allows you to bring together data from two separate sources and align them based on a
matching field.
Let's explain how it works.
First of all, you can use this node to join data from two inputs.
It takes two different sets of data and merges them into one.
Multiple merge strategies.
You can merge by a common key position the first item with the first item or combine.
Everything keeps workflows organized.
Instead of manually mapping data between sources, this node does the heavy lifting for you and I use
it basically?
Often workflows involve fetching data from multiple places instead of handling them separately.
The merge node lets you combine them seamlessly.
For example, you could use this node for combining CRM and payment data.
Let's say a customer's contact details come from a CRM and their payment history comes from stripe.
The merge node links them together by email, creating a complete customer profile.
Or you want to sync leads with LinkedIn profiles.
You collect leads from a form, name, and email.
Later, you fetch the LinkedIn profiles using an API, and thanks to the merge node, you can match
them by name or email.
Enriching your lead data automatically.
Best practice use the merge node when dealing with two data sources that need to be aligned.
Ensuring the workflow process is complete.
Now, sometimes you don't want everything to run instantly.
Maybe you need to pause between steps, wait for a response, or ensure actions happen at the right
time.
That's where the weight loader comes in.
And what this node does delays workflow execution.
So instead of running the next step immediately, it waits for a specified time.
It allows for flexible timing options, which means you can set a delay of minutes, hours, days,
or even a specific date and time.
Wait for conditions.
Hold execution until another event happens.
For example, wait until a payment is received before sending a confirmation email.
Practical use cases could be, for example, follow ups and reminders.
So imagine a scenario where a customer signs up and you can set up your workflow to wait 24 hours.
Send a follow up email or some API's.
Limit how often you can send requests.
So instead of triggering 100 API calls at once, space them out every few seconds.
The best practice is to use the wait node whenever you need to delay an action.
Whether it's sending emails, triggering notifications, or pacing API calls.
Now most of the time anything's built in nodes are enough.
But what if you need to manipulate data in a unique way?
That's where you should use the code node.
So what exactly does it do?
It runs JavaScript inside an A-10.
Therefore, you can use it to modify, transform or generate data before passing it to the next node.
This node works with JSON and APIs.
Parse API responses.
Clean up messy data or create custom formats expands workflow capabilities.
If a built in node doesn't do what you need, you can code your own logic.
We already covered the HTTP request and webhook nodes, but let's revise them because they are really
important.
The HTTP request node is one of the most important nodes you need to use this node if your workflow
needs to interact with external services.
It allows you to send and receive data from APIs, making it one of the most powerful nodes in Naa10.
What does it do?
In short, connects to any API, so fetch, update or delete data from third party services.
Works with multiple request types.
You can choose between different methods, get post, and more.
It handles authentication and headers, so supports API keys, OAuth and custom headers.
Good examples could be fetching customer data.
You need to use a Get request to retrieve customer details from a CRM, or sending data to a service.
In that case, you need to use a Post request to create a new record in an external database.
And the best practice is use the HTTP request node whenever you need to pull or send data to a service
that doesn't have a built in integration in N810.
Now we've already covered webhooks, but since it's a core trigger node, it's equally important as
HTTP request node.
Instead of constantly checking for new data.
Quick note let's services push data to N810.
This note triggers workflows instantly, therefore listens for incoming data and starts the automation
as soon as an event occurs.
It also generates a unique URL so can be used in external apps like stripe, slack, CRMs, or Zapier.
Supports different request types, accepts get, post put, and more.
Interesting examples could be when you want to receive a stripe payment event, a customer makes a payment.
In that particular scenario, stripe sends a webhook to Naa10 to process the order.
Or let's say you want to automate slack messages.
So a form is submitted which triggers a webhook that sends a notification to a slack channel.
Always use the webhook node when you need real time automation, like triggering workflows from external
apps and services.
All right, that's it for today's lesson.
I hope you have learned something useful about the most important notes in N810.
See you in the next lesson.
Bye bye.