Feature Request: Support for Custom Flow Templates with Directory-Based Categories

[flefevre]

Hello Langflow team 👋

First of all, thank you for the great work on Langflow — especially the support for custom components and their sharable directory-based structure, as described here:
https://docs.langflow.org/components-custom-components#directory-structure-requirements

I would like to request a similar feature, but for custom flows (templates).

Problem / Motivation

Currently, when clicking “New Flow” → “From template”, all available templates are displayed in a flat list.
For teams or advanced users who create many reusable flows, this becomes hard to organize and scale.

For example, I would like to:

• Create custom flow templates

• Share them across a team or environment

• Organize them using a directory / hierarchy structure, instead of a flat list

Proposed Feature

Introduce support for custom flow templates with directory-based organization, similar to how custom components work.

Example:

custom_flows/
├── scientific_watch/
│   ├── arxiv_monitor.json
│   ├── pubmed_alert.json
├── data_extraction/
│   ├── pdf_to_summary.json
│   ├── website_scraper.json

In the UI, this would translate into:

“New Flow” → “From template”

Templates grouped into expandable categories such as:

Scientific Watch

Data Extraction

etc.

Expected Benefits

• Better scalability for organizations and power users

• Easier sharing of best-practice flows

• Improved UX when working with many templates

• Consistency with the existing custom components philosophy

Optional Enhancements (Nice to Have)

• Metadata file (e.g. template.yaml) to define:

• Display name

• Description

Category

Tags

Ability to ship template packs (similar to component packs)

Summary

In short, this feature would allow users to create, organize, and share custom flow templates using a folder-based structure, and have those templates appear in categorized form in the “New Flow from template” UI.

Thanks for considering this request — happy to help or discuss implementation details if needed!

---

Si tu veux, je peux aussi :

Adapter le ton (plus court / plus technique / plus produit)

Ajouter un mock UX

Le reformuler comme une RFC ou une discussion GitHub plutôt qu’un issue