Node-Bench
Log In

Naming Nodes for Clarity in n8n

Difficulty
1/10
Tags
EssentialsBest PracticeHTTP RequestEdit Fields (Set)JSON

When you build workflows in n8n, nodes start with generic names like "HTTP Request" or "Edit Fields." These defaults work fine for tiny workflows, but as your automations grow, you will find yourself scrolling through dozens of nodes wondering "wait, which HTTP Request was that?"

Descriptive node names are a best practice that pays off immediately. A name like "Fetch User Profile" or "Send Slack Alert" tells you exactly what that node does without having to click on it.

In this challenge, you will work with a completed workflow, execute it to understand what each node does, and then rename the nodes with clear, action-oriented names.

What you'll practice:

  • Understanding workflow logic by executing and observing
  • Renaming nodes with descriptive action names
  • Following the "verb + object" naming pattern

Your Task

A completed workflow is provided that fetches a random user and transforms the data. Your task:

  1. Execute the workflow to see what each node does
  2. Understand the purpose of each node by examining its input and output
  3. Rename each node with a descriptive name that describes its action

Naming guidelines:

  • Use "verb + object" format (e.g., "Fetch User Data", "Extract Key Fields")
  • Be specific about what the node does
  • Keep names concise but meaningful

Current node names to rename:

  • HTTP Request - What data does it fetch?
  • Edit Fields - What transformation does it perform?
  • Edit Fields1 - What is the final output it creates?

There is no strict "correct" answer here. The goal is to practice giving nodes names that make the workflow self-documenting.

Paste into n8n with Ctrl+V

Hints

  1. Execute first: Click "Execute Workflow" and look at each node's output
  2. Double-click to rename: Double-click any node to open its settings, then edit the name at the top. Or select a node and press space.
  3. Think about the action: What verb describes what this node does? (Fetch, Extract, Transform, Format, Filter, Send, etc.)
  4. Include the object: What is the node acting on? (User Data, Random User, User Summary, etc.)

Example good names:

  • "Fetch Random User" instead of "HTTP Request"
  • "Extract User Details" instead of "Edit Fields"
  • "Format User Summary" instead of "Edit Fields1"

Tip: Future-you will thank present-you for clear node names when debugging at 2 AM.

Explanation

Why node naming matters:

In n8n, every node you add gets a generic default name. When your workflow has 3 nodes, this is manageable. When it has 30 nodes, it becomes chaos. Clear node names make workflows:

  • Self-documenting: Anyone can understand the workflow at a glance
  • Easier to debug: Find the problematic step quickly
  • Maintainable: Come back months later and still understand it
  • Collaborative: Team members can work with your workflows

The naming pattern:

The most effective pattern is "Verb + Object":

  • Verb: What action does the node perform? (Fetch, Get, Extract, Transform, Filter, Send, Create, Update, Delete)
  • Object: What is the node acting on? (User Data, Order Details, Email Notification, Slack Message)

Examples from this workflow:

  1. HTTP Request -> Fetch Random User: The node fetches a random user profile from an API. "Fetch" is the action, "Random User" is what we are fetching.
  2. Edit Fields -> Extract User Details: This node pulls out specific fields (name, email, country, age) from the raw API response. "Extract" describes the action of pulling out specific data.
  3. Edit Fields1 -> Format User Summary: This node shapes the data into a readable summary. "Format" indicates we are structuring data for output.

When to rename nodes:

Rename nodes as you build your workflow, not after. It takes 2 seconds to give a node a good name, but minutes to figure out what "Edit Fields3" does in a complex workflow.

Copy the Solution

Click below to copy the solution workflow to your clipboard. Then open n8n and press Ctrl+V anywhere on the canvas to paste it.

Login to see the exercise

Create an account to access challenges and track your progress.

Log in to see exercise