You're shipping an app. Users are downloading it. Reviews are rolling in.
And where are you checking them? App Store Connect. Google Play Console. Maybe a third-party dashboard you log into once a week. On your phone. On your desktop. Different apps. Different URLs.
This is the first mistake indie devs make with reviews: treating them as something you hunt for instead of something that finds you.
Here's the reality: if a critical review happens and you don't see it for 48 hours, you've already lost that user. And the 15 other potential customers who read that review before you responded.
That's why we built Slack and Discord notifications into AppTriage. Not as a gimmick. Because that's where developers actually spend their time — in Slack with their team, or in Discord communities.
A webhook is just an HTTP request. Your app does something. A message gets sent to Slack. That's it. No polling. No API limits. No dashboard refreshes.
But here's what changes when you have real-time notifications: you start responding to reviews the day they come in instead of the day you remember to check. And that actually moves your star rating.
Apple's algorithms reward recent activity. A 4.2-star app that's actively responding to reviews will outrank a 4.6-star app that's silent. Webhooks give you that speed.
Not every notification is worth interrupting your day for. You don't need a ping for every 5-star review saying "Love it!" But you do need to know immediately when someone leaves a 1-star review mentioning a crash.
Here are the events we recommend subscribing to, and why:
New low-rating review (1-3 stars) — This is your primary alert. Negative reviews need fast responses. If the review is actionable — mentioning a specific bug — you want to acknowledge it within 24 hours.
In-app feedback submission — Users who fill out your feedback form usually have specific, technical issues. This is higher quality signal than App Store reviews. Don't miss it.
Import errors — If your ASC or Google Play import fails, you won't know it unless someone tells you. A webhook notification means you catch sync problems before they compound.
High-volume spike — When you suddenly get 20 reviews in an hour (after a feature launch, or because of an issue), a notification tells you something changed. Good or bad.
You can skip: 5-star reviews (nice, but they don't need immediate action), 4-star reviews (usually feature requests, not emergencies), and duplicate notifications (overwhelming).
Slack's Incoming Webhooks are the simplest integration. You create a channel, generate a webhook URL, and AppTriage sends messages to it.
Step 1: Create a dedicated Slack channel. Call it #app-reviews, #feedback, or #apptriage-alerts. Keep it separate from #general so notifications don't drown in chat noise. Make it visible only to people who should act on reviews (your whole team, or just you for a solo project).
Step 2: Create an Incoming Webhook. Go to api.slack.com/messaging/webhooks. Click "Create New App" → "From scratch" → name it "AppTriage" → select your workspace → click "Create App." In the sidebar, go to "Incoming Webhooks" → toggle "Activate Incoming Webhooks" → "Add New Webhook to Workspace" → select your #app-reviews channel → authorize.
Step 3: Copy your webhook URL. It looks like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXX. This is a token — treat it like a password. Anyone with this URL can post to your channel.
Step 4: Add it to AppTriage. Go to AppTriage Settings → Notifications → Slack → paste your webhook URL → test it. You should see a test message appear in your channel within seconds.
That's it. No API keys. No OAuth. No complicated setup. Slack webhooks were designed for exactly this use case.
Discord webhooks are nearly identical to Slack's, but if anything, even easier to set up.
Step 1: Create a Discord channel. Right-click your server → "Create Channel" → name it "app-reviews" → create.
Step 2: Get the webhook URL. In the channel, click the settings icon (gear) → "Integrations" → "Webhooks" → "New Webhook" → name it "AppTriage" → copy the webhook URL.
Step 3: Add to AppTriage. Settings → Notifications → Discord → paste URL → test.
The message format is slightly different between Slack and Discord (Slack uses "attachments," Discord uses "embeds"), but AppTriage handles the translation automatically. You don't have to think about it.
Here's a security thing nobody talks about: if you accept webhook URLs from users without validation, you're vulnerable to Server-Side Request Forgery (SSRF) attacks. Someone could give you an internal URL like http://localhost:6379 and you'd send your webhook data there.
That's why AppTriage validates every URL before accepting it. We make a test request to ensure it's a real Slack or Discord webhook, not something else. It adds one extra round-trip, but it's worth the security.
This is also why some custom webhook URLs might fail — if you're trying to use a URL that doesn't exist or isn't publicly accessible, validation will catch it.
The worst notification setup is one that notifies you for everything. You start muting channels. Notifications become noise. You stop checking.
Smart filtering means you only get notified about things that require action.
Filter by rating: Only notify for 1-2 star reviews. 3-star reviews are on the border — if you want to see them, opt-in. 4-5 stars are nice but don't require immediate response.
Filter by source: App Store vs Google Play reviews often need different responses (different character limits, different APIs). You might want them in separate Slack channels so you don't miss context switching.
Filter by keywords: Mention "crash" or "bug" and you get a notification. Mention "price" or "too expensive" and you probably don't need an alert at 2am. You can fix those in the morning.
Filter by app: If you maintain multiple apps, notifications for each should go to different channels. #app-reviews-myapp1 vs #app-reviews-myapp2 keeps things organized.
Some developers prefer Telegram for notifications — it's lighter-weight, more private, and you can set up a bot without needing a workspace or server. AppTriage supports Telegram bots via webhook.
The tradeoff: Slack and Discord give you rich message formatting (colors, fields, buttons), timestamps, and integration with your team's existing workflows. Telegram bots are simpler and more personal, but less structured.
Use Slack/Discord if you want your whole team to see reviews and respond together. Use Telegram if you're solo and want lean notifications to your phone.
Here's how to make this practical:
1. A review comes in. You get a Slack notification (or Discord, or Telegram).
2. You click the link in the notification. It takes you to AppTriage's detail view for that review.
3. You read the full context — tags, history, any related feedback.
4. You write a response right there in AppTriage. Hit send. It goes to App Store Connect or Google Play automatically.
5. That response gets logged in your audit trail. Next time someone asks "how many reviews did we respond to this month?" you have a real number.
This beats the old way (notification → sign into App Store Connect → find the review → write response → hope you remembered it's public) by about five steps.
AppTriage could theoretically send you a notification for every single event. New 5-star review? Bing. New 4-star review? Boing. Import completed? Bong. Within an hour you'd mute the channel.
Instead, we've pre-configured sensible defaults based on what actually matters for most apps:
No notifications for: 5-star reviews (unless they mention a bug), completed imports (they always succeed unless there's an auth error, which does notify), or duplicate reviews from the same user.
Yes notifications for: Anything 1-3 stars, form submissions, permission errors, API failures, and rating trends (if your average drops by 0.3 stars in a week, that's worth knowing).
You can customize these thresholds. But the defaults are designed so you don't get alert fatigue.
Set up one Slack channel called #reviews. Add your whole team to it — not optional. Make it the central nervous system for app feedback. When a review comes in, the whole team sees it at the same time. Someone responds. Someone (or you) validates the response before it goes live.
This transforms reviews from a chore (checking a dashboard) to a workflow (collaborative triage, like code review).
And if you're tempted to set up notifications for every event, every app, every rating threshold, resist. Start simple: only 1-2 star reviews, only your main app, only your team's Slack. Add more later if you need it.
AppTriage sends Slack and Discord notifications for every new review — configurable by rating, platform, and app. Pair it with our review tracker for auto-import from both App Store and Google Play. Try free.
