Skip to main content

Auto Generate Descriptive Node Names with AI for Workflow Readability

Workflow preview

Workflow preview
100%
Auto Generate Descriptive Node Names with AI for Workflow Readability preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Auto Rename n8n Workflow Nodes with AI This workflow uses AI to automatically generate clear and descriptive names for every node in your n8n workflows. It analyzes each node's type, parameters, ...

Best for

  • Engineering automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.n8n, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.chainllm, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.if, n8n-nodes-base.form, n8n-nodes-base.stickynote, n8n-nodes-base.stopanderror

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Anan.

Original n8n.io source

1.1 Workflow description

Title
Auto Generate Descriptive Node Names with AI for Workflow Readability
Workflow name
Auto Generate Descriptive Node Names with AI for Workflow Readability

⚡Auto Rename n8n Workflow Nodes with AI✨

This workflow uses AI to automatically generate clear and descriptive names for every node in your n8n workflows. It analyzes each node's type, parameters, and connections to create meaningful names, making your workflows instantly readable.

Who is it for?

This workflow is for n8n users who manage complex workflows with dozens of nodes. If you've ever:

  • Built workflows full of generic names like HTTP Request 2 or Edit Fields 1
  • Struggled to understand your own work after a few weeks
  • Copied workflows from others with unclear node names
  • Spent hours manually renaming nodes one by one

...then this workflow will save you significant time and effort.

Requirements

  • n8n API Credentials: Must be configured to allow listing and updating workflows
  • AI Provider Credentials: An API key for your preferred AI provider (OpenRouter is used currently)

How it works

  1. Trigger: Launch via form (select from dropdown) or manual trigger (quick testing with pre-selected workflow)
  2. Fetch: Retrieve the target workflow's JSON and extract nodes and connections
  3. Generate: Send the workflow JSON to the AI, which creates a unique, descriptive name for every node
  4. Validate: Verify the AI mapping covers all original node names
  5. Apply: If valid, update all node names, parameter references, and connections throughout the workflow
  6. Save: Save/Update the workflow with renamed nodes and provide links to both new and previous versions

If validation fails (e.g., AI missed nodes), the workflow stops with an error. You can modify the error handling to retry or loop back to the AI node.

Setup

  1. Connect n8n API credentials

    • Open any n8n node in the workflow and make sure your n8n API credentials is connected
  2. Configure AI provider credentials

    • Open the "OpenRouter" node (or replace with your preferred AI)
    • Add your API credentials
    • Adjust the model if needed (current: openai/gpt-5.1-codex-mini)
  3. Test the workflow

    • Use Manual Trigger for quick testing with a pre-selected workflow
    • Use Form Trigger for a user-friendly interface with workflow selection

Important notice

If you're renaming a currently opened workflow, you must reload the page after execution to see the latest version, n8n doesn't automatically refresh the canvas when workflow versions are updated via API.

Need help?

If you're facing any issues using this workflow, join the community discussion on the n8n forum.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Save Renamed Workflow Version

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 2 - Prepare LLM Validation Data

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Generate Node Rename Mapping

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 4 - Apply Renamed Nodes Connections

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - Parse LLM Mapping ToJson

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 6 - Extract Workflow Nodes Connections

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 7 - Assemble New Workflow Object

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Validate All Nodes Renamed

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 9 - Build Workflow Version Links

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 10 - Parse Selected Workflow Id

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 11 - Check Trigger Source Type

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 12 - Display Workflow Version Links

Type / Role
n8n-nodes-base.form - form
Config choices
Version 2.3

Block 13 - Set Target Workflow Id

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 14 - LLM Flow Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Post Processing Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Select a Workflow

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 17 - Triggers Section Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Post Processing Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Post Processing Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Triggers Section Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Triggers Section Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Post Processing Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 33 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Auto Generate Descriptive Node Names with AI for Workflow Readability
Complexity advanced
Nodes 33
Categories Engineering, AI Summarization
Author Anan
Published 16 Nov 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/10889/10889.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Auto Generate Descriptive Node Names with AI for Workflow Readability do?

Auto Rename n8n Workflow Nodes with AI This workflow uses AI to automatically generate clear and descriptive names for every node in your n8n workflows. It analyzes each node's type, parameters, ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, AI Summarization use case.