An LLM-based AI agent that generates n8n automation workflows from a single text prompt.
n8n_agent is an LLM-based AI agent designed to generate n8n agentic automation workflows from a single text prompt. It provides tools for vectorizing, analyzing, and storing workflows across multiple databases, enabling semantic search and relationship mapping. The project solves the problem of managing and discovering complex automation workflows by applying knowledge graph and vector search techniques.
Developers and automation engineers who use n8n for workflow automation and need better tools for organizing, searching, and generating workflows. It's also for teams looking to apply AI and advanced data management to their automation stacks.
Developers choose n8n_agent because it combines AI-powered workflow generation with multi-database storage (vector, graph, relational), offering semantic search, validation against best practices, and direct integration with n8n via MCP—all in a self-hosted package.
LLM based AI Agent for generating n8n agentic automation workflows from a one-shot text prompt
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses an LLM-based agent to create n8n workflows from one-shot text prompts, automating complex workflow design as highlighted in the automated generation feature.
Integrates Qdrant for vectorization and similarity matching, enabling semantic search of workflows through MCP tools like 'search_similar_workflows'.
Validates workflows against best practices in naming, error handling, security, performance, and documentation with CLI tools for specific checks and strictness levels.
Supports vector (Qdrant), graph (Neo4j), and relational (Supabase) databases for diverse storage needs, though Neo4j and Supabase are noted as future enhancements.
Requires configuring multiple databases (Qdrant, Neo4j, Supabase) and MCP servers with environment variables, and references absolute paths like '/Users/kinglerbercy/MCP/', making deployment non-trivial.
The README explicitly states that Neo4j and Supabase integrations are 'to be implemented', limiting current functionality to partial database support.
Setup instructions assume specific local paths and lack detailed guidance for portability or troubleshooting, which can hinder adoption in diverse environments.