Auto Generate Descriptive Node Names with AI for Workflow Readability
VerifiedUses AI to automatically generate descriptive names for n8n workflow nodes.
What this workflow does
This automation analyzes every node in an n8n workflow and replaces generic labels with clear, context-aware names generated by an LLM chain and structured parser.
It is intended for n8n users who maintain large or shared workflows and need improved readability without manual renaming.
Who is this for?
n8n power users and automation engineers who build or maintain workflows with many nodes. Also suitable for teams that share or inherit complex automations.
What problem it solves
Generic node names like "HTTP Request 2" or "Edit Fields 1" make large workflows hard to read and maintain over time. Manually renaming every node is slow and inconsistent.
What it automates
Cleaning up imported workflows
Quickly rename all nodes in a workflow copied from the community or a colleague so the logic is immediately understandable.
Documenting production automations
Apply descriptive names before handing a workflow to another team member or before a code review.
Refactoring after iteration
Re-label nodes after many edits so the final structure stays clear without manual cleanup.
How the workflow works
The 3 nodes in this automation, in order.
- 1Basic LLM Chain@n8n/n8n-nodes-langchain.chainLlm
- 2Structured Output Parser@n8n/n8n-nodes-langchain.outputParserStructured
- 3OpenRouter Chat Model@n8n/n8n-nodes-langchain.lmChatOpenRouter
Apps & integrations used
How to set up Auto Generate Descriptive Node Names with AI for Workflow Readability
- 1Import the workflow JSON into your n8n instance
- 2Add your OpenRouter API key in the credentials section
- 3Connect the OpenRouter Chat Model node to the Basic LLM Chain
- 4Attach the Structured Output Parser to receive node-name suggestions
- 5Select or paste the workflow you want to rename into the trigger
- 6Run the workflow and review the generated names before applying them
How to customize this workflow
- →Swap OpenRouter for any other supported chat model
- →Change the trigger from manual to webhook or schedule
- →Add a filter step to skip certain node types
- →Extend the prompt to include custom naming conventions
Auto Generate Descriptive Node Names with AI for Workflow Readability: pros & cons
Pros
- +Saves hours of manual renaming
- +Produces consistent, readable names
- +Works directly inside n8n with existing nodes
- +Beginner-friendly setup
Cons
- –Requires an OpenRouter (or equivalent) API key
- –AI suggestions may still need light human review
- –Only renames; does not refactor logic
Frequently asked questions
It sends each node's type, parameters, and connections to an LLM and returns clear descriptive names that replace the defaults.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…
Similar workflows
Other ai & llm automations worth a look.