🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Google Play to Slack, review digests your team reads

Google Play to Slack, review digests your team reads - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Google Play to Slack, review digests your team reads - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You get new Google Play reviews, and somehow they still don’t reach the right people. They sit in the console, get skimmed once, then vanish until the next “why are installs dropping?” meeting.

This is the kind of mess product managers notice first, but support leads and growth marketers feel it too. With Google Play Slack automation, reviews show up as a digest your team will actually read, so feedback turns into decisions instead of noise.

Below, you’ll see how the workflow pulls reviews, summarizes them with AI, and posts a clean update to Slack daily (or weekly), plus what you need to run it reliably.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Play to Slack, review digests your team reads

The Problem: Google Play Reviews Don’t Turn Into Action

Google Play reviews are a goldmine, but the way most teams handle them is frankly chaotic. Somebody checks the console when they remember, screenshots a few spicy comments, and drops them into Slack with no context. Meanwhile, the quiet patterns get missed: a bug tied to a specific version, a spike in 1-star reviews after an onboarding tweak, or the same request repeated across multiple languages. The cost isn’t only time. It’s momentum. When insights arrive late, you ship slower and argue more because everyone is working from different “evidence.”

The friction compounds. Here’s where it breaks down.

  • Checking reviews for multiple apps turns into a daily tab-juggling ritual that steals about an hour, then still misses edge cases.
  • Raw reviews are hard to scan quickly, so the team reacts to the loudest comment instead of the most common issue.
  • Manual copying introduces mistakes (wrong star counts, missing dates, lost context), which undermines trust in the report.
  • No system for “what changed this week,” so sentiment shifts are spotted only after your rating takes a hit.

The Solution: Google Play Reviews Summarized and Posted to Slack

This n8n workflow pulls recent Google Play Store reviews for one or more apps, then turns that raw feedback into a Slack-ready digest. It starts on a schedule (daily or weekly), reads a list of app bundle IDs you define, and calls the Google Reviews API using a Google Service Account. Reviews are filtered so you’re only processing what’s new or relevant, then stored in Pinecone so the system can retrieve and summarize efficiently without reprocessing the same content forever. An AI agent powered by an OpenAI Chat Model generates a clear summary with highlights, star breakdowns, and the total count processed. Finally, the workflow posts the digest to the Slack channel you choose, so the update lands where your team already works.

The workflow kicks off from a daily schedule trigger (and optionally a weekly one). It batches through your apps, fetches recent reviews, and uses Pinecone plus OpenAI to produce a concise “what happened and why it matters” recap. Slack receives the final message, ready for product triage or support follow-up.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you manage 3 apps and you check reviews 5 days a week. Manually, you might spend about 20 minutes per app reading, sorting, and pasting notes into Slack, which is roughly 1 hour a day (about 5 hours a week). With this workflow, the “work” is basically zero: the schedule trigger runs automatically, the API fetch and AI summarization happen in the background, and Slack gets the digest. You glance at it in a couple minutes and move on.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Play Console + Service Account to access review data.
  • Slack to deliver the digest to your team.
  • OpenAI API key (get it from your OpenAI API settings page).

Skill level: Intermediate. You’ll connect credentials and adjust a couple of nodes (bundle IDs, Slack channel), but you don’t need to write code.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A schedule kicks things off. You can run it daily for a steady pulse, weekly for leadership reporting, or both if you want different levels of detail.

Your app list is expanded and processed in batches. You add one or more Google Play bundle IDs in the “Set the bundle ids” step, then the workflow loops through them so you’re not building separate automations per app.

Reviews are fetched, filtered, and stored for retrieval. n8n calls the Google Reviews API, extracts the review items, and filters for recent entries. Those reviews are embedded and written to Pinecone, which makes it much easier to generate summaries that reflect the real themes instead of cherry-picked comments.

OpenAI generates a digest and Slack receives it. The AI agent produces highlights (good and bad), a star rating breakdown, an average rating, and how many reviews were processed. Then “Post Slack Summary” publishes the message to your chosen channel.

You can easily modify the bundle ID list to include new apps, or adjust the schedule to match your release cadence based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Triggers

Set the schedule triggers that kick off the daily review ingestion and the weekly summarization cycle.

  1. Open Daily Schedule Start and set the trigger time under Rule to the daily hour. This workflow uses triggerAtHour: 10.
  2. Open Weekly Schedule Start and set the weekly rule under Rule to field: weeks, triggerAtDay: 5, and triggerAtHour: 11.
  3. Verify the execution flow: Daily Schedule Start → Define Bundle List, and Weekly Schedule Start → Define App Catalog.

