Morning Slack alerts for product errors using a Claude scheduled task and PostHog

Brooke Benson pro Minnesota · 1H AGO

The problem: I’m on the customer side, not the engineering side. When something breaks, I usually find out when a customer writes in, and by then a bunch of people have already hit it. We had an error chart in our analytics tool, but I don't often remember to check that dashboard every day, and a basic “alert me over X errors” setup would go off constantly for things that aren’t real problems. What I built: A Claude scheduled task that checks our error chart every morning, filters out the noise, and tells the whole team in Slack only when something’s actually wrong. I set it up just by describing what I wanted in plain English. How it works: Runs every morning before the team starts and looks at the full previous day. Pulls errors by type straight from our analytics tool. Claude connects to it directly, so it sees the same data as the dashboard. Ignores the noise. I gave Claude the rules on which error types are real problems and which aren’t, and it only counts the ones that matter. Checks a threshold. If the real errors go over the number I picked, it posts. Otherwise nothing happens. Posts one clear alert in a shared Slack channel with the total, which errors spiked, and a link to the chart. Never repeats itself. It checks the channel first so the same day never gets flagged twice. Why it’s worth it: I hear about issues before customers have to tell me. Everyone sees the same alert at the same time, so there’s no relaying messages or chasing people down. The right person just picks it up. Quiet days stay quiet, so when an alert shows up, people pay attention. I tested it against the past couple of weeks. It flagged every day something really broke and stayed silent on a busy day that was all harmless errors.