Glassdoor to Slack, review summaries you can act on
Reading Glassdoor reviews “when you get a minute” sounds fine until you realize you are always behind. You skim a few, miss the trend, and only find out there’s a real problem when recruiting gets harder or churn quietly spikes. That’s why Glassdoor Slack automation is so useful. It turns scattered reviews into a steady signal.
This hits HR leaders first, because sentiment changes become hiring problems fast. Employer branding teams feel it too. And if you run ops at a small company, you still need the highlights without losing half a day to tabs and spreadsheets.
This workflow pulls new Glassdoor review snapshots via Bright Data, summarizes them with Google Gemini, then sends a clean, actionable digest to Slack. You’ll see how it works, what you need, and where teams usually get stuck.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Glassdoor to Slack, review summaries you can act on
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Default Data Loader", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Recursive Character Text Spl..", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Snapshot Id", pos: "b", h: 48 }
n6["<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/>Check Snapshot Status"]
n7["<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/>Download the Snapshot Response"]
n8@{ icon: "mdi:cog", form: "rounded", label: "Wait for 30 seconds", pos: "b", h: 48 }
n9@{ icon: "mdi:robot", form: "rounded", label: "Summarization of Glassdoor R..", pos: "b", h: 48 }
n10["<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/>Configure Webhook Notification"]
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/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Request to Glassdoor"]
n4 --> n7
n4 --> n8
n5 --> n6
n2 -.-> n9
n8 --> n6
n6 --> n4
n1 -.-> n9
n11 --> n5
n7 --> n9
n3 -.-> n2
n0 --> n11
n9 --> n10
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 n0 trigger
class n2,n3,n9 ai
class n1 aiModel
class n4 decision
class n6,n7,n10,n11 api
classDef customIcon fill:none,stroke:none
class n6,n7,n10,n11 customIcon
The Problem: Glassdoor Reviews Are Useful, but Painful to Track
Glassdoor is one of the few places where employees and candidates say the quiet part out loud. The problem is volume. Even mid-sized companies can rack up enough reviews that “keeping an eye on it” turns into a weekly chore. You open the site, jump between pages, try to remember what last month felt like, then paste a few quotes into Slack or a slide. It’s slow, and it’s also subjective because whoever reads first decides what “matters.” Meanwhile, leadership asks a simple question: “Are we trending up or down?” and you’re left guessing.
It adds up fast. Here’s where it usually breaks down.
- You spend about 1–2 hours a week just collecting and skimming reviews, especially if you track multiple locations or subsidiaries.
- Important changes get missed because you only see a few comments, not the pattern across the snapshot.
- Sharing insights is messy, since raw reviews don’t translate into “what do we do next?” without interpretation.
- Manual summaries drift in tone and format, which makes trend reporting feel inconsistent from month to month.
The Solution: Glassdoor Snapshots Summarized and Sent to Slack
This n8n workflow turns Glassdoor monitoring into a repeatable process. It starts by triggering a Glassdoor company scrape through the Bright Data Web Scraper API (so you’re not manually copying anything). Bright Data returns a snapshot identifier, and the workflow uses that ID to check progress until the scrape is ready. Once the snapshot is complete, n8n fetches the full results and passes the text into a summarization step built around Google Gemini. Gemini then produces a structured digest: sentiment, recurring themes, strengths, weaknesses, and noticeable red flags. Finally, the workflow sends that digest to your chosen endpoint via a webhook, which is perfect for posting into Slack channels your team already watches.
The workflow starts when you run it (manual trigger) or adapt it to run on a schedule. It polls Bright Data until the snapshot is ready, then grabs the finished response. After that, Gemini summarizes the content and n8n pushes the final summary into Slack via webhook so it lands where decisions happen.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you check Glassdoor twice a week and pull notes for two stakeholders (HR and leadership). Manually, it’s easy to spend about 45 minutes reading, then another 15 minutes writing a summary and posting it, so call it 2 hours weekly. With this workflow, you kick it off in about a minute, Bright Data runs the scrape, and Gemini produces a digest that gets posted to Slack as soon as it’s ready. Your time becomes “review the summary for 5 minutes,” not “go hunting for what changed.”
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Bright Data Web Scraper API for Glassdoor snapshot scraping
- Google Gemini to summarize reviews into themes
- Bright Data Web Unlocker token (get it from Bright Data dashboard → Web Unlocker zone)
Skill level: Intermediate. You’ll connect credentials, paste API keys, and point a webhook to your Slack incoming webhook URL.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scrape is triggered. The workflow starts with a manual trigger in n8n, then immediately calls Bright Data to request a Glassdoor company scrape. That request returns a snapshot identifier you can track.
Status gets checked until it’s ready. n8n polls Bright Data for progress, and if the snapshot isn’t complete yet, it waits about 30 seconds and checks again. This avoids false “empty result” issues and keeps your API usage reasonable.
The snapshot is fetched and prepared for AI. When the snapshot is ready, the workflow downloads the result and runs it through a text splitting and loading step. That matters when the response is long, because it helps the summarizer handle it cleanly.
Gemini creates the summary, then Slack gets the alert. Google Gemini produces an insight-focused digest, and n8n sends it to your webhook endpoint (commonly a Slack incoming webhook). You get a message your team can act on, not a wall of copied reviews.
You can easily modify the summary focus to match your internal reporting, like calling out compensation, leadership, or exit motivation. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow starts manually, then triggers the Glassdoor scrape request.
- Add the Manual Start Trigger node as the workflow trigger.
- Connect Manual Start Trigger to Trigger Glassdoor Scrape to start the scraping flow.
Step 2: Connect Bright Data and Configure Scrape Trigger
This step triggers a Bright Data dataset run for the Glassdoor page.
- Add the Trigger Glassdoor Scrape node and set Method to
POST. - Set URL to
https://api.brightdata.com/datasets/v3/trigger. - Enable Send Body, Send Query, and Send Headers.
- Set Specify Body to
jsonand paste the JSON body: - Set Query Parameters to
dataset_id=gd_l7j0bx501ockwldaqfandinclude_errors=true. - Credential Required: Connect your
httpHeaderAuthcredentials in Trigger Glassdoor Scrape.
Step 3: Store and Poll Snapshot Status
These nodes store the snapshot ID and repeatedly check readiness before fetching results.
- In Assign Snapshot Identifier, add a field named snapshot_id with value
{{ $json.snapshot_id }}. - Configure Retrieve Snapshot Progress with URL set to
=https://api.brightdata.com/datasets/v3/progress/{{ $json.snapshot_id }}. - Credential Required: Connect your
httpHeaderAuthcredentials in Retrieve Snapshot Progress. - In Branch Status Check, set the condition to check Left Value
{{ $json.status }}equalsready. - Configure Delay 30 Seconds with Amount set to
30. - Ensure the loop is connected: Assign Snapshot Identifier → Retrieve Snapshot Progress → Branch Status Check, and Branch Status Check “false” → Delay 30 Seconds → Retrieve Snapshot Progress.
Step 4: Fetch Snapshot Results
Once the snapshot is ready, the workflow fetches the results for summarization.
- Configure Fetch Snapshot Result with URL set to
=https://api.brightdata.com/datasets/v3/snapshot/{{ $('Trigger Glassdoor Scrape').item.json.snapshot_id }}. - Enable Send Query and set query parameter
formattojson. - Credential Required: Connect your
httpHeaderAuthcredentials in Fetch Snapshot Result. - Confirm the execution flow: Branch Status Check → Fetch Snapshot Result when status is ready.
Step 5: Set Up AI Summarization Chain
The summarization chain uses a data loader, text splitter, and Gemini language model.
- Open Summarize Company Details and set Operation Mode to
documentLoader. - Connect Recursive Text Segmenter to Standard Data Loader via the AI text splitter input.
- Set Recursive Text Segmenter Chunk Overlap to
100. - Connect Standard Data Loader to Summarize Company Details via the AI document input.
- Connect Gemini Chat Engine to Summarize Company Details as the language model and set Model Name to
models/gemini-2.0-flash-thinking-exp-01-21. - Credential Required: Connect your
googlePalmApicredentials in Gemini Chat Engine (credentials belong on the parent node, not the chain sub-node).
Step 6: Configure the Webhook Output
This step sends the summarized text to a webhook endpoint.
- Add Send Webhook Alert after Summarize Company Details.
- Set URL to
https://webhook.site/ce41e056-c097-48c8-a096-9b876d3abbf7. - Enable Send Body and set body parameter summary to
{{ $json.response.text }}.
Step 7: Test and Activate Your Workflow
Run a manual test to verify scraping, polling, summarization, and webhook delivery.
- Click Execute Workflow from Manual Start Trigger to start the flow.
- Confirm that Trigger Glassdoor Scrape returns a
snapshot_idand that Retrieve Snapshot Progress eventually reportsready. - Verify Fetch Snapshot Result returns data and Summarize Company Details produces a summary.
- Check the webhook endpoint to confirm Send Webhook Alert delivers the
summarypayload. - Once verified, toggle the workflow to Active for production use.
Common Gotchas
- Bright Data credentials can expire or need specific permissions. If things break, check your Bright Data Web Unlocker token and zone settings in the Bright Data dashboard 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.
Frequently Asked Questions
About 30 minutes if you already have your Bright Data token and Slack webhook.
No. You will connect accounts and paste a couple of API keys. Most of the work is choosing what you want the summary to emphasize.
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 Bright Data usage and Gemini API costs based on how often you summarize.
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.
Yes, and honestly that’s one of the best ways to use it. Update the summarization prompt in the “Summarize Company Details” step to focus on executive-ready bullets like “top 3 themes,” “what changed since last snapshot,” and “recommended actions.” You can also change the webhook payload so leadership gets a shorter version, while HR gets the full digest. If you track multiple subsidiaries, duplicate the scrape request and route each summary into a different Slack channel.
Usually it’s an invalid or expired Bearer token in your Header Auth credential. Regenerate the Web Unlocker token in Bright Data, update it in n8n, then confirm the request is pointing at the right zone. If the first call works but polling fails, you may also be hitting permission limits for the scraping product you selected. Rate limiting can show up too, especially if you run snapshots very frequently.
A lot. On n8n Cloud, your practical limit is your monthly execution allowance, while self-hosting has no hard execution cap (it’s mostly your server size). The workflow processes one snapshot per run, so most teams schedule it daily or weekly depending on volume. If you need multiple companies, you can run them in batches, just watch Bright Data usage and Gemini token limits.
Often, yes. This workflow needs polling loops, branching logic, and text handling for long responses, and n8n is simply more comfortable there without turning every extra step into an extra charge. Zapier or Make can be quicker for simple “new thing → send message” flows, but Glassdoor scraping and snapshot status checks get fiddly. If your team wants full control over prompts, formatting, and routing, n8n is a better fit. Talk to an automation expert if you want help choosing.
Set this up once and your team stops flying blind on employer sentiment. The workflow handles the repetitive stuff. You handle the decisions.
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.
