How to Reply to App Reviews From Slack
Neither store has a Slack integration — so here's how to actually run App Store and Google Play review replies from the channel your team already lives in.
The Argus Team
Reply Argus
You can't hit "reply" on an App Store or Google Play review from inside Slack — neither store ships a Slack integration, and Apple has never offered one. What you can build, though, is the workflow developers actually want: the review lands in your Slack channel the second it posts, with a reply already drafted underneath it, and one person approves it without ever opening App Store Connect or the Play Console.
That's the real meaning of "reply to app reviews from Slack" — Slack becomes the place you see the review and decide, not the place the reply technically gets published. This guide walks the whole path: why the native stores leave you nothing, the DIY way to pipe reviews into a channel yourself, and the setup that closes the loop so a one-star can be answered before your standup ends.
Can you reply to app reviews directly from Slack?
No — not natively, and it's worth being precise about why. App Store Connect and Google Play Console are the only surfaces that can actually post a public developer reply. Neither exposes a Slack app, a Slack action, or a webhook you could wire a reply back through. Apple doesn't even send review emails; the one native alert is a push notification buried in the App Store Connect iOS app that you have to enable by hand. Google Play at least offers opt-in email notifications, but still nothing that reaches a channel.
So the honest architecture is two halves. Half one: get the review into Slack the moment it arrives — that part you can fully control. Half two: get a reply back onto the store — that always happens through the store's own API or console, whether you do it manually or a tool does it for you. A good Slack-first setup makes half one instant and half two a single approval, so the seam between them disappears. If you're still fighting just to hear about new reviews, start with [how to actually get notified of new App Store reviews](/blog/get-notified-of-new-app-store-reviews) and come back.
The DIY route: pipe reviews into a Slack channel yourself
If you only need the alert half and you're happy to write the reply by hand, you can stand this up in an afternoon with a Slack incoming webhook and a small poller. The shape is the same for both stores:
- 1
Step 1 — Create a Slack incoming webhook
In your Slack workspace, add an Incoming Webhooks app, pick the channel (say #app-reviews), and copy the webhook URL. Anything you POST to that URL shows up as a message in the channel.
- 2
Step 2 — Poll the reviews
For Apple, hit the public per-country RSS feed (itunes.apple.com/{country}/rss/customerreviews/id={appId}/json) or the App Store Connect API. For Google Play, use the Play Developer Reviews API. Run it on a cron every few minutes and diff against the reviews you've already seen.
- 3
Step 3 — Post new reviews to Slack
When you find an unseen review, format it (stars, text, author, store) and POST it to the webhook URL. Now every new review lands in the channel automatically.
- 4
Step 4 — Reply on the store
Read the alert, open App Store Connect or the Play Console, and type the reply there. Slack showed you the review fast; the reply itself still happens on the store.
curl -X POST -H 'Content-type: application/json' \
--data '{"text":"⭐️ 1-star (Play) — @kirs_dev\n“Latest update crashes on launch every time.”"}' \
https://hooks.slack.com/services/T000/B000/XXXXXXXXThe DIY route alerts, but it doesn't reply
A webhook only pushes text into a channel. It won't draft anything, won't translate the Portuguese one-star, and can't post your reply back to the store — you still context-switch into the console for every single one. It's also blind to ratings-only feedback (a star with no words produces no review object to poll), and Apple's RSS feed is per-country and cached, so it lags and you poll one URL per storefront. It's a solid alert; it is not a reply workflow.
The Slack-first workflow that actually closes the loop
The version teams keep is the one where the alert arrives with the answer already attached. That's the gap [ReplyArgus](/features) fills: it watches your Apple App Store and Google Play reviews in one inbox, and the moment a review — or a rating drop — lands, it pushes an alert to your Slack channel with an on-brand reply already drafted in the reviewer's own language. No poller to babysit, no per-country URLs, no blank reply box.
So the person who sees the Slack message isn't starting from zero. They're reading a review and a proposed reply side by side, and their only job is to decide: ship it, tweak it, or skip it. For the safe, high-volume stuff — the five-star "love this app" thank-yous — you can set opt-in rules so those publish automatically and never hit the channel at all, leaving Slack for the reviews that actually need a human. See every alert channel (Slack, Discord, Telegram, webhook, email) on the [integrations page](/integrations).
Paid for the yearly plan and now the widget won't refresh on iOS 18. Feels like a bait and switch.
That's a fair thing to be angry about — you paid for a feature that stopped working, and "bait and switch" is exactly how a broken widget after an OS update feels. This one's on us: iOS 18 changed how background refresh fires, and our 6.2 build (out today) restores it. Update and give the widget a few minutes to sync. If it's still stuck, reply here and we'll sort your subscription out directly.
That reply reads like a person because a person approved it — but they approved it in seconds, from a draft that already named the bug and the fix. The draft is grounded in your past approved replies and a knowledge base built from your store listing and marketing page, so it doesn't invent a version number or promise a feature you don't have. We dig into why that grounding matters in [grounded vs hallucinated AI replies](/blog/grounded-vs-hallucinated-ai-replies).
Alert in Slack vs. one-click publish: set expectations honestly
Here's the part people conflate. Slack is where the review and the draft show up; it is not a magic "publish" button on the store. You approve in one of three places, and it's worth knowing which fits your team:
- Approve in the inbox — click into ReplyArgus from the Slack alert, read the draft, and publish with one action. Best when you want a human eye on everything.
- Auto-publish by rule — opt in to rules (by rating, keyword, language, or store) so trusted cases like 5-star thank-yous post themselves and skip Slack. Best for cutting the volume down to the reviews that need judgment. If auto-publish makes you nervous, [is it safe to auto-publish replies](/blog/is-it-safe-to-auto-publish-app-review-replies) covers the guardrails.
- Drive it from an AI tool — because there's an [MCP connector](/agentic-tools), you can operate the whole inbox from Claude, ChatGPT, or Cursor: "draft replies to today's one-stars, hold them for me." For Slack-native dev teams already living in an agentic stack, this is the natural extension of the workflow.
Whichever you pick, the reply still has to satisfy each store's rules. Google Play caps developer replies at a hard 350 characters, so a draft has to be tight; Apple publishes no official limit (community testing suggests a few thousand characters), so you get more room there. A good drafter respects both automatically. More on the split in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).
Why Slack is the right home for review ops
For a dev team, the review isn't really a support ticket — it's a signal that belongs where the team already talks. Routing reviews into Slack fixes the boring, consistent reasons reviews go unanswered:
- No dead-end inbox — the alert lands in a shared channel, not one person's phone that they left at home.
- It survives a busy week — during a launch or crunch, nobody remembers to open the review tab; a channel ping is passive, so the angry review still surfaces.
- The right person can grab it — a crash report can be @-mentioned to the engineer, a billing complaint to whoever owns refunds, right there in-thread.
- Speed, which is measurable — the faster you answer, the more the reply lands. Srisopha et al. (EASE 2021) found timeliness among the top predictors of a reply that wins a reviewer back, ahead of politeness; and Google shared at I/O 2019 that apps see roughly a +0.7-star average lift when developers respond. Since ratings went recency-weighted that same year, a fresh one-star flipped fast counts for more than an old rating ever will. We cover that clock in [review velocity](/blog/review-velocity).
Frequently asked
- Can you reply to App Store reviews from Slack?
- Not directly — Apple has no Slack integration, and only App Store Connect can post a public developer reply. What you can do is route new reviews into a Slack channel with a reply pre-drafted, then approve it in a click. A tool like ReplyArgus pushes each review to Slack and publishes the approved reply back to the store for you.
- Does Google Play have a Slack integration for reviews?
- No native one. Google Play Console offers opt-in email notifications for new reviews but nothing that posts to Slack. To get Play reviews into a channel, you either wire the Play Developer Reviews API to a Slack incoming webhook yourself, or use a monitoring tool that supports Slack as an alert channel.
- How do I set up Slack alerts for new app reviews myself?
- Create a Slack incoming webhook for the channel, then run a poller against Apple's review RSS feed or App Store Connect API and Google's Play Reviews API. When it finds an unseen review, POST it to the webhook URL. It alerts you, but it won't draft or publish replies — that stays manual.
- Can ReplyArgus publish my reply straight from the Slack message?
- The Slack message is where the review and the AI draft show up. You approve in the ReplyArgus inbox with one action, set opt-in rules so safe cases auto-publish, or drive it from Claude/ChatGPT via the MCP connector. The publish itself always goes through the store's API — Slack is the alert-and-draft surface, not the publish button.
- What's the character limit for a review reply?
- Google Play enforces a hard 350-character cap on developer replies. Apple publishes no official limit; community testing suggests a few thousand characters, so you get more room on the App Store. Any draft you approve should fit the store it's going to.
- Is it against store policy to reply with AI?
- No store bans AI-assisted replies. The rules that matter are about content — no spam, no off-topic promotion, staying respectful — not about whether a human typed every word. Grounding the draft in real facts and keeping a human approval step keeps you comfortably inside the guidelines.
There's no Apple or Google switch that turns Slack into a reply box — but you can get all the way there by letting the review and its answer arrive together in the channel your team already watches. If you'd rather skip the poller and the console tabs, [start free with ReplyArgus](/signup) — no card — and Argus will watch both stores, ping your Slack the moment a review lands, and have a reply drafted in the reviewer's language before you've finished reading the alert.
Try it
Let Argus draft your next reply.
Watch it answer a real review in your voice. 10-day trial, no card to begin.
Keep reading
App Store Reviews Not Showing? The Full Fix List for Apple and Google Play
App Store or Google Play reviews not showing? Here's every real cause — moderation delay, wrong country storefront, filtering, rating lag, cache — and the fix.
Read moreAre App Store Reviews Fake? How to Spot Them and What to Do
Yes, some App Store and Google Play reviews are fake — but fewer survive than you think. How to spot them, and what to do when they hit your app.
Read more