Add Folder Management Support to n8n Workflow Node

Feature Requests
,
1

Currently, there is no n8n node that allows managing workflow folders (directories) via automation.

In the n8n UI interface, users can:

  • Create folders

  • Move workflows into folders

  • Organize workflows using a parent directory structure

However, this functionality is not available through built-in workflow nodes.

Missing Functionality

The built-in nodes:

  • Create a Workflow

  • Update a Workflow

  • Get a Workflow

do not support specifying a parentDirectory (or folder ID) when creating or updating a workflow.

This makes it impossible to:

  • Automatically place new workflows into a specific folder

  • Move workflows between folders programmatically

  • Maintain structured workflow organization via automation

  • Fully replicate UI functionality using n8n itself

Expected Behavior

The following capabilities should be supported:

  1. Ability to specify parentDirectory (or folder ID) when creating a workflow

  2. Ability to update/move a workflow into another folder

  3. (Optional) Dedicated node for:

    • Creating folders

    • Updating folders

    • Deleting folders

    • Listing folders

Why This Is Important

  • Enables full CI/CD automation for workflows

  • Required for large-scale workflow management

  • Necessary for infrastructure-as-code setups

  • Currently forces manual UI interaction

Environment

  • n8n version: 2.8.3

  • Deployment type: Docker Self-hosted

  • Database: Postgres

2

hello @osmenog that’s a really great point !

Technically it’s possible already today to create/delete/move folders/wf , so basically do everything the UI provides, and apply them from workflows.

That’s how I’ve built that workflow : Back up n8n workflows to Google Drive while preserving folder structure | n8n workflow template

Basically I’m using the same API endpoints used from the UI, but I use them within a workflow. This is because the native n8n node doesn’t provide the features you mentionned.

But there is still this alternative of consuming the n8n API (undocumented) that is triggered from the UI actions.