← Tool Garage
Connect station
Slack & Discord
Where your team and your first users talk — and a place your app can post updates to.
1. Learn it
- Slack tends to be teams and customers; Discord tends to be communities and builders.
- Both accept incoming webhooks: your app sends a message to a URL and it appears in a channel.
- That's the cheapest alerting you will ever build — 'someone signed up', 'a payment failed'.
- Treat the webhook URL as a secret. Anyone holding it can post in your channel.
- Don't pipe everything in. An alert channel nobody reads is worse than no alerts.
Cost: Free tiers on both.
2. Practice it
Simulated — nothing real happensChoose the three events worth interrupting you
List every event your app could notify you about, then cross out everything that isn't worth a phone buzz at 9pm.
3. Connect it
Real — your own account- 1Create a channel just for app alerts, separate from conversation.
- 2Add an incoming webhook in the workspace or server settings and copy the URL.
- 3Store it as a secret on your server and post one test message.
- 4Send a real event next — and delete any alert you start ignoring.
MessyDev never signs you up, spends your money, or touches your accounts. You do that part.
4. Use it
Signup and payment alerts, error notifications, and running a community around your product.
Honest alternatives
There is no single correct stack. Any of these would be a reasonable choice instead.
- Email alerts
- Telegram bot
- Your monitoring tool's own notifications
More in Connect
GitHubA save system for your code, with history and an undo that actually works.PostmanA place to poke an API by hand and see exactly what it sends back.MCP & agent toolsA standard way to hand an AI model real tools it can call.n8nWire apps together with a flowchart instead of code.ZapierThe no-code version of the same idea, with thousands of ready connections.TwilioSends text messages and makes phone calls from your code.