Google Play and Slack, replies that protect your rating
Your Google Play reviews pile up faster than you can answer them. A few get missed, a few get rushed, and suddenly the public “support vibe” of your app looks sloppy (even if your product is solid).
This Google Play replies automation hits indie devs first, honestly. But product managers and agency teams managing multiple apps feel the same pressure: reply quickly, stay on brand, don’t sound like a bot.
This workflow fetches new reviews, checks what’s already handled, uses AI to write a human response, posts it back to Google Play, and logs the result in Slack so your team stays in the loop.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Google Play and Slack, replies that protect your rating
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge1"]
n1@{ icon: "mdi:robot", form: "rounded", label: "Verify Analysis", pos: "b", h: 48 }
n2@{ icon: "mdi:memory", form: "rounded", label: "User Review Memory", pos: "b", h: 48 }
n3@{ icon: "mdi:brain", form: "rounded", label: "OpenAI GPT 4o mini", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Post Reply to Play Store"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Slack"]
n6@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger1", pos: "b", h: 48 }
n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter1", pos: "b", h: 48 }
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTPS1"]
n9@{ icon: "mdi:robot", form: "rounded", label: "OpenAI1", pos: "b", h: 48 }
n10@{ icon: "mdi:robot", form: "rounded", label: "AI Agent1", pos: "b", h: 48 }
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge2"]
n8 --> n7
n8 --> n0
n8 --> n11
n0 --> n1
n11 --> n10
n7 --> n9
n9 --> n0
n10 --> n4
n1 --> n11
n6 --> n8
n3 -.-> n10
n2 -.-> n10
n4 --> n5
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n6 trigger
class n1,n9,n10 ai
class n3 aiModel
class n2 ai
class n7 decision
class n4,n8 api
class n6 disabled
classDef customIcon fill:none,stroke:none
class n0,n4,n5,n8,n11 customIcon
The Challenge: Replying fast without sounding fake
Google Play reviews are public support tickets, but they don’t arrive in a neat queue. They show up at night, during launches, and right when you’re trying to ship fixes. When you reply late (or not at all), users assume you won’t fix the issue. When you reply too quickly with a copy-paste template, you look robotic, and people keep scrolling. The worst part is the mental load: you’re always wondering what’s sitting unanswered, and whether a 1-star review is quietly dragging your rating down.
It adds up fast. Here’s where it usually breaks down.
- Review replies get delayed because nobody “owns” the inbox every day.
- Negative reviews don’t get prioritized, so small fires turn into visible reputation damage.
- Teams drift into inconsistent tone, especially when multiple people answer across multiple apps.
- You lose visibility because replies live inside Google Play, not where your team actually works.
The Fix: AI-written replies posted to Google Play, logged in Slack
This workflow runs on a schedule, pulls in the newest Google Play reviews via the Play Store API, then checks which ones have already been replied to so you don’t double-handle anything. For each eligible review, it analyzes the text for sentiment and tone using OpenAI, then hands the review context to an AI Agent that writes a response meant to sound like a helpful human (not a template). That reply is sent back to Google Play automatically through a request to the Google API. Finally, the workflow posts a message to Slack so your team can see what was answered, what the sentiment was, and what users are complaining about this week.
The workflow starts with a scheduled trigger. From there, it fetches reviews, filters out anything already handled, then runs sentiment + reply generation before posting the final response. Slack logging closes the loop so you’re not guessing what happened.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you manage 3 apps and each gets about 10 reviews a week. Manually, it’s easy to spend 5 minutes per review between reading, drafting, posting, and then updating your team, which is roughly 2.5 hours weekly. With this workflow, you glance at the Slack log and only step in when something looks sensitive, which is usually 10 minutes total. That’s a couple hours back every week, and the public replies stay timely.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Play Developer Console access to read and reply to reviews
- Google Cloud service account to authenticate API requests
- OpenAI API key (get it from your OpenAI dashboard)
- Slack workspace to log replies for visibility (optional)
Skill level: Intermediate. You’ll connect credentials, add a service account, and test with a few sample reviews.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A scheduled check runs automatically. The Scheduled Review Trigger fires on your chosen interval (for many teams, daily is enough). That trigger starts the whole chain without someone remembering to “go look.”
Reviews are pulled from Google Play. An HTTP Request fetches the latest reviews through the Play Store API, then the workflow splits what’s coming in so sentiment analysis and reply composition can work in parallel.
Already-replied reviews are filtered out. The If node checks review state so you only respond where it’s needed. This is one of those small details that prevents messy double-replies.
AI evaluates the review and drafts a reply. OpenAI analyzes the review text, then the AI Agent writes a human-like response using the sentiment context (and any brand guidance you add). A final HTTP request posts the reply back to Google Play.
Slack gets a paper trail. After posting, the Slack Channel Alert logs what happened so the team can review it, spot trends, and jump in when a situation needs a personal touch.
You can easily modify the sentiment rules to route “angry” reviews into a manual approval path based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Review Trigger
Set the workflow schedule that initiates your review processing cycle.
- Add or open Scheduled Review Trigger and define your desired schedule for polling reviews.
- Ensure Scheduled Review Trigger connects to Fetch Store Reviews.
- Confirm the node is enabled before production use (it is currently disabled in the workflow).
Step 2: Connect the Review Data Source
Configure the node that fetches reviews from your app store or review platform.
- Open Fetch Store Reviews and configure the HTTP endpoint for your review source.
- Provide any required authentication headers or query parameters for your store API.
- Verify that Fetch Store Reviews outputs to Review Filter Check, Combine Streams A, and Combine Streams B in parallel.
Step 3: Configure Review Filtering and Analysis
Filter and analyze reviews before sentiment validation.
- In Review Filter Check, define the condition that determines which reviews should be analyzed.
- Connect the “true/continue” output of Review Filter Check to Analyze Review Text.
- Ensure Analyze Review Text connects to Combine Streams A to merge analysis results.
- Credential Required: Connect your OpenAI credentials in Analyze Review Text.
Step 4: Validate Sentiment and Merge Streams
Use sentiment analysis to prepare inputs for reply composition.
- Open Validate Sentiment and configure the prompt/model settings for sentiment validation.
- Credential Required: Connect your OpenAI credentials in Validate Sentiment.
- Confirm Combine Streams A feeds into Validate Sentiment and Validate Sentiment outputs to Combine Streams B.
- Keep Combine Streams B connected to Compose Reply Agent to pass merged data forward.
Step 5: Set Up AI Reply Composition
Configure the agent, memory, and language model that create the final response.
- Open Compose Reply Agent and set your reply-generation instructions and tools.
- Ensure GPT-4o Mini Chat is connected as the language model for Compose Reply Agent.
- Credential Required: Connect your OpenAI credentials in GPT-4o Mini Chat.
- Confirm Review Memory Buffer is connected as memory for Compose Reply Agent (add credentials to the parent model node, not the memory node).
Step 6: Configure Review Reply Dispatch and Notifications
Send the generated response back to the store and notify your team in Slack.
- In Dispatch Store Reply, set the HTTP method and endpoint for posting replies to your store.
- Map the reply content from Compose Reply Agent into the request body.
- Open Slack Channel Alert and select the Slack channel for notifications.
- Credential Required: Connect your Slack credentials in Slack Channel Alert.
Step 7: Test and Activate Your Workflow
Verify each branch works and then enable the automation for production.
- Click Execute Workflow and confirm Fetch Store Reviews returns review data.
- Verify that analysis flows through Analyze Review Text and Validate Sentiment, then into Compose Reply Agent.
- Confirm a successful response is sent by Dispatch Store Reply and a message appears in Slack Channel Alert.
- Enable Scheduled Review Trigger and switch the workflow to active for ongoing automated use.
Watch Out For
- Google Play (service account) permissions are easy to misconfigure. If replies fail, check Google Cloud IAM roles and the API access settings tied to your Play Console first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Common Questions
Usually about an hour once your Google service account is ready.
Yes, but you’ll want one person comfortable with Google Cloud permissions. The n8n side is mostly connecting accounts and testing with a few reviews.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs (often just a few dollars a month at typical review volumes).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Start by adjusting the instructions inside the Compose Reply Agent so it matches your brand voice and support policy (refunds, bug-report links, escalation language). If you want stricter control, update the Review Filter Check to route certain ratings (like 1-star) to Slack-only logging instead of auto-posting. You can also tweak Analyze Review Text and Validate Sentiment to add categories like “billing,” “crash,” or “feature request,” then send those tags into Slack or Google Sheets for tracking.
Usually it’s the service account setup, not n8n. Check that the correct JSON key is loaded, the Play Developer API is enabled in your Google Cloud project, and the service account has access in the Play Console for the right app. If it works once and then stops, look for rotated keys or a permission change made by someone else on the team. Rate limits can also show up during spikes, so spacing the schedule out can help.
For most small apps, it’s effectively “as many reviews as you get.” On n8n Cloud Starter, you’re limited by monthly executions, while self-hosting has no execution cap and mainly depends on your server. In practice, reviews process quickly because you’re only sending short text to OpenAI and posting a short reply back to Google Play. If you manage lots of apps, the easiest scale move is batching and running the schedule more frequently.
Often, yes. The hard part here isn’t “send a message when a review arrives,” it’s the filtering, the branching, and the AI agent prompt control, and n8n handles that without turning it into an expensive multi-step bill. Self-hosting is also a big deal if you have a lot of review volume. Zapier or Make can still work if you only need a basic alert and a manual reply process, but you’ll usually end up bolting on extra steps to get close to this behavior. If you’re on the fence, Talk to an automation expert and we’ll map the simplest path for your setup.
Your reviews keep moving, even when you’re busy. Let the workflow handle the repetitive replies and the Slack visibility, so you can spend your attention on fixing the issues that caused them.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
