Building Your First Workflow: Hello World

Hello! Welcome to your third lesson.

In our previous session, we did a comprehensive tour of the n8n Editor UI. You now have a mental map of the Canvas, the Node Panel, and the Execution Panel. This foundation is essential, as these are the tools you'll use in every workflow you build.

Today, we transition from theory to practice. The goal of this lesson is to guide you through building your very first automation. We will cover the entire basic development lifecycle: creating the workflow, executing it to see it run, and saving your work. By the end, you will have built a simple "Hello, World!" workflow, a rite of passage for learning any new system.

The "Hello, World!" Workflow

In software development, a "Hello, World!" program is the simplest possible application that produces a tangible output. It confirms that your environment is set up correctly and you understand the basic syntax. We'll apply the same principle in n8n.

Our first workflow will consist of two nodes:

1. A trigger node to start the process.
2. An action node to generate a "Hello, World!" message.

Let's begin.

Step 1: Create and Name Your Workflow

First, create a new workflow from your n8n dashboard by clicking Start from scratch. The first thing you should always do is give your workflow a descriptive name.

For tips on naming, saving, and adjusting initial workflow settings like the time zone, the following short video provides a good overview.

Step 2: Build a Minimalist Workflow

Now, let's add the nodes to the canvas.

1. Add a Trigger: Every workflow needs a trigger. For development and testing, the Manual trigger is perfect. It allows you to start the workflow on demand, just like clicking a "run" button in an IDE.

   • Click the + icon on the canvas.
   • Search for and select the Manual trigger (it may also be named Start or When clicking 'Test workflow'). Add it to your canvas.

2. Add an Action: Now, we need a node to perform an action. The Set node is a fundamental building block used to create or modify data fields. Think of it as declaring and assigning a variable.

   • Click the + icon that appears when you hover over the Manual trigger node.
   • Search for and select the Set node. It will be automatically connected to the trigger.
   • In the Set node's configuration panel, ensure Keep Only Set is turned off. This makes the node add new data to the incoming data, rather than replacing it.
   • Under Values to Set, click Add Value.
   • Choose String.
   • For the Name, enter message.
   • For the Value, type Hello, World!.

Your canvas should now show a simple two-node workflow: Manual -> Set.

Step 3: Execute and Inspect

Now, let's run it.

1. Click the Test Workflow button in the top-right of the canvas.
2. After a moment, both nodes should show a green checkmark, and the Execution Panel will appear on the right, displaying the output of the selected Set node.

You should see the following in the JSON view:

[
  {
    "message": "Hello, World!"
  }
]

Congratulations! You have successfully created and executed your first n8n workflow. You've provided no input data, and the Set node has created a single item containing an object with your message.

A More Interactive Example: A Form Trigger

The manual workflow is great for testing, but most real-world automations are triggered by an external event. Let's create a slightly more complex "Hello, World!" that starts when a user submits a web form. This will show you how input data from a trigger flows through the workflow.

We will use the official n8n quick-start video to guide this process.

First, let's replace our Manual trigger with a form. You can delete the Manual trigger and add an On Form Submission trigger in its place.

Now that you've configured the form, the next step is to test it. This is where you'll see the direct connection between user input and the JSON data inside your workflow.

[
  {
    "userName": "Alex"
  }
]

[
  {
    "userName": "Alex",
    "message": "Hello, World!"
  }
]

Step 4: Saving and Activating Your Workflow

So far, you've been working in a temporary, test environment. To make your workflow "live" and ensure your work is not lost, you need to save and activate it.

• Saving preserves the workflow's structure (the nodes and their settings).
• Activating enables the trigger to run automatically in production. For a form trigger, this means its public-facing URL becomes active.

Remember to save your workflow now!

Conclusion

You have now successfully built, tested, and saved your first n8n workflow. You've experienced the fundamental development loop: adding nodes, executing them, inspecting the data, and making adjustments.

Key Takeaways:

• All workflows start with a trigger node (e.g., Manual, On Form Submission).
• Action nodes (e.g., Set) receive data from previous nodes, process it, and pass it on.
• The Test Workflow button is for development; the Activate toggle makes a workflow live.
• Saving your workflow frequently is essential to preserve your work.
• Inspecting the JSON output in the Execution Panel is the key to understanding and debugging your automations.

In our next lesson, we will delve deeper into the most critical building blocks of any workflow: trigger nodes and action nodes. We'll explore the different types of triggers and clarify their role in defining how and when your automations run.