Tip: Align the daily and weekly schedules with your reporting timezone to avoid missing same-day reviews in Filter Recent Reviews.

Step 2: Define Your App Lists and Iteration

Configure the app bundle IDs for daily ingestion and the app catalog used for weekly summaries.

  1. Open Define Bundle List and set the array value for apps to your bundle IDs, e.g. ["com.bundle.id1","com.bundle.id2","com.bundle.id3"].
  2. Open Expand App List and set Field to Split Out to apps.
  3. Open Define App Catalog and set the array value for apps to objects containing app and app_name, e.g. [{"app":"com.bundle.id1","app_name":"App1"}].
  4. Open Expand App Catalog and set Field to Split Out to apps.
  5. Keep Batch Through Apps and Iterate App Details as split-in-batches nodes for pacing and iteration.

⚠️ Common Pitfall: Make sure the bundle IDs in Define Bundle List and the app values in Define App Catalog match exactly, or the weekly summaries will not find stored reviews.

Step 3: Connect Google Play Reviews and Filter Recent Items

Fetch reviews from Google Play, split them into individual items, and keep only the most recent ones.

  1. Open Google Reviews API Call and confirm the URL is https://androidpublisher.googleapis.com/androidpublisher/v3/applications/{{$json.apps}}/reviews.
  2. Credential Required: Connect your googleApi credentials in Google Reviews API Call.
  3. Keep pagination enabled with completeExpression: {{$response.body.tokenPagination.nextPageToken == null}} to retrieve all pages.
  4. Open Extract Review Items and set Field to Split Out to reviews.
  5. Open Filter Recent Reviews and keep the date comparison: {{ $json.reviews.comments[0].userComment.lastModified.seconds.toDateTime('s').toISODate() }} equals {{$today.minus({days: 1})}}.

Step 4: Load Reviews into Pinecone Vector Store

Convert review records into documents and store them in Pinecone for later retrieval.

  1. Open Review Data Loader and set JSON Data to comment: {{ $json.reviews.comments[0].userComment.text }} | date: {{ $json.reviews.comments[0].userComment.lastModified.seconds.toDateTime('s') }} | star rating: {{ $json.reviews.comments[0].userComment.starRating }} | app version: {{ $json.reviews.comments[0].userComment.appVersionName }} | language: {{ $json.reviews.comments[0].userComment.reviewerLanguage }}.
  2. Keep metadata mappings in Review Data Loader for star_rating, date, app_version, language, and review_id using the existing expressions.
  3. Open Pinecone Store Writer and set Mode to insert.
  4. In Pinecone Store Writer, confirm Clear Namespace is set to {{ new Date().getDay() === 6 }} and Pinecone Namespace is google_play_store_reviews_{{ $('Expand App List').item.json.apps }}.
  5. Credential Required: Connect your pineconeApi credentials in Pinecone Store Writer.
  6. Open OpenAI Embeddings and ensure it is connected as the embedding model for Pinecone Store Writer. Credential Required: Connect your openAiApi credentials in OpenAI Embeddings.

Tip: The namespace format google_play_store_reviews_{{ $('Expand App List').item.json.apps }} keeps reviews separated by app for clean weekly summaries.

Step 5: Configure the AI Summarizer and Retrieval Tooling

Set up the AI agent to retrieve reviews from Pinecone and generate a structured summary.

  1. Open Pinecone Store Retriever and set Mode to retrieve-as-tool with Top K set to 500.
  2. In Pinecone Store Retriever, set Pinecone Namespace to google_play_store_reviews_{{ $('Iterate App Details').item.json.app }}.
  3. Credential Required: Connect your pineconeApi credentials in Pinecone Store Retriever.
  4. Open AI Review Summarizer and confirm the Text prompt is set to Create a summary of store reviews submitted... {{$json.app_name}} ... and includes the star rating breakdown requirements.
  5. Open OpenAI Chat Model and verify the model selection, e.g. gpt-4.1-mini. Credential Required: Connect your openAiApi credentials in OpenAI Chat Model.
  6. Open OpenAI Embeddings 2 and ensure it is connected as the embedding model for Pinecone Store Retriever. Credential Required: Connect your openAiApi credentials in OpenAI Embeddings 2.

⚠️ Common Pitfall: OpenAI Embeddings and OpenAI Embeddings 2 are AI sub-nodes; ensure credentials are attached directly to those nodes since they power the vector store operations.

