There are four ways to get new App Store and Google Play reviews in front of your team, from turning on a store notification to paying for a tool. This guide puts them in order of effort and says what each one costs in delay, money and upkeep, including when you do not need a tool at all.
Checked 16 November 2026. Every statement about Apple or Google links to Apple's or Google's own page. Tritonium makes one of the tools in option 4, and its section says only what the product does today. If something here is out of date, write to support@tritonium.com and we will correct it.
1. The stores' own notifications
Start here. It costs nothing, and for one app with a few reviews a week it may be all you need.
App Store
- The App Store Connect app for iPhone and iPad can send push notifications about new customer reviews, and you can read and answer reviews in the app (Apple: App Store Connect for iPhone and iPad).
- App Store Connect's email notifications do not include new reviews. The one email about reviews, called Developer Response, tells you when a customer edits a review you have already answered. It is available to the Account Holder, Admin and Customer Support roles (Apple: user notifications).
- App Store Connect also has webhooks, which call a server of yours when something changes. Apple lists 12 webhook event types, covering app versions, builds, TestFlight feedback, background assets and alternative distribution. None of them is about customer reviews (Apple: WebhookEventType).
Google Play
- Play Console can email you when users write new reviews or update existing ones. You turn this on in your notification preferences (Google: View and analyze your app's ratings and reviews).
- Google generally holds new ratings and reviews back from the public store for around 24 hours while it checks for suspicious activity. You can still see and reply to them in Play Console during that time (same Google page).
Good for: one person who wants to hear about new reviews on their phone or by email. Limits: a notification reaches the person who turned it on, not a shared channel, so the rest of the team sees the review only if someone passes it on.
2. A no-code automation
Automation tools such as Zapier, Make and n8n have templates that post new app reviews to a Slack channel. Before you pick one, check where the template gets the reviews from, because that decides most of the cost and how reliable it is:
- A paid data service. For example, one n8n template checks for new App Store and Google Play reviews once a day through the DataForSEO App Data API, so it needs a DataForSEO account as well as n8n (n8n template). The same template is offered for Make (DataForSEO: Make template).
- A feed you provide. One Zapier template reads reviews from an RSS feed that you set up and formats them for Slack with a short Python step (Zapier template).
- The stores' official APIs with your own keys. Possible in tools that can send web requests, but then you are building most of option 3 inside the automation tool.
Good for: a team that already pays for one of these tools and wants new reviews in one channel. Limits: you pay for the automation tool, and often for a data service too. Each run happens on a schedule, so the delay is the time between runs. The flow works only as long as its data source does, and it needs a way to skip reviews it has already posted, or the channel fills with repeats.
3. A small script on the official APIs
If someone on your team writes code, a short script can read new reviews from each store and post them to a channel. Both stores have an official API for this.
Read new App Store reviews
The App Store Connect API lists the customer reviews for an app. You can sort newest first (sort=-createdDate), filter by star rating and by territory, and fetch up to 200 reviews a page (Apple: List all customer reviews for an app). Each request is signed with an API key. To create a team key you need the Admin role in App Store Connect, and Apple asks you not to keep keys in a code repository or in client-side code (Apple: Creating API keys).
Read new Google Play reviews
The Google Play Developer API lists reviews too, with limits worth knowing before you build on it (Google: Reply to Reviews API):
- It returns only the reviews that users created or changed in the last week. For older reviews, Google points you to the CSV download in Play Console.
- It returns only reviews with a written comment, and only for the production version of your app. A rating without a comment, and feedback on an alpha or beta version, stay in Play Console.
- Requests that read reviews are limited to 200 an hour for each app. You can ask Google for more.
- You connect with an OAuth client or a service account. A service account needs the "Reply to reviews" permission.
Post to the channel
Slack and Discord both accept messages sent to a webhook URL, so the script does not need a bot. A Slack incoming webhook is a unique URL for one channel that takes a short JSON message (Slack: incoming webhooks). A Discord webhook needs no bot user and no sign-in, and its message text can be up to 2,000 characters (Discord: webhooks).
Run it on a schedule
Run the script every hour or every few hours with cron, a scheduled job in your build system or a cloud function. Keep the IDs of the reviews you have posted, so each run posts only new ones. If the script stops for more than a week, the Google Play reviews from that gap are no longer in the API, so add an alert for failed runs.
Good for: a team with a developer that wants control and no new subscription. Limits: someone keeps the keys safe, handles errors and fixes the script when an API changes. The delay is the time between runs.
4. A review tool
Review tools collect reviews for you and send them to Slack and other places, usually with filters, several apps and more than a feed. Our comparison of nine review tools lists their prices, trials and limits from each vendor's own page.
Worth it when: you have several apps, want different reviews in different channels, or need more than notifications, such as replies, tags or analysis. Not worth it when: you only want new reviews for one app in one channel. Options 1 to 3 do that for less.
The four options side by side
| Option | Shared channel | Ongoing cost | Delay | Upkeep |
|---|---|---|---|---|
| Store notifications | No, one person | None | When the store sends it | None |
| No-code automation | Yes | The tool, often a data service too | Time between runs | Low, until the data source changes |
| Script on the official APIs | Yes | Hosting | Time between runs | Yours: keys, errors, API changes |
| Review tool | Yes | A subscription | The tool's sync schedule | The vendor's |
How Tritonium does it
Tritonium is a review tool, so it is option 4. This is what it does today, including the delay.
- When it checks for reviews: once a day by default. On a paid plan you can choose up to four sync times a day (one during the trial), and a workspace admin can choose Sync now. A new review reaches your channel after the next sync, so with the default schedule that can be up to a day after the store makes it available. It is not real time.
- Where the reviews come from: with an App Store Connect API key or a Google Play service account, Tritonium reads reviews through the same official APIs as option 3. Without them, it reads public sources: the App Store's public review feeds for ten countries, and the public Google Play listing.
- Sending reviews to a channel: a workflow that runs on "New review received" can post each matching review to a Slack channel through Tritonium's Slack app, to a Discord channel through a Discord webhook URL, create a Linear issue, or email teammates. Conditions can match the star rating, platform, language, review age or app. A ready-made workflow posts 1- and 2-star reviews to Slack. Each message shows the rating, app, platform, author and review text, with a link to the app's reviews in Tritonium.
- What a workflow does not post: reviews more than three days old when they are first synced, such as an app's history when you add it. Each sync checks up to 500 new reviews for workflows, and each workflow has a daily limit. Messages are one per review, not a daily summary.
- Alerts: separate alert rules watch for problems such as a rating drop or a spike in low ratings. Alerts appear in the dashboard and can be sent by push notification or to Slack. A workflow can pass an alert on to Discord, Linear or email.
- Who sets it up: workspace owners and admins create workflows, during the trial or on a paid plan. Microsoft Teams is not available.
If all you need is new reviews in a channel, options 1 to 3 cost less. Tritonium is built for teams that also want to see which problems keep coming up across reviews, with the source reviews behind each one, and to reply with drafts a person approves.
Which one to choose
- One app, a few reviews a week, one person answering: turn on the store notifications.
- Your team works in Slack or Discord and has a developer: a script on the official APIs is cheap and under your control.
- You already pay for Zapier, Make or n8n: use a template, but check where it gets the reviews.
- Several apps or channels, or you also need replies and analysis: a review tool.
Whichever you choose, decide what the team does when a review lands in the channel: who reads it, what counts as urgent and who replies. Our free app review triage checklist and CSV worksheet gives you a simple structure for that.
See your own reviews in Slack or Discord
Connect one App Store or Google Play app, add a workflow that sends its 1- and 2-star reviews to Slack or Discord, and check what reaches your channel after the next sync. The ready-made workflow for this posts to Slack; for Discord, choose Send to Discord as its action.