Executive Summary

n8n is a workflow automation platform that combines AI capabilities with business process automation.

This report answers a simple question: is n8n.io helping users where they need it most? By analyzing 14,691 forum posts (where users struggle) and 7,209 templates (what solutions n8n offers), we used machine learning to identify patterns in both, then compared them.

The result is a data-driven map showing where user needs align with available resources, where critical gaps exist, and where emerging demand signals future priorities.

Note for readers unfamiliar with clustering or ML terminology: See the Glossary at the end of this document for definitions of technical terms.

How to Use This Information

Product Teams

Prioritize debugging tools (OAuth flow debugger, webhook tester) over more workflow templates. Users need help fixing things, not just building things.

Documentation Teams

The top demand clusters signal where troubleshooting guides would have the highest impact. OAuth alone represents 418 struggling users.

Content/Template Teams

Focus new templates on the emerging AI space (MCP protocol, AI agents, session memory) where demand is growing but supply is thin.

Strategy/Leadership

Use this as a baseline for quarterly tracking. Re-run the analysis to measure whether gaps are closing and spot new emerging demand before it becomes a support burden.

Methodology: Demand-Supply Gap Analysis

This analysis uses a machine learning approach to systematically compare user needs (forum discussions) against available solutions (template library) to identify gaps and alignment opportunities.

• Collect relevant data sources (forum posts, solution templates)
• Cluster the raw text using machine learning algorithms to identify demand and supply patterns
• Label the clusters with descriptive keywords and semantic summaries
• Compare the labeled clusters to reveal gaps, alignments, and emerging trends

Why Dynamic Analysis?

AI and technology markets are evolving faster than traditional research methods can track. By the time a conventional study completes, the landscape has already shifted. This analysis uses an automated pipeline designed for continuous intelligence.

Key capability: The "category mismatch" finding - that users need debugging help while templates offer workflows - emerged from comparing cluster-level patterns across the entire dataset. This structural insight would be invisible to manual analysis of sample posts, and can now be tracked for drift quarter over quarter.

Evolution Tracking: Beyond Point-in-Time Snapshots

A unique strength of this methodology is longitudinal tracking. By running the same clustering algorithm on rolling time windows (e.g., 6-month periods shifted by one quarter), we can observe how demand patterns evolve:

This evolution analysis revealed a critical insight: cluster composition is volatile even when item overlap is high. Posts persist, but the themes they form constantly reorganize. See Finding #6 and Appendix G for detailed trajectory analysis.

Key Outputs

• Demand Map: What users struggle with, sized by volume
• Supply Map: What solutions exist, sized by coverage
• Gap Analysis: Where demand exists without corresponding supply
• Trend Signals: Emerging patterns to monitor

Refresh Cadence

Quarterly re-analysis to track drift and measure gap closure.

Context for Non-Technical Readers

How to Think About "Clusters"

A cluster is simply a group of similar things. When the report says "OAuth Authentication cluster (418 members)," it means 418 forum posts are similar enough in topic/content to be grouped together. They share common keywords (google, oauth, redirect, oauth2, client) and represent a coherent theme - not 418 identical posts, but 418 variations on the same general struggle.

The larger the cluster, the more users share that particular experience. A 418-member cluster is a louder signal than a 50-member cluster.

How to Think About "Keywords" vs "Labels"

Each cluster has two descriptions:

• Keywords (e.g., "google, oauth, redirect, oauth2, client"): The literal terms that appear frequently in that cluster. These are evidence - mathematical output from the analysis.
• Semantic Label (e.g., "OAuth Authentication Flows"): A human-readable interpretation of what the cluster represents. These are meaning - analyst judgment based on the evidence.

How to Think About "Noise"

Noise refers to items that don't fit into any cluster because they're too unique or rare. In this analysis, 41% of forum posts and 44% of templates are "noise." This is normal and healthy - it indicates a diverse community with varied, non-repetitive questions. Noise can also hide emerging patterns: a topic that's "noise" today (too few posts to cluster) could become a cluster next quarter as adoption grows.

