User
Write something
🔒 Q&A w/ Nate is happening in 4 days
Pinned
🚀New Video: STOP Fixing n8n Workflows. Let Claude Code Do It.
In this video, I show you how I built a self-healing automation system using n8n and Claude Code. Whenever one of my n8n workflows throws an error, it automatically triggers an error workflow that calls Claude Code. Claude then uses its n8n MCP server to audit the broken workflow, understand what went wrong, and fix it, all without any manual intervention. I just get a notification that the error was caught and resolved. The next time the workflow runs, it works perfectly because Claude already patched it. It's like having an AI engineer on call 24/7 to maintain your automations.
Pinned
Want to get featured in front of 500,000+ people?
If you've sold an AI automation to a client, any tool, any industry, I want to hear about it. I'm collecting case studies to break down on the channel. This is your chance to build authority, get your brand out there, and showcase what you've built. 🎁 Bonus: I'll be analyzing all submissions and sharing the trends with you: what's selling, which industries are buying, and where the opportunities are. So even if you don't get featured, you'll benefit from the data. 👉 Fill it out HERE Takes 5 minutes. You can submit multiple projects.
Want to get featured in front of 500,000+ people?
Pinned
🚀New Video: Master 95% of Claude Code in 36 Mins (as a beginner)
In this video, I break down everything you need to know to use Claude Code effectively for building automations. I cover the interface and what actually matters, the WAT framework we use to build every automation, how to communicate clearly with Claude Code and get it to ask the right questions during planning, the superpowers like MCP servers and Claude skills, and how to test, optimize, and deploy your workflows so they run automatically. No fluff, I build a real workflow live so you can see exactly how it all comes together. By the end of this video, you'll understand Claude Code better than most people using it and have a clear framework for building your own workflows.
Welcome! Introduce yourself + share a career goal you have 🎉
Let's get to know each other! Comment below sharing where you are in the world, a career goal you have, and something you like to do for fun. 😊
🚨 A quick security reminder about automation workflows
Don’t run workflows from strangers without inspecting every single node first. Whether it’s an n8n workflow, Make scenario, Zap export, or a random JSON someone drops in a Discord or Skool post — blindly importing and running automations is risky. There are bad actors out there. Some are obvious. Some are very good at hiding what they’re doing. I’m sharing workflows to help people learn and move faster — but you should still verify everything before you run anything. Why this matters Automation tools usually have deep access to: - APIs - Databases - Credentials - File systems - Webhooks - Internal business data A single hidden node can: - Exfiltrate credentials - Send your data to a third-party server - Create hidden webhooks - Write or delete database records - Trigger actions on a schedule you never notice And the scariest part? ⚠️ It can look completely harmless at first glance. Good security practices (please don’t skip these) 1️⃣ Inspect every node — no exceptions - Open each node - Check URLs, endpoints, headers, payloads - Look for unfamiliar domains or IPs - Be suspicious of “utility” or “helper” nodes 2️⃣ Verify the source - Who posted it? - Do they explain what it does and why? - Does the workflow come with context or documentation? - Anonymous drops = 🚩 3️⃣ Never import with credentials pre-attached - Remove all credentials before testing - Re-add your own manually - Never trust “ready-to-run” workflows with keys baked in 4️⃣ Test in a sandbox first - Use a dev instance - Use test APIs / fake data - Never run unknown workflows in production first 5️⃣ Watch for outbound traffic - HTTP Request nodes - Webhooks - “Logging” endpoints - Anything sending data “for analytics” If you don’t recognize the destination — investigate. 6️⃣ Least-privilege access - Use limited API keys - Separate prod vs dev credentials - Rotate keys regularly 7️⃣ Assume automation = code No-code does not mean low-risk.
0
0
1-30 of 12,403
AI Automation Society
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
Powered by