Write something
Pinned
Jan 18 •
What do you want / need?
This community is growing faster than ever and I am committing to know *your* needs and wants. Why are you here? What do you want (big picture)? What is the 1 thing stopping you from building your dream *right now*?
Pinned
Jan 17 •
🏆 The January "Build in Public" Challenge
It's time to wake up the machines! 🤖 We are running a leaderboard sprint from now until January 31. The goal is simple: Share what you're building, help others debug, and level up your automation skills. The Prizes (Total Value: $1,000+) 🥇 1st Place: A 1-on-1 "System Architecture" Call with me (We can audit your flows or map out a new project). 🥈 2nd Place: My "Unreleased" Workflow Bundle (Templates I use personally that aren't in the store). 🥉 3rd Place: A comprehensive video audit of one of your n8n workflows. How to Win (Points = Visibility) You get points when other members Like your posts and comments. - Post a Win: Did you finally get that API to connect? Share a screenshot! - Share a Fail: Did you break production? Tell us what happened (we all learn from it). - Help a Peer: Answer a question in the Q&A section. Pro-Tip: The best way to get points is to share value. A post explaining how you solved a problem gets way more likes than a generic "Hello." Why does this matter? This isn't just about points. In the automation world, your portfolio is your resume. - Posting here builds your reputation as an expert. - Answering questions solidifies your own learning. - Building in public attracts opportunities. Current Leaderboard Standings (The ones to beat!): 1 Ms. Niche +16 2 Ros Wei +15 3 Dale James +10 Let’s kick this off: Drop a GIF in the comments that represents your current relationship with n8n (Is it a smooth dance? Or a dumpster fire? 🗑️🔥). GO! 👇
Pinned
Jan 6 •
Live workflow help on the schedule
@David Ashby and I have spun up a separate community to handle all learning and live help that is scheduled on the calendar. You can join the community here. Right now there are 3 types of calendar events: 1. Q&A (free) every Friday, you'll have the floor to come and ask any questions you might have and myself and/or David will be there to assist however we can. 2. Work on your workflows session (free for now) every Tuesday you'll have the floor to come get live help on your workflows that've got you stuck. And if you aren't stuck, but want to optimize or improve an existing workflow, then you can come join in and get some help. 3. Let's talk business (paid) every Wednesday we'll talk about what's going on in your agency or in your freelance work. We'll also address these questions: - Having an issue bidding a project? - Not sure how to talk to a client about a scope change? - Wanting to scale, but not sure how to? - Wandering what the best model for launching a product is? - Just want to listen in and learn? We're excited to take your n8n experience to the next level!
5h •
Built a 5-agent restaurant automation system in n8n — here's the full architecture
Hey everyone 👋 Just wrapped up a project I've been building for the past few weeks and wanted to share it here since this community will appreciate the technical side. I built a modular 5-agent AI system for restaurant automation using n8n. Here's the architecture: 🔧 Tech stack: → n8n v2.6 (self-hosted + ngrok) → Supabase (PostgreSQL) — central database → OpenAI GPT-4o-mini + GPT-4o + DALL-E 3 → SerpAPI (Google Maps, TripAdvisor, Yelp scraping) → OpenWeatherMap API → Telegram Bot + Gmail OAuth2 → HTML/JS dashboard on Netlify ⚙️ The 5 agents: 1. Reputation Manager — scrapes reviews from 3 platforms, runs sentiment analysis, upserts to Supabase 2. Reservations Bot — multi-step Telegram conversation flow with session management in Supabase 3. Weather Menu Promoter — fetches weather, matches menu items by weather_tags, sends Telegram recommendations 4. Inventory Manager — reads stock, builds AI prompt, parses JSON response, sends low-stock alerts 5. AI Menu Photographer — dual mode: GPT-4o Vision analysis OR DALL-E 3 generation, stores in Supabase Storage A few things I learned building this: - Merge node must use Append mode (not Choose Branch) to avoid blocking - Telegram Parse Mode should be removed to prevent MarkdownV2 errors - OpenAI response lives at response.output[0].content[0].text Full workflows on GitHub (sanitized, no credentials): github.com/Evgeniy1970-ai/restaurant-ai-suite Happy to answer questions or discuss the architecture. What would you have built differently?
0
0
Sep '25 •
Welcome to n8n Nodes Automation Lab!
We're glad you're here. Start off in the classroom and make sure to join us for our weekly calls - **NOW Hosted directly within Skool!!** If you've been here, I am including you in this announcement because we have had over 100 new members join this month and there are going to be lots more opportunities to learn, share, teach, and grow together! First Step: https://www.skool.com/n8n-automation-lab/classroom/25b46b59?md=bf827f004026481a85d6b0870d95f9d3
1-30 of 244
Suggested communities
Powered by