Block 1 - Webhook
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 2.1
This workflow is provided as-is. Please review and test before using in production.
n8n Learning Hub — AI Powered YouTube Educator Directory Overview This workflow demonstrates how to use n8n Data Tables to create a searchable database of educational YouTube content. Users c...
n8n-nodes-base.webhook, n8n-nodes-base.datatable, n8n-nodes-base.respondtowebhook, n8n-nodes-base.set, n8n-nodes-base.manualtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.stickynote, n8n-nodes-base.code
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Olusola.
Original n8n.io sourceThis workflow demonstrates how to use n8n Data Tables to create a searchable database of educational YouTube content. Users can search for videos by topic (e.g., "voice", "scraping", "lead gen") and receive formatted recommendations from top n8n educators.
✅ Data Tables Introduction - Learn how to store and query structured data
✅ Webhook Integration - Accept external requests and return JSON responses
✅ Keyword Processing - Simple text normalization and keyword matching
✅ Batch Operations - Use Split in Batches to populate tables efficiently
✅ Frontend Ready - Easy to connect with Lovable, Replit, or custom UIs
The workflow uses a Data Table called n8n_Educator_Videos with these columns:
To create it:
n8n_Educator_Videoshttps://your-n8n.app.n8n.cloud/webhook/1799531d-...)curl -X POST https://your-n8n.app.n8n.cloud/webhook/YOUR-WEBHOOK-ID \
-H "Content-Type: application/json" \
-d '{"topic": "voice"}'
The JavaScript node normalizes search queries:
The Data Table query uses LIKE matching on the Description field, so partial matches work great.
{"topic": "voice"} // Returns Eleven Labs Voice Agent
{"topic": "scraping"} // Returns 2 scraping tutorials
{"topic": "avatar"} // Returns social media AI avatar videos
{"topic": "advanced"} // Returns all advanced-level content
Lovable is an AI-powered frontend builder perfect for quick prototypes.
Prompt for Lovable:
Create a modern search interface for an n8n YouTube learning hub:
- Title: "🎓 n8n Learning Hub"
- Search bar with placeholder "Search for topics: voice, scraping, RAG..."
- Submit button that POSTs to webhook: [YOUR_WEBHOOK_URL]
- Display results as cards showing:
* 🎥 Video Title (bold)
* 👤 Educator name
* 🧩 Difficulty badge (color-coded)
* 🔗 YouTube link button
* 📝 Description
Design: Dark mode, modern glassmorphism style, responsive grid layout
Implementation Steps:
[YOUR_WEBHOOK_URL] with your actual webhookUse Replit's HTML/CSS/JS template for more control.
HTML Structure:
<!DOCTYPE html>
<html>
<head>
<title>n8n Learning Hub</title>
<style>
body { font-family: Arial; max-width: 900px; margin: 50px auto; }
#search { padding: 10px; width: 70%; font-size: 16px; }
button { padding: 10px 20px; font-size: 16px; }
.video-card { border: 1px solid #ddd; padding: 20px; margin: 20px 0; }
</style>
</head>
<body>
<h1>🎓 n8n Learning Hub</h1>
<input id="search" placeholder="Search: voice, scraping, RAG..." />
<button onclick="searchVideos()">Search</button>
<div></div>
<script>
async function searchVideos() {
const topic = document.getElementById('search').value;
const response = await fetch('YOUR_WEBHOOK_URL', {
method: 'POST',
headers: {'Content-Type': 'application/json'},
body: JSON.stringify({topic})
});
const data = await response.json();
document.getElementById('results').innerHTML = data.Message || 'No results';
}
</script>
</body>
</html>
If using Base44 or similar no-code tools:
topic){"topic": "{{topic}}"}{{response.Message}}Category column (Automation, AI, Scraping)Problem: Webhook returns empty results
Solution: Check that the Description field contains searchable keywords
Problem: Database is empty
Solution: Run the "When clicking 'Execute workflow'" branch to populate data
Problem: Frontend not connecting
Solution: Verify webhook is activated and URL is correct (use Test mode first)
Problem: Search too broad/narrow
Solution: Adjust the keyword logic in "Load Video DB" node
Want to learn more about the concepts in this workflow?
By completing this workflow, you now understand:
✅ How to create and populate Data Tables
✅ How to query tables with conditional filters
✅ How to build webhook-based APIs in n8n
✅ How to process and normalize user input
✅ How to format data for frontend consumption
✅ How to connect n8n with external UIs
Happy Learning! 🚀
Built with ❤️ using n8n Data Tables
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Create a searchable YouTube educator directory with smart keyword matching |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Internal Wiki |
| Author | David Olusola |
| Published | 05 Nov 2025 |
Use the JSON export at /data/workflows/10518/10518.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
n8n Learning Hub — AI Powered YouTube Educator Directory Overview This workflow demonstrates how to use n8n Data Tables to create a searchable database of educational YouTube content. Users c...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Internal Wiki use case.