Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
What is this?
Less
More

Memberships

AI Automation Base

428 members • Free

Knox: Build AI · Claude Code

670 members • $29/month

n8n ⭐

1.2k members • Free

Automation Masters

3.9k members • Free

Data and Ai Automations

2k members • Free

AI Automation Base

911 members • Free

Automation University

5.9k members • Free

AI Automation Society

415.1k members • Free

AI Automation Agency Hub

327.2k members • Free

6 contributions to Data and Ai Automations
🚀 Just shipped: BFS Suite (Big For Small) — a multi-agent AI support system built entirely with n8n + RAG
🚀 Just shipped: BFS Suite (Big For Small) — a multi-agent AI support system built entirely with n8n + RAG Here's what I built: 3 specialized AI agents under one roof: → Legal agent — contracts & compliance → HR agent — policies & onboarding → Support agent — FAQs & troubleshooting Every query goes through an AI Router (GPT-4o-mini) that classifies the topic and routes to the right agent in real time. ⚙️ Under the hood: • RAG with pgvector similarity search (Supabase) • Dual access: public web widget vs internal dashboard • Knowledge gap detection — unanswered questions logged automatically • Escalation via Telegram — 3 triggers: low similarity score, explicit user request, or ambiguous routing (Legal/HR overlap) • Human-in-the-loop — when the router's confidence drops below 0.7, the query goes to a human instead of guessing • Full analytics dashboard with live charts • Document upload straight from the dashboard 🛠 Stack: n8n · GPT-4o-mini · Supabase (pgvector) · Netlify · Telegram Bot API 📊 5 workflows: Ingestion → Query → Logging → Upload → Escalation Everything is production-ready — real RAG, real logging, real escalation. Not a toy project. 🔗 GitHub: github.com/Evgeniy1970-ai/bfs-suite 🌐 Live dashboard: charming-sable-0dd4f8.netlify.app Happy to answer any questions about the build — drop them below 👇
🚀 Just shipped: BFS Suite (Big For Small) — a multi-agent AI support system built entirely with n8n + RAG
1 like • 9d
@Justin Connell Great questions, thanks for digging in! 1. Configuration every time? No. Settings are persisted via localStorage (webhook URL, API key, Supabase credentials). One-time setup, everything survives page reloads and browser restarts. 2. Single index.html — backend plans? n8n actually serves as the backend here. It handles all request processing, AI routing, RAG search, logging, and escalation logic. Supabase handles data persistence. So the architecture is: - Frontend: index.html on Netlify (static) - Backend: n8n workflows (5 in total) - Database: Supabase (PostgreSQL + pgvector) - Auth: dual API key model (public for widget, private for dashboard) The real limitation right now is that n8n runs locally with ngrok. Moving n8n to a cloud deployment (n8n Cloud, Railway, or VPS) is the actual next step before going to production — that gives a permanent webhook URL and removes the dependency on a local machine. The localStorage point is fair though — for a multi-tenant SaaS with multiple users per client, server-side session management would be the right move. That's a natural evolution once the product is deployed on cloud infrastructure. 3. Authentication and role-based access? There's already a two-tier access model via API keys: a public key for the embeddable widget (restricted to public documents only) and a private key for the internal dashboard (full document access). It's lightweight but functional for the target market — small businesses. Full login/register with role-based access is the next layer, and it fits naturally into the backend milestone. Demo — absolutely yes. The dashboard is live right now at charming-sable-0dd4f8.netlify.app and the widget is embeddable on any site. Happy to walk through it on the next call. Would love to hear your thoughts on the architecture and where you see it going.
1 like • 8d
@Justin Connell thank you for the invitation! I will endeavour to participate in the call either next week or the week thereafter.
How I automated 5 core restaurant operations with AI agents — modular architecture breakdown
Hey everyone 👋 Finished a portfolio project I'm excited to share — a Restaurant AI Suite that automates 5 core areas of restaurant operations. The problem it solves: Restaurant owners spend hours every week on tasks that can be fully automated — checking reviews, handling bookings, monitoring stock, promoting the menu. This system handles all of it. 🍽️ What it does: → Monitors reputation on Google Maps, TripAdvisor & Yelp — AI sentiment analysis every 6 hours → Handles reservations via Telegram bot — auto-confirms by email, sends reminder 24h before → Recommends menu items daily based on live weather conditions → Checks inventory and sends low-stock alerts before items run out → Analyzes dish photos with AI vision and generates professional menu photos with DALL-E 3 All results go into a live dashboard the owner can check from their phone. 💡 The key design decision: modular architecture. Each agent is an independent n8n workflow. The client can start with 1 agent and add more over time — without touching existing workflows. Need a guest return engine? Delivery bot? Social media poster? Each one slots in as a new agent. This is the approach I use for all client projects now — start small, expand modularly. Full project on GitHub: github.com/Evgeniy1970-ai/restaurant-ai-suite Portfolio: neolithai.netlify.app Has anyone here built automation for HoReCa clients? Would love to hear what challenges you ran into.
How I automated 5 core restaurant operations with AI agents — modular architecture breakdown
1 like • May 5
@Leela Krishna Great question! Telegram is actually the go-to choice for automation workflows for a few solid reasons: API access — Telegram has a free, open and incredibly well-documented Bot API. You can create a bot in 30 seconds via @BotFather and start sending messages programmatically right away. No approval process, no fees. WhatsApp, on the other hand, requires the official WhatsApp Business API — which means going through Meta's approval process, paying per message, and dealing with rate limits and template restrictions. It's designed for enterprise-scale customer communication, not developer automation. Security-wise — Telegram bots communicate over HTTPS and the tokens are straightforward to manage. It's not end-to-end encrypted by default for bots (that's a fair point), but for internal business alerts going to the restaurant owner, it's more than sufficient. For a portfolio project or a small/medium restaurant client, Telegram is simply the most practical choice — fast to set up, free to use, works great with n8n out of the box. That said — if a client specifically needs WhatsApp, it's totally doable via Twilio or the Meta Business API. It just adds cost and complexity. I'd always ask the client what they actually use before deciding.
0 likes • 15d
@Dalvir Ferreira Thank you!
I built a full B2B lead gen pipeline in n8n — one Telegram message triggers everything. Here's the full breakdown
Hey everyone, I just finished a production-ready AI lead generation workflow in n8n and wanted to share the full architecture with the community. Happy to answer questions and hear how you'd improve it. 🔧 What it does (end-to-end): 1. You send a search query to a Telegram bot (e.g. "IT consulting firms Amsterdam") 2. Google Maps Places API returns up to 10 businesses 3. Leads are split, deduplicated across runs (persistent memory), and paginated 4. Prepare Keys node enriches each item with company_name, website, phone, address and generates a company_key for merging 5. Two parallel Serper searches run simultaneously: 6. Two sequential Merge nodes combine everything by company_key 7. Edit Fields normalizes all data into a clean unified object 8. Research Agent (GPT-4o-mini) generates 3 automation opportunities + personalized icebreaker per company 9. JSON Cleaner (Code node) parses the AI response and merges it with contact data 10. Contact Validator scores email/LinkedIn quality (0–100) 11. Lead Scoring calculates total score: corporate email (+40), LinkedIn (+25), website (+15), phone (+10), icebreaker quality (+10) 12. IF Score gates the outreach — only leads ≥ 55 proceed 13. Google Sheets Append logs everything to CRM 14. Email Generator (GPT-4o-mini) writes a personalized cold email 15. Gmail creates a draft → waits 3 days → follow-up draft created → Telegram report sent 🐛 Interesting bugs I hit and fixed: - $json context loss after Serper nodes — fixed by using $('Prepare Keys').item.json.company_key explicitly - websiteUri returning undefined for businesses without a website — fixed with || $json.nationalPhoneNumber || 'unknown' fallback in the key - JSON Cleaner failing with raw.slice is not a function — GPT-4o-mini returns a parsed object, not a string, when json_object mode is enabled - Merge nodes not joining — caused by null company_key on one input branch - Remove Duplicates discarding all items — cleared deduplication history after test runs - - 💡 Key design decisions:
I built a full B2B lead gen pipeline in n8n — one Telegram message triggers everything. Here's the full breakdown
Update: My AI Content Master got a major upgrade!
18 days ago I shared my first automation project here. Since then, I've significantly improved its architecture — and I'm excited to share what's new! What changed: 🗄️ Cross-Workflow Data Bridge: Added Google Sheets as a reliable data layer between Generator and Moderator workflows — seamlessly passing image URLs and multilingual texts between two separate n8n workflows. 🔗 Real LinkedIn Publishing: Connected LinkedIn OAuth2 API — approved posts now go live automatically in the selected language (EN, PL, or ES) with just one tap in Telegram. 📘 Facebook Publishing Ready: Facebook Graph API node is already implemented in the workflow and ready to activate for clients who need it. 📝 Universal Prompt: Removed the archaeology-specific focus — the agent now creates expert content on ANY topic the user sends via Telegram bot. The system now consists of two interconnected n8n workflows — a true agentic architecture! About the Development: This upgrade was co-developed with Claude (Anthropic) as a technical mentor and debug partner. If you're learning AI automation — don't be afraid to iterate and improve. Every upgrade teaches you something new! 🚀 PhD in Archaeology → AI Automation at 55. It's never too late! 👉 See where it all started: https://www.skool.com/data-and-ai/my-first-experience-in-automation?p=76cc6cfe 📂 Full project on GitHub: https://github.com/Evgeniy1970-ai/ai-content-scout
Update: My AI Content Master got a major upgrade!
0 likes • Apr 11
@Godspower Toikumo Thank you!
My first experience in automation
I am excited to share the results of my 3-month journey here. Transitioning from a career as a PhD in Archaeology to building AI systems has been a profound experience. Today, I am presenting my fully functional 'International Content Scout'. What you see on the screen: This is a 'Man-in-the-Loop' architecture built in n8n. - The Creative Core: I send a raw thought via Telegram. The AI Agent (GPT-4o) instantly generates expert content, video scripts, and engagement posts in English, Polish, and Spanish. Simultaneously, DALL-E 3 creates a unique visual for the topic. - The Control Center: The system doesn't post anything without my word. I receive everything in Telegram and use Interactive Buttons to Approve or Decline. - The Execution: Once approved, the content is queued for direct publication via Facebook Graph API and LinkedIn API. About the Development: This project was co-architected with Gemini 1.5 Pro, an advanced AI model from Google. During weeks of collaboration, Gemini acted as a mentor, technical consultant, and debug partner, bridging the gap between scientific methodology and modern AI automation.
My first experience in automation
0 likes • Apr 8
@Rudolf Van Loggerenberg Thank you!
1 like • Apr 8
@Jake Schen I'm happy for you, colleague! What I love about automation is the wide variety of solutions it offers, some of which can be truly amazing. In that sense, automation is similar to scientific work, especially archaeological research.
1-6 of 6
Yevhenii Nohin
3
37points to level up
@yevhenii-nohin-9140
Hi! The modern world is changing so rapidly that I am excited to see what the future holds! I'm really excited to learn how to create AI agents.

Active 6d ago
Joined Jan 30, 2026
Powered by