Create n8n folders from tags

n8n Tag to Folder Migration Automation Overview This workflow automates the process of organizing an n8n instance by converting existing workflow tags into a structured folder system. It systematically creates a folder for each specified tag and moves all workflows associated with that tag into the corresponding new folder. This provides immense value by eliminating the tedious manual task of creating folders and moving hundreds of workflows one by one. It's a powerful utility for tidying up an n8n instance, especially after the introduction of the folder feature, ensuring workflows are organized, easy to find, and consistently managed. Technologies Used - n8n: The workflow is built and executed entirely within the n8n platform. - n8n REST API: The automation relies heavily on direct HTTP requests to the n8n instance's own internal REST API. This is used for advanced operations like user login, fetching projects, listing all tags, creating folders, and updating a workflow's parent folder, which are not all available via standard nodes. - n8n Forms: The workflow is interactive, using two Form nodes. The first acts as a start button, and the second dynamically generates a multi-select list of tags for the user to choose from, providing a user-friendly interface to control the migration process. Node-by-Node Analysis Step 1: Initiation and Authentication The process is initiated manually by the user, who provides their n8n credentials to allow the workflow to operate on their behalf. - On form submission: A simple Form Trigger node that acts as a "Run" button for the user to start the entire process. - set credentials: A Set node where the user must input their n8n instance URL, username, and password. This centralizes the credentials for use throughout the workflow. - login n8n: An HTTP Request node performs a POST to the /rest/login endpoint of the user's n8n instance. This authenticates the user and retrieves a session cookie, which is crucial for authorizing subsequent API calls. - my-projects: This HTTP Request fetches all projects associated with the logged-in user.