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

Memberships

Vibe Life Labs

4 members • Free

AI Enthusiasts

11.7k members • Free

Empire OS

394 members • $9/month

AI n8n Automation Collective

2.7k members • Free

WotAI

744 members • Free

AI + Automation Lab

964 members • Free

Automation Squad

88 members • Free

AE
Automate Everything

144 members • $1/year

AI Automation Agency Hub

312k members • Free

12 contributions to AutomationForDays
I turned my Agency in a BOX system into a full web app. Any LLM. Self-hosted. Free.
Some of you saw my Agency in a Box project a few days ago. 113+ AI agents, 8 teams, 9 workflows, all running inside Claude Code. The most common response was: "This is insane. But I don't use Claude Code." That's a problem. I built something useful but locked it behind one tool. Not everyone uses Claude Code. Not everyone wants to. People should be able to use whatever they already have. So I rebuilt the whole thing as a web app. AGEX. Same 113 agents. Same 8 teams. Same 9 workflows. But now it runs in your browser, on your machine, with whatever LLM provider you already use. You pick the brain. AGEX is the agency. The biggest problem with AI agent systems right now is that they make you learn how the system works before you can use it. Pick agents from a dropdown. Configure workflows. Connect tools. Build chains. By the time you've set it up, you've spent more time configuring than actually getting work done. AGEX is a conversation. You just talk to it. "Write me cold outreach for selling AI tools to CTOs." It figures out which team is needed, which agents to activate, and delivers the work. No setup. No configuration. No learning curve. Behind the scenes, every agent has a real identity, a specialization, and instructions for when to activate. The system prompt loads all of them into the LLM so it becomes the agency. No frameworks. No chains. Just direct communication between you and 113 specialists. I ran it through 13 tests before shipping. B2B SaaS product launch. D2C fashion brand with a difficult editorial voice. Full stress test with edge cases. Zero failures. The whole thing is self-hosted. Your keys stay on your machine. No telemetry. No accounts. No subscriptions. Clone it, install it, add your key, start talking. Repo: https://github.com/z1fex/AGEX The best tools don't make you learn how they work. They just work the way you already think. You think in conversations. So the interface is a conversation. — Neel
0 likes • 13d
@Clara Boyd Thanks Clara. That was exactly the thinking. If the system only works on one platform, it doesn't matter how good it is. The whole point is accessibility.
Most people don't have a lead magnet. So I built one for you. Repo attached.
Here's the problem with lead magnets. Everyone knows they need one. A playbook. A guide. A checklist. Something you give away for free that makes people go "okay, this person actually knows what they're doing" and then they want to work with you. But nobody makes them. Because making a good lead magnet takes days. You have to research, write, design, brand it, format it. And by the time you're done with one, you've burned a week and you still need five more for different topics. So most people just... skip it. No lead magnet. No free value. No system pulling leads in while they sleep. Here's what I realized. The content already exists. There are thousands of YouTube videos, LinkedIn posts, PDFs, and blog posts covering the exact topics your audience cares about. The ideas are already out there. The research is already done. Someone already said the thing you need to say. You don't need to create from scratch. You need a system that takes that content and turns it into YOUR lead magnet. Your voice. Your brand. Your design. Your CTA at the end. So I built that system. Lead Magnet System In A Box. You feed it any content source. A YouTube video, a LinkedIn post, a PDF, a URL, screenshots, raw text. It reads the content, extracts the core ideas, closes the original, and writes everything from scratch in your voice and your brand. Not a summarizer. Not a copy-paste rebrand. It actually rewrites from zero. Compare the input and the output side by side. Nothing matches. Your version. Your words. Your frameworks. What it generates: Playbooks (visual slide decks, one concept per slide, pixel-perfect). Infographics. Email scripts and DM templates. Social posts. Step-by-step guides. Checklists. All branded with your colors, fonts, and design system. How the pipeline works: 7 stages. Fetch content from any platform. Identify the best output type. Write a full draft in your voice (it loads your brand bible and voice guide before writing a single word). Critique the draft with a second pass. Revise only what the critique flagged. Validate with a Python script, zero AI tokens burned, 100% accurate. Render into branded HTML and PDF.
"Claude Code Sucks At Design." No. Your Prompts Do.
I see this complaint every single week in these communities. Someone opens Claude Code, types "build me a landing page," gets a generic purple gradient template, and says "AI can't design." They're wrong. But I get why they think that. Here's what's actually happening. AI has no taste. That part is true. But here's the thing most people miss: you probably don't either. Not because you're dumb, but because you've never trained your eye to know what good design actually looks like. And if you can't articulate what "good" looks like, how is Claude Code supposed to figure it out for you? Before: I typed "build me a landing page for my automation business." Got the same boring hero section, purple gradients, and generic feature cards that every AI generated site looks like. After: I started showing Claude Code exactly what I wanted. Screenshots of websites I liked. The actual HTML and CSS from sites I wanted to mimic. Specific instructions about colors, typography, spacing, and layout. The output went from "AI template" to "wait, a human didn't build this?" The difference wasn't the tool. It was the input. Here's what I learned works: First, stop prompting blind. Go look at what good actually looks like. Sites like Awwwards, Godly, Dribbble, Pinterest. Spend 30 minutes just scrolling and saving things that catch your eye. You're training your own taste before you train the AI. Second, show, don't just tell. Screenshots beat descriptions every time. If you like how a website handles its hero section, screenshot it and paste it into Claude Code. "Make it look like this" will always outperform "make it look clean and modern." Third, go deeper than the surface. The real unlock is learning to look at the actual code behind websites you admire. Right click, view source. Copy the HTML. Look at the CSS. Feed that context to Claude Code. Now it's not guessing from a screenshot, it's working from the actual blueprint. The gap between people who say "AI can't design" and people who are shipping beautiful sites with AI is not talent. It's not technical skill. It's input quality.
2
0
"Is n8n Dead?" No. But How You Build On It Is About To Change.
Every week I see another post saying automation platforms are dead because AI coding agents exist now. Let me tell you why that take is wrong and what's actually happening. I just built a full lead generation automation in n8n. Scrapes Google Maps, enriches leads with company data, qualifies them, grabs emails through an enrichment API, and drops everything into a Google Sheet. Production ready. The difference? I didn't build it manually node by node. I threw a client transcript into Claude Code, let it analyze the requirements, plan the workflow, and then build the entire thing directly on my n8n account. Node by node. Testing each step. Debugging errors as it went. What would normally take me a few hours took about 30 minutes of steering. But here's the key word: steering. Because this is NOT a magic bullet. I still had to tell it which APIs to use. I still had to correct it when it went down the wrong path. I still had to paste in API documentation when it didn't have the right context. I still had to understand what a good automation looks like so I could catch mistakes. That's why your automation skills still matter. Maybe even more than before. Think about it this way. These AI coding agents are getting really good at execution. They can write code, build nodes, test and debug. But they still need someone who knows what should be built, which approach to take, and when the output is wrong. If you don't have that knowledge, you'll burn through credits watching Claude build the wrong thing over and over. So here's how I actually see these tools working together: Claude Code is great for building things faster. Applications, custom software, and now helping us scaffold n8n workflows in minutes instead of hours. n8n / Make is still the best place to deploy and maintain automations. Especially for clients. Because a client can actually look at a visual workflow and understand what's happening. Try explaining a code repository to a business owner who doesn't code.
6
0
Your AI Agent Forgets Everything About You. Every. Single. Time.
Think about this for a second. Every time you open a new chat with Claude or ChatGPT, you start from zero. You explain your business again. You describe your ICP again. You paste your tone of voice again. You remind it what you're working on, what your goals are, what your team looks like. Every single time. It's like hiring a brilliant employee who gets amnesia at the end of every conversation. Now imagine the opposite. You open a new chat and your AI already knows your business inside out. Your strategy. Your brand. Your ICP. Your writing style. Your current projects. Your team. What you discussed in your last meeting. What decisions you made yesterday. No re-explaining. No context dumps. No wasted time. That's what happens when you build a second brain for your AI. Here's how it works, and it's simpler than you think. I use Obsidian for this. It's free, it's local, and all it really is under the hood is a folder of markdown files on your computer. Each file holds a specific piece of context about you, your business, or your work. One file for your ICP. One for your brand voice. One for your current projects. One for meeting notes. One for decisions and rules. You point your AI agent (Claude, Codex, whatever you use) to that same Obsidian folder. Now it can read and write to those files anytime it needs context. The key is one instruction file at the root (a CLAUDE.md or equivalent) that tells the AI how the folder is structured and where to find what. Think of it like a map for your agent to navigate your knowledge. So when you ask "What should I focus on today?" it pulls your current projects, checks your recent meeting notes, and gives you an answer that actually makes sense for YOUR situation. Not generic advice. Real, contextualized direction. But here's where it gets really powerful. It updates itself. When you make a decision in a chat, you tell your AI to log it. When you correct something ("never use that phrase in my content"), it saves that as a rule. When a project status changes, it updates the file.
0 likes • 29d
@Clara Boyd exactly. The context is the moat. Two people using the same AI model will get completely different results based on how much context their agent has about them. The ones building that library now are going to have an unfair advantage in six months that no one can shortcut.
0 likes • 29d
@Brooks Turner Fair point. Here's a quick one: I asked my AI "what should I focus on today?" Without the second brain, it gave me generic productivity advice. With it, it pulled my current projects, checked my recent meeting notes, and told me to finish the landing page copy because the deadline is Thursday and the client followed up yesterday. Same AI, completely different output. That's the difference context makes.
1-10 of 12
Rudranil Chatterjee
3
37points to level up
@rudranil-chatterjee-6895
I build AI systems that run your ops while you sleep. Systems thinker. Reader. Occasionally lost staring at the night sky.

Active 6h ago
Joined Dec 10, 2025
India