How to Send App Store and Google Play Reviews to Slack
Step-by-step: route App Store and Google Play reviews into Slack with email forwarding, a DIY webhook script or Review Expert, plus channel and filter recipes.
Most teams do not ignore app reviews on purpose. They ignore them because the reviews live in App Store Connect and Play Console, and nobody opens those every day. Putting reviews in Slack, where the team already talks, fixes that: support sees complaints, engineers see crash reports and everyone sees the praise.
This guide walks through the options, from free do-it-yourself setups to a managed integration, and then covers the part that decides whether the channel stays useful: channel strategy and filters that keep noise down.
Your options at a glance
| Approach | Effort | Good for | Trade-offs |
|---|---|---|---|
| Store email notifications forwarded to Slack | Low | A single app, a quick start | Depends on what the stores email you; little control over format or filtering |
| DIY script: store APIs + Slack incoming webhook | Medium to high | Teams with engineering time who want full control | You own credentials, scheduling, deduplication and maintenance |
| Alert bots (for example ReviewBot) | Low | Alerts only | Pricing often scales per app or per destination; replying and analytics vary by tool |
| Review Expert | Low | Slack routing plus replies, dashboards and other destinations | Paid (Slack on Starter and above, 14-day free trial) |
Option 1: Store email notifications forwarded to Slack
App Store Connect and Play Console both have per-user notification settings. Depending on your account and the options the stores currently offer, you may be able to receive emails related to ratings and reviews. Check the notification settings in each console to see what is available for your role.
If you can get review emails, you can pipe them into Slack:
- In Slack, open the channel details and look for the option to get an email address for the channel (available on paid Slack plans), or use Slack's email app.
- In your email client, create a filter that forwards store review emails to that address.
- Test with a recent notification and check how it renders in the channel.
This is the fastest setup, but you cannot filter by rating or keyword reliably, the message format is whatever the email looks like, and you are limited by which notifications the stores send.
Option 2: A DIY script with the store APIs and a Slack webhook
If you have engineering time, the official APIs give you full control:
- Create a Slack incoming webhook for the target channel by following Slack's incoming webhooks guide.
- Get App Store credentials: create an API key in App Store Connect under Users and Access → Integrations (you need the Issuer ID, Key ID and the .p8 key, which can be downloaded only once). Use the App Store Connect API to list customer reviews.
- Get Google Play credentials: create a service account with access to your app in Play Console and call the reviews API. It returns only reviews with text that were created or modified in about the last week, so poll regularly.
- Schedule it (cron, a serverless function or CI job), store the IDs you have already posted so you do not send duplicates, and format each review as a Slack message with rating, app, version, country and a link to the console.
A minimal Slack payload looks like this:
POST https://hooks.slack.com/services/T000/B000/XXXX
Content-Type: application/json
{
"text": "★☆☆☆☆ MyApp (iOS 4.2, US): \"Crashes every time I open settings\""
}The hidden costs are the ongoing ones: rotating keys, handling API errors and rate limits, adding apps, and changing filters every time the team asks for a new channel.
Option 3: Connect Slack in Review Expert
Review Expert syncs App Store and Google Play reviews (history first, then roughly every 5 minutes) and can route them to Slack. The Slack destination is available on the Starter plan and above.
- Connect your apps under Apps & Businesses with your App Store Connect API key and Google Play service account.
- In the Review Expert dashboard, open Automation, choose Manage destinations (or Add destination), click Connect next to Slack and approve access in Slack.
- Pick the channel and set filters: minimum rating, maximum rating and keywords.
- Repeat with different filters for each channel in your strategy.
Keyword filters match when the review text contains any of the listed keywords, ignoring case. Because it is a contains-match, "crash" also catches "crashes" and "crashing". More on the Slack integration page.
Channel strategy: one firehose, a few focused channels
One channel with every review works for a small app. As volume grows, split by what people need to act on:
- #reviews-all: every review, for anyone who wants the full picture. Mute-friendly.
- #reviews-urgent: 1–2 star reviews. Support and the on-call engineer watch this one.
- #reviews-praise: 5 star reviews. Good for morale and for collecting quotes (with care for privacy).
- Keyword channels such as #reviews-crashes or #reviews-billing for specific teams.
Keep the number of channels small. Every channel needs an owner who reads it, otherwise it becomes a second place to ignore reviews.
Filter recipes
| Channel | Min rating | Max rating | Keywords |
|---|---|---|---|
| #reviews-all | 1 | 5 | (none) |
| #reviews-urgent | 1 | 2 | (none) |
| #reviews-praise | 5 | 5 | (none) |
| #reviews-crashes | 1 | 3 | crash, freeze, frozen, black screen, won't open |
| #reviews-billing | 1 | 5 | refund, charged, subscription, cancel, payment |
| #reviews-login | 1 | 3 | login, log in, sign in, password, account |
Tip: keyword filters only match the words you list, so include common variants and, if you have many non-English reviews, the equivalent words in those languages.
Avoiding noise
- Start narrow. Begin with #reviews-urgent only, then add channels when someone asks for them.
- Avoid overlapping alerts in the same channel. If a review can match two destinations that post to one channel, it will appear twice.
- Review keywords monthly. Remove words that mostly produce false positives ("account" can be noisy) and add terms you see in new complaints.
- Use threads. Discuss a review in its thread so the channel stays scannable.
- Agree on a reaction convention, for example :eyes: for "looking" and :white_check_mark: for "replied", so two people do not answer the same review.
Replying: closing the loop
Slack is where you notice a review; the reply still has to land on the store. With a DIY setup, that means opening App Store Connect or Play Console. In Review Expert, open the review and reply there; the reply is posted back to the App Store or Google Play, and your response rate and average response time show up on the dashboard.
For wording, see how to respond to app reviews and our reply templates. If your team also uses Microsoft Teams, the same filters work for the Teams destination on Pro and above.
