Monitor G2 competitors reviews [Google Sheets, ScrapingBee, Slack]
This workflow monitor G2 reviews URLS.
When a new review is published, it will:
- trigger a Slack notification
- record the review in Google Sheets
To install it, you'll need:
- access to Slack, Google Sheets and ScrapingBee
Full guide here: https://lempire.notion.site/Scrape-G2-reviews-with-n8n-3f46e280e8f24a68b3797f98d2fba433?pvs=4
n8n Workflow: G2 Competitor Review Monitoring with ScrapingBee and Slack
This n8n workflow automates the process of monitoring competitor reviews on G2, scraping the data, storing it in Google Sheets, and notifying a Slack channel about new reviews. It's designed to keep you informed about what customers are saying about your competitors, enabling quick insights and competitive analysis.
What it does
This workflow performs the following steps:
- Schedules Execution: The workflow is triggered on a recurring schedule (e.g., daily, weekly) to check for new reviews.
- Fetches Competitor URLs: It reads a list of competitor G2 profile URLs from a specified Google Sheet.
- Scrapes G2 Reviews: For each competitor URL, it uses the HTTP Request node (likely configured with a web scraping service like ScrapingBee, given the directory name) to fetch the HTML content of the G2 review page.
- Extracts Review Data: The HTML content is then processed by the HTML node to extract specific review details (e.g., review text, rating, date, reviewer name).
- Transforms Data: A Code node is used to format and refine the extracted data, ensuring consistency and preparing it for storage and notification.
- Checks for New Reviews: It compares the newly scraped reviews with existing reviews in another Google Sheet to identify only the new ones.
- Stores New Reviews: Any newly identified reviews are appended to a Google Sheet, creating a historical record.
- Formats Slack Message: A Markdown node formats the new review information into a readable and actionable message for Slack.
- Notifies Slack Channel: The formatted message is then posted to a designated Slack channel, alerting the team to new competitor reviews.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Google Sheets Account: Configured credentials for Google Sheets to read competitor URLs and store review data.
- ScrapingBee Account (or similar web scraping service): An API key for a web scraping service capable of rendering JavaScript (like ScrapingBee) to effectively scrape G2 pages. This will be used by the HTTP Request node.
- Slack Account: Configured credentials for Slack to post notifications to a channel.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Google Sheets: Set up your Google Sheets credentials. You will need to specify the spreadsheet containing competitor URLs and the sheet where new reviews will be stored.
- HTTP Request (ScrapingBee): Configure the HTTP Request node with your ScrapingBee API key and endpoint. Ensure it's set up to fetch the HTML content of G2 review pages.
- Slack: Set up your Slack credentials and specify the channel where you want to receive notifications.
- Update Google Sheet IDs and Ranges: Modify the Google Sheets nodes to point to your specific spreadsheet IDs and sheet names/ranges for both input (competitor URLs) and output (new reviews).
- Adjust HTML Extraction: If G2's website structure changes, you might need to update the CSS selectors in the HTML node to correctly extract review data.
- Customize Slack Message: Adjust the Markdown node to tailor the content and formatting of the Slack messages to your team's preferences.
- Activate the workflow: Enable the workflow to start monitoring competitor reviews on your defined schedule.
Related Templates
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.
AI-powered document search with Oracle and ONNX embeddings for recruiting
How it works Create a user for doing Hybrid Search. Clear Existing Data, if present. Add Documents into the table. Create a hybrid index. Run Semantic search on the Documents table for "prioritize teamwork and leadership experience". Run Hybrid search for the text input in the Chat interface on the Documents table. Setup Steps Download the ONNX model allMiniLML12v2augmented.zip Extract the ZIP file on the database server into a directory, for example /opt/oracle/onnx. After extraction, the folder contents should look like: bash bash-4.4$ pwd /opt/oracle/onnx bash-4.4$ ls allMiniLML12_v2.onnx Connect as SYSDBA and create the DBA user sql -- Create DBA user CREATE USER app_admin IDENTIFIED BY "StrongPassword123" DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users; -- Grant privileges GRANT DBA TO app_admin; GRANT CREATE TABLESPACE, ALTER TABLESPACE, DROP TABLESPACE TO app_admin; Create n8n Oracle DB credentials hybridsearchuser → for hybrid search operations dbadocuser → for DBA setup (user and tablespace creation) Run the workflow Click the manual Trigger It displays Pure semantic search results. Enter search text in Chat interface It displays results for vector and keyword search. Note The workflow currently creates the hybrid search user, docuser with the password visible in plain text inside the n8n Execute SQL node. For better security, consider performing the user creation manually outside n8n. Oracle 23ai or 26ai Database has to be used. Reference Hybrid Search End-End Example