Anan
Engineer & Problem Solver.
Templates by Anan
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 Trigger: Launch via form (select from dropdown) or manual trigger (quick testing with pre-selected workflow) Fetch: Retrieve the target workflow's JSON and extract nodes and connections Generate: Send the workflow JSON to the AI, which creates a unique, descriptive name for every node Validate: Verify the AI mapping covers all original node names Apply: If valid, update all node names, parameter references, and connections throughout the workflow 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 Connect n8n API credentials Open any n8n node in the workflow and make sure your n8n API credentials is connected 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) 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.
By AnanAutomatic email notifications for n8n version releases with Gmail
📢 Monitor n8n releases and get notifications for new versions 🆕 This workflow automatically monitors n8n’s release channels (latest and beta) and sends you email notifications whenever a new version is published. It also reads the version of your current n8n instance, allowing you to integrate automatic updates and ensure you never miss a release. Who is this for This workflow is designed for n8n users who want to stay informed and up to date with new releases and features without manually checking for updates, especially those managing their own instances who need to plan upgrades and review release notes. How it works The workflow performs the following steps: Fetches version information from the npm registry (latest and beta releases) Identifies only new versions by deduplication Retrieves release notes from GitHub for any newly detected version Converts Markdown to HTML for email template formatting Sends a styled email notification including the release name, version tag, your current version, and the complete release notes Setup Configure your n8n instance URL (Set myn8nurl) to detect your current version (optional — can be left blank) Connect and authorize the Gmail account used to send emails Update the recipient email address in the Gmail node Requirements A Gmail account for sending emails Customization tips Adjust the schedule trigger if hourly checks are too frequent Modify the release channel (e.g., “latest” or “beta”) if you want to track a different tag Change the npm registry link if you want to monitor a different package Customize the email template/styling in the Gmail node Add additional notification channels (Slack, Discord, etc.) alongside or instead of email Extend this workflow to automatically update your n8n instance when a new release becomes available Need help? If you're facing any issues using this workflow, join the community discussion on the n8n forum.
By Anan