You Can’t Send a Notification to Yourself

You Can't Send a Notification to Yourself

Unless you’re a bot.

Let me tell you about the two weeks I spent slowly losing my mind over a Slack notification.

The setup was simple, or so I thought. Connect n8n to a Slack channel, get a real-time ping whenever something important happened. Nodes built, tested, working perfectly. Messages landed in the channel exactly when they should. Except for one thing. No sound. No bold text. No little notification number. Just a message, sitting there, quietly, like it had wandered in and didn’t want to make a fuss.

The bit where I did everything anyone tells you to do

Checked my notification settings. Checked the channel settings. Made sure the app was actually added to the channel properly, not just sort of loosely associated with it. Still nothing. Contacted Slack support, because at this point I was fairly sure I’d missed something obvious and wanted someone to point at it.

Support had suggestions. I tried them. Double checked everything again, just in case I’d imagined ticking a box I hadn’t actually ticked. Still no sound. Still no bold. Still nothing.

The bit where I went round in circles with Claude too...

I’d been troubleshooting this with Claude as well, working through the usual suspects. Notification settings, channel settings, whether the app was properly added. All correct. All checked, twice. And we got stuck in exactly the kind of loop you get stuck in when everyone involved, human or otherwise, has already checked the obvious things and is now just checking them again with slightly more emphasis.

So I opened a new chat. Pasted in screenshots of the node I was working on, the channel setup, the notification settings, everything. A fresh look, with no accumulated assumptions from two weeks of “well it’s definitely not that, we already checked.”

The bit where it turned out to be something nobody had checked

The actual question, once we finally got to it, was about how the Slack API credential in n8n was set up. Specifically, whether it was configured to send as a bot.

Here’s the thing I genuinely hadn’t clocked. If the message is coming through as you, Slack doesn’t notify you about it, because you can’t send yourself a notification. You already know you said the thing. You were there. It’s you. Slack quite reasonably assumes you don’t need alerting to your own existence.

Two weeks of settings, support tickets, and increasingly specific googling, and the whole thing came down to one identity mix-up between me and a robot pretending to be me.

The bit where AI actually helped

Not because it found the answer on the first try. It didn’t. We looped just as hard as I did with support, checking the same reasonable things in the same reasonable order and getting nowhere.

What actually worked was starting fresh with the full picture laid out at once, screenshots and all, rather than another round of the same back and forth building on two weeks of assumptions. Sometimes the fix isn’t a cleverer diagnosis. It’s just getting a clean look at the whole problem again, without the baggage of everything you’ve already half-solved and ruled out.

Once that happened, the actual cause turned up fast. Not because anyone was smarter the second time around. Because nobody was dragging two weeks of wrong turns into the conversation with them.

The bit that's actually the whole point of this post

This is the experience you’re paying for when you hire me. Not someone who’s never stuck, because everyone gets stuck, including me. What you’re paying for is someone who knows when to stop going round the same loop and start again properly, who knows which tools to bring in and how to use them well, and who’s done this enough times to recognise “you can’t send a notification to yourself” as a plausible answer rather than a strange one.

Two weeks of settings and troubleshooting came down to one identity mix-up between me and a bot pretending to be me. Finding that isn’t luck. It’s the actual job.