Step 6: Configure the Slack Output

Send the AI-generated summary to your Slack channel.

  1. Open Post Slack Summary and set Text to {{ $json.output }}.
  2. Select the target channel by setting Channel to your Slack channel ID value.
  3. Credential Required: Connect your slackApi credentials in Post Slack Summary.

Step 7: Test and Activate Your Workflow

Run the workflow manually to verify outputs, then activate it for scheduled execution.

  1. Click Execute Workflow and watch Daily Schedule Start and Weekly Schedule Start paths run through their respective sequences.
  2. Confirm that Google Reviews API Call returns review data and that Filter Recent Reviews outputs only the last day’s reviews.
  3. Verify Pinecone Store Writer inserts documents and that AI Review Summarizer returns a structured summary including positive/negative summaries, star breakdown, and average rating.
  4. Check Slack to ensure Post Slack Summary posts the summary text in the correct channel.
  5. Toggle the workflow to Active to enable scheduled runs.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Service Account access can fail if the Play Console permissions aren’t correct. If reviews suddenly stop, check your Google Play Console user/service account access and the API scope settings first.
  • If you’re using Wait nodes or external processing, timing can drift. Bump up the wait duration if downstream nodes fail on empty responses, especially when review volume spikes after a release.
  • Default prompts in AI nodes are generic. Add your brand voice and what “actionable” means to your team early, or you will be editing outputs forever.

Related Workflows

If your team also ships on iOS, pairing this with App Store to Slack, weekly review summaries your team reads gives you one rhythm for both app stores, which makes cross-platform trend spotting much easier.

When you want to go beyond “read and react” and actually respond quickly, Google Play and Slack, replies that protect your rating helps you turn certain reviews into drafted replies so the team can address issues while they’re still fresh.

Need the same insights, but in a format leadership can slice and filter? Google Sheets + OpenAI: clearer Google review insights is great when you want a spreadsheet view for tags, versions, and recurring themes.

For ecommerce brands running an app plus a store, Shopify reviews to Slack and Trello, handled fast creates a nice parallel workflow so product feedback and store feedback don’t get mixed together in the same channel.

Finally, if you’re on WordPress and you want a lighter-weight “temperature check” in Slack, WooCommerce + Slack: review sentiment at a glance keeps reviews visible without asking someone to babysit another dashboard.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Google Play Slack automation?

About 45 minutes if you already have your credentials ready.

Do I need coding skills to automate Google Play review digests?

No. You’ll paste in credentials, add your bundle IDs, and pick a Slack channel.

Is n8n free to use for this Google Play Slack workflow?

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 usage (usually a few dollars a month for most teams) and Pinecone, depending on how much you store.

Where can I host n8n to run this automation?

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.

Can I customize this Google Play Slack workflow for weekly summaries instead of daily?

Yes, and it’s already built for that. You can enable the “Weekly Schedule Start” trigger and tune what counts as “recent” in the filtering step so the summary covers the last 7 days. Common customizations include changing the Slack message format, summarizing per app instead of combined, and adding “top recurring issues” as a dedicated section in the AI summarizer prompt.

Why is my Google Play connection failing in this workflow?

Usually it’s a Google Service Account problem, not n8n. Confirm the service account has access inside the Google Play Console, then re-check the credential JSON you uploaded or pasted into n8n. If the HTTP request node is returning permission errors, it’s almost always missing scope or incorrect project access. Also watch for quota or rate limiting if you’re pulling reviews for many apps at once.

How many reviews can this Google Play Slack automation handle?

A lot. On n8n Cloud, your limit is mainly monthly executions, not review count, so batching matters. If you self-host, there’s no execution cap, but you’ll still want to keep batches reasonable so OpenAI and Pinecone calls don’t pile up; most small teams comfortably process hundreds of reviews per day.

Is this Google Play Slack automation better than using Zapier or Make?

For this use case, often yes. The Pinecone retrieval step and the AI agent logic are the kind of “real workflow” pieces that get awkward (or expensive) in simpler automation tools. n8n also lets you self-host for unlimited runs, which is useful if review volume jumps after a big launch. Zapier or Make can still be fine if you only want to forward raw reviews to Slack and you don’t care about digests. If you’re on the fence, Talk to an automation expert and you’ll get a straight answer for your setup.

Once this is running, reviews stop being a background chore and start showing up as a steady signal your team can act on. Set it up once, then let Slack do the reminding.

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.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.