Key Findings

1. Demand Exceeds Supply

Demand exceeds supply at a 0.60:1 ratio. Users have 108 distinct problem patterns, but only 65 solution patterns exist in the template library. More importantly, the type of demand (troubleshooting, debugging) doesn't match the type of supply (workflow templates).

2. The Alignment Landscape: Coverage, Gaps, and Everything Between

Comparing demand clusters to supply patterns reveals a spectrum — from genuine alignment (WhatsApp, Calendar) to complete gaps (OAuth, Webhooks). The key insight is that alignment and gaps require different actions.

3. Critical Gaps in Foundational Areas

The three largest demand clusters — OAuth authentication (418 posts), API credential management (395 posts), and webhook configuration (257 posts) — have zero dedicated templates, and documentation coverage appears insufficient based on persistent, high-volume forum activity (needs validation against current docs). Combined, these represent 1,070 users struggling with fundamental platform capabilities.

Recommended Priority Order

4. Emerging Demand Signals Future Needs

Three newer patterns are appearing with significant volume: MCP protocol integration (245 posts), AI agent workflows (142 posts), and AI session memory management (136 posts).

5. Noise Is Normal (And Informative)

41% of forum posts and 44% of templates don't belong to any cluster - they're classified as "noise." This is expected and healthy.

6. Demand is Highly Dynamic

Quarterly evolution analysis reveals that user demand is constantly reorganizing. When analyzing rolling 6-month windows across 2025 (Q1Q2 → Q2Q3 → Q3Q4), we observed significant fluidity in how user needs cluster together.

The Sankey diagram below shows how themes flow and transform across three 6-month windows. Watch for:

• Coalescence: Scattered topics converging into focused themes (e.g., scattered AI discussions → focused "AI Agent" cluster)
• Fragmentation: Large themes breaking into specialized concerns (e.g., "Docker/Setup" dissolving as users graduate to specific integration problems)
• Persistence: "Stable islands" that remain consistent pain points (Google OAuth, Webhooks, WhatsApp)

Why Closing These Gaps Matters

Acting on demand-supply gaps can drive measurable business outcomes:

1. Reduced Support Burden

Each forum post represents a user who couldn't self-serve. The top 5 gaps alone account for ~1,400 support-seeking interactions. Closing these with documentation or tooling could significantly reduce community support volume.

2. Improved Customer Satisfaction & NPS

Users struggling with OAuth (418 posts) or webhooks (257 posts) are experiencing friction at critical moments - often during initial setup or production deployment. Resolving them directly impacts perceived product quality.

3. Reduced Churn Risk

Troubleshooting clusters (29% of all demand) represent users who may abandon the platform if they can't resolve issues. The forum post is often a last resort before giving up.

4. Faster Time-to-Value

Configuration & Setup demand (13%) represents users stuck in onboarding. Reducing this friction accelerates the path from sign-up to first successful workflow - a key product-led growth metric.

5. Community Health & Advocacy

A community where questions get answered (via docs, templates, or guides) breeds advocates. Unaddressed gaps breed frustration and negative word-of-mouth.

6. Strategic Resource Allocation

This analysis replaces gut-feel prioritization with evidence. Instead of debating "should we build more AI templates or fix OAuth docs?" - the data shows OAuth affects 3x more users than any AI-related gap.

Appendices

Appendix A: Visual Analytics

How to Read the Scatter Plots

Important: The scatter plots show forum posts and templates positioned by semantic similarity. Items plotted closer together are more similar in meaning. The X and Y axes are mathematical projections (from high-dimensional space reduced via UMAP) - they don't represent interpretable dimensions like time or category. Look for dense clusters (strong patterns) versus scattered points (diverse/unique items).

Key Observations - Forum Demand

