The automation and AI space has a signal-to-noise ratio problem. Everyone's an expert. Everyone has a course. Everyone has a hot take that just happens to end with a link to their $497 masterclass. After 12+ years in this space, we've built up a mental filter for separating the people who actually know what they're talking about from the people who are very good at sounding like they do.
This post is our honest attempt to share that filter. Who we follow. What we read. What we listen to. And more importantly, the red flags that help us tune out the noise before it wastes our time.
Fair warning: we're going to name real people and real publications. We're going to leave a lot of names off this list. That's not a slight. It just means this is a curated list, not a comprehensive directory. And it's biased toward practitioners (people who build things) over commentators (people who talk about things).
The Signal vs. Noise Problem
Before we get to recommendations, let us explain why this is so hard right now.
The AI and automation space rewards hype. Social media algorithms amplify extreme claims. "AI will replace all knowledge workers by 2027" gets 50x the engagement of "AI is useful for some specific tasks in some specific contexts." The incentive structure pushes everyone toward more dramatic takes, and the people with the most followers aren't necessarily the people with the most experience.
Here's the gap: the people actually building production automation systems (maintaining workflows, debugging failures at 2 AM, migrating clients between platforms) mostly don't have time to post on LinkedIn three times a day. They're busy. The people posting constantly are often consultants, coaches, or content creators whose primary product is the content itself, not the automation work.
That's not inherently bad. Some of those content creators are genuinely knowledgeable. But it means you have to work harder to find the practitioners, because the algorithm isn't promoting them.
The question we always ask when evaluating someone in this space: Have they built and maintained something in production? Not "did they set up a demo." Not "did they build a cool proof of concept." Did they ship something that ran reliably, at scale, with real data, for months or years? That experience creates a completely different perspective than building demos, and you can hear it in how someone talks about the work.
People Worth Following
These are people we've learned from personally, either through their content, their work, or direct conversations. They're builders and practitioners, and they tend to be honest about what works and what doesn't.
Wade Foster and the Zapier team. Wade's been running Zapier since 2011 and has a level-headed perspective on automation that's refreshingly free of hype. The Zapier blog itself is one of the most consistently useful resources in the space. Their content team understands the difference between "here's how to actually use this" and "here's why you should be impressed." Follow the official blog and Wade's occasional longer posts.
Jean-Paul Lam (Make community). If you're in the Make ecosystem, Jean-Paul is one of the most knowledgeable community members and automation consultants. He goes deep on complex scenarios and is honest about Make's limitations alongside its strengths. The kind of person who'll tell you "don't use Make for this, use something else" when that's the right answer.
Jan Oberhauser (n8n). The founder and CEO of n8n has a technical perspective that's valuable even if you don't use n8n. He thinks clearly about workflow orchestration as an engineering problem, and his take on where open source fits in the automation landscape is thoughtful. Worth following for the "how things actually work under the hood" perspective.
Bram Kanstein. Known for the No-Code Economy newsletter and community. Bram sits at the intersection of no-code, automation, and building real products. What we appreciate is that he's upfront about the limitations of no-code approaches, not just the possibilities. That intellectual honesty is rare.
Aron Korenblit. Runs Automate All the Things and has been teaching practical automation for years. His content is genuinely educational (not just motivational) and focuses on repeatable patterns rather than one-off tricks. If you learn better from video tutorials that respect your intelligence, Aron's a good starting point.
The "integration architects" you've never heard of. Some of the smartest people in this space don't have big followings. They're the senior consultants at Workato partners, the solutions architects at Tray.io agencies, the freelance automation developers who've built hundreds of production workflows. You find them in the community forums, the Slack groups, and the Stack Overflow equivalents for automation platforms. They don't optimize for reach. They optimize for accuracy.
Newsletters That Actually Earn Their Spot in Your Inbox
We subscribe to too many newsletters. Here are the ones we actually open.
The Zapier Blog / "How to Automate" series. We know, we're biased. But genuinely, the Zapier blog publishes some of the best practical automation content on the internet. Their "how to automate [specific workflow]" posts are step-by-step, screenshot-heavy, and written for people who want to actually do the thing, not just read about the concept. If you subscribe to one automation blog, this is the one.
The Automator by No-Code Founders. A weekly newsletter that covers automation tools, strategies, and real-world case studies. What we like is the ratio of "I can use this today" to "isn't this interesting." It skews heavily toward the former. Practical, specific, and concise.
TLDR newsletters (various). The TLDR family (TLDR, TLDR AI, TLDR Founders) does a good job of curating the firehose of AI and tech news into a digestible daily email. They're not automation-specific, but they'll keep you current on the broader AI developments that eventually affect the automation space. We scan them most mornings with our coffee.
Lenny's Newsletter. Lenny Rachitsky covers product management and growth, not automation specifically. But his thinking about how to evaluate tools, build processes, and make strategic decisions is directly relevant to anyone building a tech stack. His frameworks for "build vs. buy" decisions have influenced how we think about integration strategy with clients.
Ben's Bites. One of the better AI-focused newsletters that manages to cover the developments without breathless "everything is different now" energy. Ben has a good filter for what's actually significant versus what's just noise, and the daily format means you stay current without doing the research yourself.
Podcasts for Your Commute (or Your Walk, or Your Dishes)
We listen to podcasts while doing things that don't require our full brain. Here are the ones that have consistently been worth the time.
Automate It with Dan Young. Specifically focused on automation and integration, with guests who are practitioners, not pundits. Dan asks good follow-up questions, and the episodes tend to be focused on specific problems and solutions rather than grand visions. If you only listen to one automation podcast, this is a strong pick.
Lenny's Podcast. The podcast version of the newsletter mentioned above. Lenny's interviews with product leaders, operators, and founders consistently surface insights about tool selection, process design, and organizational efficiency. Not automation-focused, but deeply relevant.
The Changelog / Practical AI. For the more technically inclined. The Changelog covers open source and software broadly, and their Practical AI episodes specifically explore AI applications with the kind of technical depth that helps you understand what's actually possible versus what's marketing. Good for staying grounded.
My First Million / How I Built This. These are broader business podcasts, but we include them because the best automation decisions come from understanding business context first and tool selection second. The SMB Automation Playbook starts with business outcomes, not tools, and these shows reinforce that mindset.
Hard Fork (NY Times). Kevin Roose and Casey Newton cover AI and tech with genuine curiosity and appropriate skepticism. They're journalists, not salespeople, and that distinction matters. When everyone else is saying "this changes everything," Hard Fork tends to ask "okay, but does it actually?" That's the energy we want.
Communities Where You'll Actually Learn
The best learning happens in communities where people are solving real problems together. Here are the ones we've found most valuable.
Zapier Community Forum. Thousands of real automation problems with real solutions. The search alone is worth it. Whatever workflow you're trying to build, someone has probably asked about it. The community experts are generous with their time and genuinely knowledgeable. This is where you go when you're stuck on a specific technical problem.
Make Community. Similar to Zapier's but with the more technical bent that reflects Make's user base. More likely to find complex scenarios involving HTTP modules, JSON parsing, and multi-step logic. Good place to learn the more advanced stuff.
n8n Community. Particularly valuable because n8n is open source, and the community has a hacker ethos. People share full workflow templates, contribute custom nodes, and debug each other's setups with an openness that comes from the open-source culture. If you're technically inclined, this is a goldmine.
r/automation and r/nocode on Reddit. Hit or miss (it's Reddit, after all), but the upvote/downvote system does a reasonable job of surfacing genuine expertise. We sort by "top of the month" to filter for quality. You'll find real practitioners sharing lessons learned, which is worth wading through the occasional "what tool should I use?" posts.
Slack and Discord communities. Various no-code and automation Slack/Discord communities exist. The quality varies enormously. Our advice: join one or two, lurk for a week, and see if the discussions are specific (good) or vague motivational posts (bad). The No-Code Founders community and the Makerpad (now Zapier-owned) community have consistently been above average.
Red Flags: How to Spot the Noise
This is the section we wish someone had written for us five years ago. Here's what makes us immediately skeptical of someone's automation/AI content:
"I automated my entire business in one weekend." No, you didn't. Or if you did, your business is very simple. Real automation takes iteration, debugging, monitoring, and maintenance. A weekend gets you a prototype. Production takes weeks or months.
Revenue screenshots with no context. "This automation made me $50,000 last month." What's the cost? What broke along the way? How long did it take to build? What's the failure rate? Revenue without context is meaningless. But it looks impressive in a tweet.
"This one tool replaces everything." No tool replaces everything. This is either naivety or marketing. In both cases, it's not useful advice.
Course launches every month. If someone is releasing a new course or masterclass every few weeks, their primary business is selling courses, not doing automation work. That doesn't make them useless, but it means their incentive is to make automation seem simultaneously easy (so you'll buy the course) and mysterious (so you think you need the course). Be wary.
No discussion of failures. This is the biggest red flag. Anyone who's built real automation systems has stories about things that went wrong. Workflows that broke in production. Data that got corrupted. Integrations that caused more problems than they solved. If someone only talks about wins, they're either not building real things or they're not being honest. Either way, filter accordingly.
"You're leaving money on the table." Fear-based marketing. It's designed to make you feel urgency, not to help you make a good decision. Good automation advice starts with "here's how to figure out what you actually need" and not "you're falling behind if you don't buy my thing."
Breathless enthusiasm about every new feature. When someone treats every product update as the most important thing that's ever happened, they've lost the ability (or willingness) to distinguish between incremental improvements and genuine shifts. You want people who can tell you "this is interesting but doesn't change much" alongside "this actually matters."
How to Build Your Own Filter
We've given you our list, but ultimately you need your own filter. Here's how to build it.
Follow the builders, not the commentators. Look for people who share specific, detailed examples from their own work. "Here's a workflow I built for a client, here's what went wrong, here's how I fixed it." That's gold. "10 reasons you need automation in 2026" is filler.
Prefer specifics over generalities. "Use Zapier's Paths feature to route leads based on deal size" is useful. "Automation can help you work smarter" is noise. The more specific someone gets, the more likely they actually know what they're talking about.
Look for intellectual honesty. People who say "I'm not sure about this" or "it depends on your situation" or "here's the downside" are the ones we trust. Certainty about complex topics is almost always a warning sign. The real work of automation is full of tradeoffs and judgment calls. Anyone who pretends otherwise is selling you something.
Check their timeline. Have they been in this space for years, or did they pivot to "AI and automation expert" six months ago when the topic got hot? Longevity isn't everything (some newcomers are brilliant), but someone who's been building integrations for a decade has a depth of experience that a recent convert doesn't.
Watch what they recommend when they have nothing to sell. The most valuable recommendations come from people who don't benefit from your purchase. When a Zapier consultant tells you to use Make for a specific use case, that's a signal of honesty. When someone only recommends the tool they're affiliated with, factor that in.
Experience over credentials. Certifications, badges, and "official partner" status tell you someone passed a test. They don't tell you they've solved hard problems. We'd take advice from someone who's maintained 50 production workflows over someone who completed a certification course any day.
The best people in this space have a quality in common: they're more interested in solving problems than in impressing you. Their content makes you smarter, not just more enthusiastic. They give you frameworks for thinking, not just tools to buy. And they're honest enough to say "I don't know" when they don't.
Find those people. Follow them. Ignore the rest.
This post is part of The SMB Automation Playbook, a series on practical automation for small and mid-size businesses.