User
Write something
🔒 Q&A w/ Nate is happening in 15 hours
Pinned
🚀New Video: Claude Code + Playwright Automates Literally Anything
When you connect Playwright CLI to Claude Code, you can automate almost anything in a browser. This video walks through 3 use cases: having Claude Code QA a web app and fix its own bugs, scraping contact info from search results, and automating actions inside logged-in sessions like Skool. I also show how I'm chaining these scripts into scheduled tasks so an agent runs them on its own.
Pinned
🚀New Video: I Tested GPT 5.5 vs Opus 4.7: What You Need to Know
OpenAI just dropped GPT 5.5 and the benchmarks look strong against Opus 4.7, but benchmarks only tell part of the story. I ran four head-to-head experiments in Codex and Claude Code to see how the models actually compare on speed, cost, and output quality. The results were not what I expected.
Pinned
🏆 Weekly Wins Recap | Apr 18 – Apr 24
From high-ticket deals and agency SaaS launches to client systems, websites, and real-world automations - this week inside AIS+ was packed with serious builder energy. 🚀 Standout Wins of the Week 👉 Michael Wacht closed a $10K AI Readiness Assessment deal, sponsored by finance with training and system-integration readiness included. 👉 @Uros Pesic signed a £9K UK agency client for a 3-month ops audit and used multi-agent Claude Code to prep 20+ interviews in parallel. 👉 @Fernando Gómez turned a corporate social-media automation system into an agency SaaS with €2.5K setup + €100/month per client. 👉 @George Mbajiaku closed his first $1,300 client by shifting his pitch from “n8n builder” to “problem solver.” 👉 @Josh Holladay wrapped a 30-day client sprint and earned a retainer offer for ongoing strategy, builds, and AI education. 🎥 Super Win Spotlight | Balaji Iyer Balaji joined AIS+ knowing he could build something useful - but he needed structure, clarity, and confidence. Since joining, he has: • Set up his own cloud instance, Docker, Postgres, and self-hosted n8n • Built a real backend workflow from scratch • Created an app he now improves daily • Moved from “Can I really do this?” to “How can I make this better?” His biggest shift? Going from sitting on the sidelines → to finally building something he’s proud of. Balaji’s journey is proof that once you take the first step, momentum starts to build. 🎥 Watch Balaji’s story 👇 ✨ Want to see wins like this every week? Step inside AI Automation Society Plus and start building assets that compound 🚀
🏆 Weekly Wins Recap | Apr 18 – Apr 24
🚀New Video: Claude Code + iMessage is Finally Here.
In this video I walk through Claude Code's new iMessage channel, which lets you text your Claude Code session from your phone and have it run tasks like it's sitting at your computer. I cover the full setup process, the current limitations you should know about, and break down the difference between Dispatch, Channels, and Remote Control so you know which one to use.
I use n8n as the entire backend for my SaaS
Most people use n8n to connect Tool A to Tool B. I use it as the entire backend for a SaaS platform. Inboundy (inboundy.app) doesn't have a traditional backend. It runs on n8n as an API Gateway — 8 webhook routes, auth handling, auto onboarding, feature delegation, state management via Supabase, and rate-limiting. All in workflows. The architecture: Frontend → n8n Webhooks → Services → Supabase No Express server. No Flask. No microservices. Just workflows. But the real killer feature isn't the architecture — it's observability. When a request fails, I see exactly which node broke and why. Instantly. No digging through logs, no reproducing bugs locally. The error is right there in the workflow editor. With traditional code — especially AI-generated code — you end up with functions calling functions calling functions. Good luck tracing that when something breaks. I've been there. Hours of debugging code I barely understand, written by an LLM that's already forgotten it wrote it. n8n forces you into a visual structure. You can't hide complexity behind layers of abstraction. Every step is visible. Every failure is traceable. Is it the "right" way to build a SaaS? Probably not. But it shipped in weeks instead of months, it handles real users every day, and when something breaks — I know exactly where. Sometimes the best architecture is the one you don't have to maintain. https://inboundy.app
0
0
1-30 of 16,012
AI Automation Society
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
Powered by