• Dense clusters (OAuth, API credentials, WhatsApp) indicate strong, coherent demand patterns
• Scattered gray points represent 41% noise (unique/unclustered posts) - normal for a diverse community
• Cluster separation shows distinct problem domains with minimal overlap
• Largest clusters are tightly grouped, indicating high semantic coherence

Key Observations - Template Supply

• Fewer, larger clusters compared to forums (65 vs 108) - templates are more focused
• WhatsApp booking is the largest and most cohesive pattern
• AI/RAG patterns show emerging solution areas
• 44% noise indicates many templates are unique or niche use cases

Appendix B: Demand Landscape (Forums)

Overview

• Total forum posts analyzed: 14,691
• Demand clusters identified: 108
• Noise (unclustered posts): 6,057 (41%) - posts too unique to group; see Glossary
• Average cluster size: 80 members
• Largest demand cluster: 418 members
• Date range: January 2025 - January 2026

Top 20 Demand Patterns

Demand Pattern Analysis

Debugging & Troubleshooting (28% of demand)

Users struggling with authentication failures, broken webhooks, connection drops, and workflow execution errors.

• OAuth Authentication Flows (#1, 418 members)
• Webhook Configuration & Testing (#5, 257 members)
• Connection Reliability (#9, 193 members)
• Telegram Bot Triggers (#13, 150 members)
• Execution Performance (#17, 141 members)

Integration (18% of demand)

Questions about connecting to third-party platforms like WhatsApp, Slack, Telegram, and email services.

• WhatsApp Business Integration (#3, 319 members)
• Calendar & Scheduling (#12, 151 members)
• Slack Integration (#19, 134 members)
• Email Triggers (IMAP) (#20, 132 members)

Data Operations (14% of demand)

Issues with reading, writing, transforming, and merging data in Google Sheets, databases, and file formats.

• Google Sheets operations (#4, 279 members)
• Data merging & aggregation (#11, 163 members)
• Binary File Handling (#16, 141 members)

Configuration & Setup (13% of demand)

Help needed setting up API credentials, tokens, and LLM model connections for the first time.

• API credential management (#2, 395 members)
• LLM model setup (#14, 142 members)

Emerging Technologies (13% of demand)

Questions about cutting-edge features like MCP protocol, AI agents, and conversational memory.

• MCP protocol integration (#6, 245 members)
• AI agent workflows (#15, 142 members)
• AI session memory (#18, 136 members)

Workflow Patterns (11% of demand)

Confusion around loops, iterations, branching logic, and data type handling in complex workflows.

• Data type handling (#7, 230 members)
• Loop & iteration patterns (#8, 227 members)

Platform Support (3% of demand)

License activation problems, subscription issues, and self-hosted instance management.

• License & activation (#10, 179 members)

Representative Forum Posts (Exemplars)

1. OAuth Authentication (418 members):

"I'm facing an extremely frustrating and persistent issue with my self-hosted n8n instance. I need help resolving why the OAuth Redirect URL for Google credentials keeps failing..."

"It keeps happening randomly: every few minutes I'm forced to reconnect my Google accounts because the authentication drops..."

2. API Credentials (395 members):

"Snowflake is deprecating the username/password connection. I would like to use a key pair but it's not possible in the Snowflake node..."

"I'm building a multitenant workflow and need to dynamically load a credential inside a Code node based on an incoming clientId..."

3. WhatsApp Business (319 members):

"Does anyone know how to build a connection between webhook and WhatsApp Cloud API?"

"I've been struggling to find a way to send a message to a WhatsApp number and wait for a response directly in the app, without using any external links..."

4. Google Sheets (279 members):

"I cannot update a gsheet row using my N8N scenario. It is supposed to output the emails that are circled..."

"I have my workflow append the final info into Google Sheets. It works most of the time, but sometimes the info just won't append/update..."

5. Webhooks (257 members):

"My webhooks are not working for production. It works in test environment. I have tried multiple webhooks in different flows..."

"I am self-hosting on Proxmox and followed the steps setting the ENV to my domain, yet when I try to use any sort of webhook, the URL has a space..."

Appendix C: Solution Landscape (Templates)

Overview

• Total templates analyzed: 7,209
• Solution patterns identified: 65
• Noise (unclustered templates): 3,156 (44%) - unique/niche templates; see Glossary
• Average pattern size: 62 templates
• Largest solution pattern: 211 templates

Top 20 Solution Patterns

Solution Pattern Analysis

Content & Social Media (26% of templates)

Automated content creation and publishing for LinkedIn, WordPress, YouTube, and podcasts.

• LinkedIn content automation (#2, 166 templates)
• WordPress blog publishing (#5, 159 templates)
• News aggregation (#9, 119 templates)
• YouTube content management (#10, 104 templates)
• Podcast & Audio Processing (#18, 74 templates)

Business Automation (21% of templates)

End-to-end workflows for appointments, HR screening, memberships, and payment processing.

• WhatsApp appointment booking (#1, 211 templates)
• HR recruitment automation (#7, 127 templates)
• Membership & Subscriptions (#16, 86 templates)
• Payment processing (#17, 74 templates)

AI & Machine Learning (12% of templates)

RAG-powered knowledge bases, AI image generation, and video creation with tools like HeyGen.

• RAG knowledge base (#6, 151 templates)
• AI image generation (#14, 90 templates)
• AI video generation (#20, 66 templates)

Communication & Productivity (14% of templates)

Email inbox management, calendar scheduling, and task automation.

• Gmail email management (#3, 166 templates)
• Calendar & task management (#12, 97 templates)

Platform & Infrastructure (11% of templates)

Self-hosted deployment guides and MCP server configuration templates.

• Self-hosted infrastructure (#4, 163 templates)
• MCP support & QA (#13, 96 templates)

Marketing & Sales (8% of templates)

SEO optimization, lead scoring, and CRM integration workflows.

• SEO & search optimization (#11, 103 templates)
• Lead management & CRM (#15, 87 templates)

Data Analysis (5% of templates)

Financial market tracking, crypto analysis, and trading signal automation.

• Financial market analysis (#8, 125 templates)

DevOps & Security (3% of templates)

Vulnerability scanning, IP monitoring, and security alerting workflows.

• Security & vulnerability scanning (#19, 69 templates)

Appendix D: Demand-Supply Alignment

Alignment Overview

• Supply:Demand ratio: 0.60:1 (demand exceeds supply)
• Pattern overlap: Strong alignment in WhatsApp, Calendar, MCP protocol
• Critical gaps: API debugging, webhook configuration, loop patterns
• Emerging alignment: MCP protocol (both demand #6 and supply #13)

Alignment Matrix

Appendix E: Critical Gaps Detail

Gap #1: OAuth Authentication Debugging

Demand: 418 forum members (#1 demand cluster) | Supply: Zero dedicated templates; documentation coverage appears insufficient based on persistent forum volume (needs validation) | Impact: CRITICAL

Root cause: Users struggle with OAuth flows (redirect URIs, token refresh, scope configuration)

Owner: Product + Documentation Teams

Recommended Actions

1. Create "OAuth Troubleshooting Guide" documentation
2. Build "OAuth Flow Debugger" template with common error patterns
3. Add OAuth configuration wizard for Google, Microsoft, LinkedIn

Gap #2: API Credential Management

Demand: 395 forum members (#2 demand cluster) | Supply: Zero dedicated templates; documentation coverage appears insufficient based on persistent forum volume (needs validation) | Impact: CRITICAL

Root cause: Users confused about credential storage, environment variables, secure handling

Owner: Documentation Team

Recommended Actions

1. Create "API Credential Best Practices" guide
2. Build "Credential Vault" template with secure storage patterns
3. Add credential testing/validation workflows

Gap #3: Webhook Configuration & Testing

Demand: 257 forum members (#5 demand cluster) | Supply: Zero dedicated templates; documentation coverage appears insufficient based on persistent forum volume (needs validation) | Impact: CRITICAL

Root cause: Users struggle with webhook URLs, testing in production vs development, payload validation

Owner: Product + Documentation Teams

Recommended Actions

1. Create "Webhook Testing Toolkit" template
2. Build "Webhook Debugger" with request/response inspection
3. Add webhook URL validation and testing workflows

Gap #4: Loop & Iteration Patterns

Demand: 227 forum members (#8 demand cluster) | Supply: Zero dedicated templates | Impact: HIGH

Root cause: Conceptual understanding gap - users don't understand loop node, iteration, batching

Owner: Content Team

Recommended Actions

1. Create "Loop Patterns" template collection
2. Build "Loop Examples" with common use cases (batch processing, pagination, retries)
3. Add interactive loop pattern selector

Appendix F: Quarterly Tracking Framework

Baseline Metrics (January 2026)

Demand (Forums)

• Total clusters: 108
• Total posts: 14,691
• Noise ratio: 41%
• Largest cluster: 418 (OAuth)

Supply (Templates)

• Total patterns: 65
• Total templates: 7,209
• Noise ratio: 44%
• Largest pattern: 211 (WhatsApp)

Alignment

• Supply:Demand ratio: 0.60:1
• Critical gaps: 5 (OAuth, API creds, webhooks, loops, AI memory)
• Strong alignments: 3 (WhatsApp, MCP, Calendar)
• Emerging trends: 3 (AI agents, MCP, RAG)

Quarterly Drift Monitoring

What to track each quarter:

1. New demand clusters: Patterns not present in this baseline
2. Growing demand: Clusters increasing >20% in size
3. New supply patterns: Template clusters added to library
4. Gap closure: Critical gaps addressed with new templates
5. Keyword overlap: Changes in demand-supply keyword intersection

2025 Quarterly Results

Quarterly clustering runs throughout 2025 reveal how demand patterns shift:

Cluster counts vary from 27 to 39 across quarters, reflecting changing user focus areas. Q3 showed peak diversity with 39 distinct demand patterns. See Appendix G for detailed evolution analysis.

Interpretation Guidance

Common Misinterpretations to Avoid

"0 clusters = no resources exist"
Reality: Could mean fragmented usage, not absence of resources. Example: Supabase (0 clusters, 168 templates).

"High forum activity = documentation failure"
Reality: Could mean complexity, troubleshooting, or discovery gaps. Example: OAuth (418 posts, docs exist, users hit errors).

"Noise is bad clustering"
Reality: Noise is expected for unique/rare items. 41% forum noise is normal for a diverse community.

"More clusters = better coverage"
Reality: Fewer, larger clusters often indicate stronger patterns. 65 focused template patterns are more actionable than many fragmented micro-clusters.

Validation Checklist

Before acting on any gap:

• Documentation exists for this topic?
• Forum posts are errors or questions?
• Existing docs address the pain points?
• Templates would help or is it a docs issue?
• Is this a discovery problem (resources exist but unfindable)?

Appendix G: Demand Evolution Analysis

User needs in automation platforms are not static. By tracking how forum posts flow between topic clusters across 2025, we can see which needs are persistent (requiring ongoing investment) versus transient (trending topics that fade).

The Demand Landscape is Highly Dynamic

We tracked 8,464 forum posts that appeared in multiple 6-month analysis windows to understand how user needs evolve. The results reveal a dynamic marketplace:

How User Needs Move Over Time

Theme Flow: Q1Q2 → Q2Q3 → Q3Q4

The visualization below shows how user questions flow between topic areas across three overlapping 6-month windows. Each column represents a time period; flows show how topics persist, merge, fragment, or dissolve.

Reading the chart: Green flows = stable topics (users asking similar questions over time). Red flows = topics dissolving into unique questions. Blue flows = new topics emerging. Yellow flows = users migrating between related topics.

Persistent Needs: The "Stable Islands"

Despite the overall churn, certain topic areas maintain consistent user attention across all time periods. These "stable islands" represent either:

• Unaddressed pain points — Users keep asking because existing resources don't solve their problems
• Inherently complex topics — Some integrations require ongoing troubleshooting regardless of documentation
• Growing adoption areas — New users continuously encounter the same learning curve

Evolution Patterns to Watch

1. Topic Fragmentation

Some broad topics break apart into specialized sub-topics over time. For example, general "installation issues" fragmented into Docker-specific, npm-specific, and self-hosted deployment topics. This signals maturing user needs—early adopters had generic questions; experienced users have specific edge cases.

2. Topic Coalescence

Scattered questions sometimes coalesce into new recognizable patterns. "Account and workspace" questions emerged as a distinct cluster mid-year, suggesting growing self-service adoption and associated friction points.

3. Persistent Pain

OAuth authentication, webhook debugging, and loop patterns show growing stable populations—more users are hitting the same walls quarter after quarter. These are the highest-priority gaps for product and documentation investment.

Glossary of Terms

Analysis & Methodology Terms

Cluster: A group of items (forum posts or templates) that share similar meaning or topic. Think of it as a "natural grouping" - like how a pile of mail might naturally sort into bills, advertisements, and personal letters.

Clustering: The automated process of finding natural groupings within large datasets. Instead of manually reading 14,000+ forum posts, clustering algorithms identify patterns at scale.

HDBSCAN: Hierarchical Density-Based Spatial Clustering of Applications with Noise. The specific clustering algorithm used in this analysis. It excels at finding groups of varying sizes without requiring a pre-specified number of groups.

BERTopic: A topic modeling technique that extracts the most representative keywords for each cluster. It answers "what is this group about?" by identifying statistically significant terms.

Noise: Items that don't fit into any cluster because they're too unique or rare. In this analysis, 41% of forum posts and 44% of templates are "noise" - this is normal and indicates healthy diversity.

Semantic Similarity: How close two pieces of text are in meaning, regardless of exact wording. "My OAuth token expired" and "Google authentication stopped working" are semantically similar even though they share few words.

UMAP: Uniform Manifold Approximation and Projection. A technique that reduces complex data into a simpler form that can be visualized. Think of it as creating a 2D map from high-dimensional data.

Exemplar: A representative example from a cluster - the post or template that best illustrates what the entire group is about.

Demand & Supply Framework Terms

Demand: In this report, user needs as expressed through forum posts - questions asked, problems reported, and help requested.

Supply: Available solutions in the form of workflow templates in the n8n template library.

Demand-Supply Gap: An area where significant user demand exists but corresponding solutions (templates, documentation, or tooling) are missing or inadequate.

Alignment: The degree to which supply patterns match demand patterns. Strong alignment means users asking questions have corresponding resources available.

n8n & Integration Terms

n8n: An open-source workflow automation platform that allows users to connect different apps and services to automate tasks. Pronounced "n-eight-n."

Workflow: A series of automated steps that move data between services or perform actions.

Template: A pre-built workflow that users can import and customize rather than building from scratch.

OAuth: Open Authorization. A secure standard that lets users grant apps (like n8n) limited access to their accounts (like Google) without sharing their password.

Webhook: A way for one application to send real-time data to another when an event occurs - like a notification system between apps.

MCP: Model Context Protocol. An emerging standard for AI applications to communicate and share context with each other.

RAG: Retrieval-Augmented Generation. A technique where an AI first searches a knowledge base for relevant information, then uses that context to generate a more accurate response.

Analysis methodology and report by Andrew Hay
linkedin.com/in/andrewcdhay