HumationHuman + Automation
Back to Catalog

TrustPilot SaaS product review tracker with Bright Data & OpenAI

Ranjan DailataRanjan Dailata
1128 views
2/3/2026
AirtableAutomatedSynchronizationOrdersShopify
Official Page

Who this is for

The TrustPilot SaaS Product Review Tracker is designed for product managers, SaaS growth teams, customer experience analysts, and marketing teams who need to extract, summarize, and analyze customer feedback at scale from TrustPilot.

This workflow is tailored for:

  • Product Managers - Monitoring feedback to drive feature improvements

  • Customer Support & CX Teams - Identifying sentiment trends or recurring issues

  • Marketing & Growth Teams - Leveraging testimonials and market perception

  • Data Analysts - Tracking competitor reviews and benchmarking

  • Founders & Executives - Wanting aggregated insights into customer satisfaction

What problem is this workflow solving?

Manually monitoring, extracting, and summarizing TrustPilot reviews is time-consuming, fragmented, and hard to scale across multiple SaaS products.

This workflow automates that process from unlocking the data behind anti-bot layers to summarizing and storing customer insights enabling teams to respond faster, spot trends, and make data-backed product decisions.

This workflow solves:

  • The challenge of scraping protected review data (using Bright Data Web Unlocker)

  • The need for structured insights from unstructured review content

  • The lack of automated delivery to storage and alerting systems like Google Sheets or webhooks

What this workflow does

Extract TrustPilot Reviews: Uses Bright Data Web Unlocker to bypass anti-bot protections and pull markdown-based content from product review pages

Convert Markdown to Text: Leverages a basic LLM chain to clean and convert scraped markdown into plain text

Structured Information Extraction: Uses OpenAI GPT-4o via the Information Extractor node to extract fields like product name, review date, rating, and reviewer sentiment

Summarization Chain: Generates concise summaries of overall review sentiment and themes using OpenAI

Merge & Aggregate Output: Consolidates individual extracted records into a structured batch output

Outbound Data Delivery:

  • Google Sheets – Appends summary and structured review data

  • Write to Disk – Persists raw and processed content locally

  • Webhook Notification – Sends a real-time alert with summarized insights

Pre-conditions

  1. You need to have a Bright Data account and do the necessary setup as mentioned in the "Setup" section below.
  2. You need to have an OpenAI Account.

Setup

  • Sign up at Bright Data.
  • Navigate to Proxies & Scraping and create a new Web Unlocker zone by selecting Web Unlocker API under Scraping Solutions.
  • In n8n, configure the Header Auth account under Credentials (Generic Auth Type: Header Authentication). Header Authentication.png The Value field should be set with the Bearer XXXXXXXXXXXXXX. The XXXXXXXXXXXXXX should be replaced by the Web Unlocker Token.
  • In n8n, Configure the Google Sheet Credentials with your own account. Follow this documentation - Set Google Sheet Credential
  • In n8n, configure the OpenAi account credentials.
  • Ensure the URL and Bright Data zone name are correctly set in the Set URL, Filename and Bright Data Zone node.
  • Set the desired local path in the Write a file to disk node to save the responses.

How to customize this workflow to your needs

Target Multiple Products :

  • Configure the Bright Data input URL dynamically for different SaaS product TrustPilot URLs

  • Loop through a product list and run parallel jobs for each

Customize Extraction Fields :

Update the prompt in the Information Extractor to include:

  • Review title
  • Response from company
  • Specific feature mentions
  • Competitor references

Tune Summarization Style

  • Change tone: executive summary, customer pain-point focus, or marketing quote extract

  • Enable sentiment aggregation (e.g., 30% negative, 50% neutral, 20% positive)

Expand Output Destinations

  • Push to Notion, Airtable, or CRM tools using additional webhook nodes

  • Generate and send PDF reports (via PDFKit or HTML-to-PDF nodes)

  • Schedule summary digests via Gmail or Slack

Trustpilot SaaS Product Review Tracker with Bright Data & OpenAI

This n8n workflow automates the process of extracting, analyzing, and storing product reviews from Trustpilot. It leverages Bright Data for web scraping, OpenAI for sentiment analysis and information extraction, and Google Sheets for data storage.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: The workflow is initiated manually, allowing you to control when the review tracking process runs.
  2. HTTP Request (Bright Data): It makes an HTTP request to the Bright Data API to scrape product reviews from a specified Trustpilot page.
  3. Code (Process Scraped Data): A Code node processes the raw data received from Bright Data, likely parsing the HTML to extract relevant review information such as review text, rating, and reviewer details.
  4. Edit Fields (Set): The extracted review data is then formatted and standardized using the Set node, preparing it for AI processing.
  5. Basic LLM Chain (Sentiment Analysis): The workflow uses an OpenAI Chat Model within a Basic LLM Chain to perform sentiment analysis on each review, determining if the review is positive, negative, or neutral.
  6. Information Extractor (Key Information): Another LangChain node, the Information Extractor, is used with the OpenAI Chat Model to identify and extract specific key information from the reviews, such as product features mentioned, common complaints, or suggestions.
  7. Merge: The sentiment analysis and extracted information are merged back with the original review data.
  8. Code (Prepare for Google Sheets): A final Code node prepares the enriched review data into a format suitable for appending to a Google Sheet.
  9. Google Sheets (Append Data): The processed and analyzed review data is appended as new rows to a designated Google Sheet, creating a structured database of product reviews.
  10. Read/Write Files from Disk (Optional): An additional Read/Write Files from Disk node is present, which could be used for temporary storage or logging of data during the process, though it's not directly connected in the provided JSON.
  11. Function (Optional): A Function node is also present but not connected, indicating a potential placeholder for custom JavaScript logic if needed.
  12. Aggregate (Optional): An Aggregate node is present but not connected, suggesting a potential for combining multiple items into a single one if required.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Bright Data Account: An account with Bright Data (formerly Luminati) to utilize their web scraping services. You will need API access.
  • OpenAI API Key: An API key for OpenAI to power the sentiment analysis and information extraction.
  • Google Account: A Google account with access to Google Sheets to store the extracted and analyzed data.
  • Google Sheets Credential: An n8n credential configured for Google Sheets.
  • OpenAI Credential: An n8n credential configured for OpenAI.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Bright Data credentials for the HTTP Request node.
    • Set up your OpenAI credentials for the "OpenAI Chat Model" nodes.
    • Set up your Google Sheets credentials.
  3. Customize Bright Data Request: In the "HTTP Request" node, update the URL and any necessary parameters to target the specific Trustpilot product page you wish to scrape.
  4. Configure Google Sheet: In the "Google Sheets" node, specify the Spreadsheet ID and Sheet Name where you want to store the data. Ensure the sheet has appropriate headers matching the data output from the workflow.
  5. Review Code Nodes: Inspect the "Code" nodes to understand how data is being parsed and transformed. Adjust if your Bright Data output or desired Google Sheet structure differs.
  6. Run the Workflow: Click "Execute Workflow" to start the process. The workflow will fetch reviews, analyze them, extract information, and store the results in your Google Sheet.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942