Beginner n8n course video 5: covers canvas layout, trigger nodes, workflow activation, branching with If and Filter nodes, and builds a contact-filtering workflow.
Key Takeaways
- Every n8n workflow begins with a trigger node, and activation is required for triggers to run in production.
- Branching can be done with multi-output nodes (items take one path) or by fanning out lines (items are duplicated).
- Filter and If nodes are core tools for cleaning data and routing items by condition.
What the video covers
- Introduces the n8n workflow canvas: the workflow menu, name and tags, activation toggle, version history, settings, nodes, and zoom controls.
- Explains that workflow activation pushes a workflow to production so triggers run automatically, and that changes save automatically on activation.
- Describes the workflow menu for finding workflows by tags and owners, and how default ownership is assigned on creation.
- Defines trigger nodes as the starting point of every workflow, recognizable by their orange lightning icon and having only an output branch.
- Shows how double-clicking a node reveals its upstream and downstream neighbors and how to navigate the workflow with the icons.
- Explains two ways to branch: nodes with multiple outputs (items follow one path) and dragging multiple output lines from one node (items are duplicated down every path).
- Demonstrates a Schedule Trigger set to run daily at 8:00 a.m., and notes that manual test runs work without activation.
- Builds a Filter node step that removes contacts with empty email fields, reducing 10 items to 8.
- Adds an If node with OR-combined conditions to separate Gmail and Hotmail addresses from professional email addresses.
- Notes that branch outputs can be accessed separately from the node's output data, with a demonstration of splitting items 5 and 3 across two paths.
Chapters
- 00:00Introduction to core workflow concepts
- 01:00Understanding the workflow canvas and activation
- 01:57Workflow menu, ownership, and settings
- 03:12Nodes, triggers, and navigation
- 04:15Branching: multi-output and fan-out paths
- 05:40Demo: schedule trigger and activation in n8n
- 07:00Demo: filtering contacts without emails
- 09:00Demo: If node branching by email domain
- 11:50Wrap-up and next video preview
Full Transcript — Download SRT & Markdown
Speaker A
hello and welcome to video number five of the beginner course for nen in this video we'll be covering some core workflow Concepts and continue building our first workflow together let's start off by covering some uh important core workflow Concepts
Speaker A
that you'll need to understand before building uh your own workflows here we have uh the canvas so from the canvas we can see the main workflow elements up here we have the workflow menu uh the name and tags associated with that workflow we have
Speaker A
the workflow activation settings here we can also access the version history and workflow specific uh settings up in the top right corner in the middle obviously we have the nodes of the given workflow and we have some Zoom settings uh to the bottom left
Speaker A
activating the workflow is what allows us to push a workflow to production and is what actually allows us to start using the workflow automatically uh we'll cover workflow activation a little bit later in any then and of course in
Speaker A
the Cannabis we have the nodes which are going to be the biding blocks the atoms of our workflow the main workflow menu is where you'll find all the workflows of your Ann instance you'll find information like tags and owners that you can filter
Speaker A
on um you can also find all workflows of which you are the Creator uh by clicking my workflows down here to see only workflows owned by you you can create a workflow uh and every time you do you are going to be assigned as the default
Speaker A
owner from the workflow setting so to the top right of the canvas we can access everything that has to do with workflow accessibility as well as the error workflow and how workflow executions are saved um we'll be covering both error workflows and saved executions in video number seven let's look at how nodes are
Speaker A
connected um and how we actually can create workflows every workflow starts with a trigger node you can recognize them by the fact that they only have an output Branch as you can see here and they have the orange lightning icon next to them a workflow can have
Speaker A
multiple different triggers multiple of the same Trigger or multiple different triggers for more complex use cases and the trigger is what starts the workflow except when testing the workflow it must be activated for the trigger to actually work in the canvas when we double click on a node we can see the nodes before
Speaker A
and after the given node um you can use these little icons to navigate through the workflow as you are building here we have a very simple example uh when clicking execute workflow Google Sheets filter and then an edit Fields node and
Speaker A
by double clicking the filter node we can see to the left Google Sheets and to the right the edit filter node another core topic we need to cover is branching so branching is very important uh when building complex workflows um branches are how we create
Speaker A
different paths or different set of sets of actions depending on different conditions um branches is what allows us to create complex workflows where one workflow is able to cover a large variety of cases and not only one single case we can create branches in two
Speaker A
different ways the first way is we use a node that has multiple output options in this case each item will follow only one of the multiple paths so here for example we have we have an if node and the if node has two outputs true and
Speaker A
false as we can see we have three input items and only one item goes through true and two items go through false so each item only follows one specific path another way to create branches is by dragging two or more output lines from a single node
Speaker A
this means every single item will follow every path and will be duplicated out by the number of paths we'll um see what this looks like in N then in just a minute nodes with multiple output branches will have different sets of
Speaker A
output items obviously um and these can be accessed from the output data of the given node for example here the if node has an output item for items that satisfy the condition and an output item for items that don't satisfy the
Speaker A
condition let's jump into naden and see what all of this looks like so here we are back in nen uh the first thing I'd like to show you is uh triggers and Activation so this workflow that we started building that we execute
Speaker A
manually before reading some information in a Google sheet if we want this workflow to execute let's say every morning at 8 a we could use the schedule trigger and this would allow us to set the uh trigger interval how many
Speaker A
days between each trigger and what hour to trigger at so in this case we would like to trigger every day with you know every one one day as spacing and we're going to trigger it at 8:00 a.m. here you can see we have so multiple Triggers on a given workflow
Speaker A
and here if I want to test the step it is going to execute even though it is not 8:00 a.m. on a given day however if I want to uh once I'm done building this workflow if I wanted to actually run every day at 8 am I have to make sure
Speaker A
that the workflow is activated so when the workflow is activated you will get a confirmation message your schedule trigger will now trigger executions on the schedule you have defined and now I could remove this uh manual step every time you activate a workflow
Speaker A
it will automatically save um so make sure that your uh workflow is ready to be activated before you actually do turn it on so continuing to build this workflow let's add a node after the uh Google Sheets first let's execute so we
Speaker A
have uh the data just as a reminder we have here a list of contacts with their first name last name email and Company so what we'd like to do here is first of all we'd like to remove everyone that doesn't have an email let's say we want
Speaker A
to email all of these people if people do not have an email then there's nothing we can do with them so we are going to use the filter node to filter out every contact that does not have an email so here in the filter node we have
Speaker A
our conditions and here we want to make sure that the email is so email is going to be a string a sequence of letters and characters and we want to make sure that it exists so by executing this step we can see that we went from 10 to 10 items in this
Speaker A
case we can see that even if the email is empty we still have an empty value so in this case the condition would not be exists but rather is not equal to an empty string here if we test this step again we will see that we go down from 10 items in the
Speaker A
input to eight items that were kept and two items that were discarded items that had empty emails so from here on we only have the eight items uh that we want to work with that have emails from here we could think okay maybe we want a different kind of
Speaker A
behavior depending depending on if the uh person has a professional email address or a work email address or a personal email address so here we can add an if node and in the if node we can add some conditions so looking at the Json we see
Speaker A
here a Gmail address some work emails and a hot mail address so our condition here is going to be we want the email to not contain gmail.com this will allow us to filter out the Gmail addresses and as a second step we could filter out so here we see we have gmail. and we
Speaker A
have a hotmail.com so by simplifying this condition by removing the do com we could just remove anything that has at Gmail and we can add a condition when we add a condition uh and so we have two conditions in our if node we have to decide how we want to combine the
Speaker A
conditions here we want to exclude everyone whose email contains at gmail or anyone whose email contain PS at Hotmail and so in this case we're going to be using the or filter so again we drag and drop email and we want it to not
Speaker A
contain hot mail or actually at Hotmail would be better if we test this step so if we test this step we can see that none of the items actually went into the force branch and this is because we are creating the uh branch of
Speaker A
professional email addresses and so we actually should use the and condition the professional email addresses are that they don't contain Gmail and that they don't contain hot mail so here I can test this step here we can see that we have uh
Speaker A
multiple branches so if I were to add a node here and then another one here and I execute again this if node we're going to see five items are going up this branch and three items are going down this Branch if we had uh this allows us to
Speaker A
create these branches where each item of the input is going down only one of these paths if we were to uh just drag another if from the filter node and then maybe just realign things so we can see a bit better and here I execute the filter
Speaker A
node we can see that in this case eight items are going down here and eight items are going down here so by dragging multiple outputs from the same node we duplicate the items down both paths but by creating an if or a set of
Speaker A
conditional branches then we split the items down the different paths thanks for listening to the fifth video of the nend beginner course where we covered some core workflow Concepts and created our first connected nodes in the next video we'll be covering some very useful nodes when building
Speaker A
workflows and we'll keep on building on this workflow to make a more complex example see you in the next video
Topics:n8nworkflow automationtrigger nodeschedule triggerbranchingif nodefilter nodeworkflow activationbeginner tutorialno-code automation











![The ENTIRE History of ROME [No AI] — Transcript](https://i.ytimg.com/vi/EHLI2WZUtXs/maxresdefault.jpg)