Back to Catalog

Trustpilot insights scraper: Auto reviews via Bright Data + Google Sheets sync

Shiv GuptaShiv Gupta
280 views
2/3/2026
Official Page

Trustpilot Insights Scraper: Auto Reviews via Bright Data + Google Sheets Sync

Overview

A comprehensive n8n automation that scrapes Trustpilot business reviews using Bright Data and automatically stores structured data in Google Sheets.

Workflow Architecture

1. πŸ“ Form Trigger Node

Purpose: Manual input interface for users

  • Type: n8n-nodes-base.formTrigger
  • Configuration:
    • Form Title: "Website URL"
    • Field: "Trustpilot Website URL"
  • Function: Accepts Trustpilot URL input from users to initiate the scraping process

2. 🌐 HTTP Request (Trigger Scraping)

Purpose: Initiates scraping on Bright Data platform

  • Type: n8n-nodes-base.httpRequest
  • Method: POST
  • Endpoint: https://api.brightdata.com/datasets/v3/trigger
  • Configuration:
    • Query Parameters:
      • dataset_id: gd_lm5zmhwd2sni130p
      • include_errors: true
      • limit_multiple_results: 2
    • Headers:
      • Authorization: Bearer BRIGHT_DATA_API_KEY
    • Body: JSON with input URL and 35+ custom output fields

Custom Output Fields

The workflow extracts the following data points:

  • Company Information: company_name, company_logo, company_overall_rating, company_total_reviews, company_about, company_email, company_phone, company_location, company_country, company_category, company_id, company_website
  • Review Data: review_id, review_date, review_rating, review_title, review_content, review_date_of_experience, review_url, date_posted
  • Reviewer Information: reviewer_name, reviewer_location, reviews_posted_overall
  • Review Metadata: is_verified_review, review_replies, review_useful_count
  • Rating Distribution: 5_star, 4_star, 3_star, 2_star, 1_star
  • Additional Fields: url, company_rating_name, is_verified_company, breadcrumbs, company_other_categories

3. βŒ› Snapshot Progress Check

Purpose: Monitors scraping job status

  • Type: n8n-nodes-base.httpRequest
  • Method: GET
  • Endpoint: https://api.brightdata.com/datasets/v3/progress/{{ $json.snapshot_id }}
  • Configuration:
    • Query Parameters: format=json
    • Headers: Authorization: Bearer BRIGHT_DATA_API_KEY
  • Function: Receives snapshot_id from previous step and checks if data is ready

4. βœ… IF Node (Status Check)

Purpose: Determines next action based on scraping status

  • Type: n8n-nodes-base.if
  • Condition: $json.status === "ready"
  • Logic:
    • If True: Proceeds to data download
    • If False: Triggers wait cycle

5. πŸ•’ Wait Node

Purpose: Implements polling delay for incomplete jobs

  • Type: n8n-nodes-base.wait
  • Duration: 1 minute
  • Function: Pauses execution before re-checking snapshot status

6. πŸ”„ Loop Logic

Purpose: Continuous monitoring until completion

  • Flow: Wait β†’ Check Status β†’ Evaluate β†’ (Loop or Proceed)
  • Prevents: API rate limiting and unnecessary requests

7. πŸ“₯ Snapshot Download

Purpose: Retrieves completed scraped data

  • Type: n8n-nodes-base.httpRequest
  • Method: GET
  • Endpoint: https://api.brightdata.com/datasets/v3/snapshot/{{ $json.snapshot_id }}
  • Configuration:
    • Query Parameters: format=json
    • Headers: Authorization: Bearer BRIGHT_DATA_API_KEY

8. πŸ“Š Google Sheets Integration

Purpose: Stores extracted data in spreadsheet

  • Type: n8n-nodes-base.googleSheets
  • Operation: Append
  • Configuration:
    • Document ID: 1yQ10Q2qSjm-hhafHF2sXu-hohurW5_KD8fIv4IXEA3I
    • Sheet Name: "Trustpilot"
    • Mapping: Auto-map all 35+ fields
    • Credentials: Google OAuth2 integration

Data Flow

User Input (URL) 
    ↓
Bright Data API Call
    ↓
Snapshot ID Generated
    ↓
Status Check Loop
    ↓
Data Ready Check
    ↓
Download Complete Dataset
    ↓
Append to Google Sheets

Technical Specifications

Authentication

  • Bright Data: Bearer token authentication
  • Google Sheets: OAuth2 integration

Error Handling

  • Includes error tracking in Bright Data requests
  • Conditional logic prevents infinite loops
  • Wait periods prevent API rate limiting

Data Processing

  • Mapping Mode: Auto-map input data
  • Schema: 35+ predefined fields with string types
  • Conversion: No type conversion (preserves raw data)

Setup Requirements

Prerequisites

  1. Bright Data Account: Active account with API access
  2. Google Account: With Sheets API enabled
  3. n8n Instance: Self-hosted or cloud version

Configuration Steps

  1. API Keys: Configure Bright Data bearer token
  2. OAuth Setup: Connect Google Sheets credentials
  3. Dataset ID: Verify correct Bright Data dataset ID
  4. Sheet Access: Ensure proper permissions for target spreadsheet

Environment Variables

  • BRIGHT_DATA_API_KEY: Your Bright Data API authentication token

Use Cases

Business Intelligence

  • Competitor analysis and market research
  • Customer sentiment monitoring
  • Brand reputation tracking

Data Analytics

  • Review trend analysis
  • Rating distribution studies
  • Customer feedback aggregation

Automation Benefits

  • Scalability: Handle multiple URLs sequentially
  • Reliability: Built-in error handling and retry logic
  • Efficiency: Automated data collection and storage
  • Consistency: Standardized data format across all scrapes

Limitations and Considerations

Rate Limits

  • Bright Data API has usage limitations
  • 1-minute wait periods help manage request frequency

Data Volume

  • Limited to 2 results per request (configurable)
  • Large datasets may require multiple workflow runs

Compliance

  • Ensure compliance with Trustpilot's terms of service
  • Respect robots.txt and rate limiting guidelines

Monitoring and Maintenance

Status Tracking

  • Monitor workflow execution logs
  • Check Google Sheets for data accuracy
  • Review Bright Data usage statistics

Regular Updates

  • Update API keys as needed
  • Verify dataset ID remains valid
  • Test workflow functionality periodically

Workflow Metadata

  • Version ID: dd3afc3c-91fc-474e-99e0-1b25e62ab392
  • Instance ID: bc8ca75c203589705ae2e446cad7181d6f2a7cc1766f958ef9f34810e53b8cb2
  • Execution Order: v1
  • Active Status: Currently inactive (requires manual activation)
  • Template Status: Credentials setup completed

For any questions or support, please contact: Email or fill out this form

n8n Form Trigger to Google Sheets with Trustpilot Insights Scraper (via Bright Data)

This n8n workflow automates the process of scraping Trustpilot reviews using Bright Data, then conditionally saves the data to a Google Sheet. It's designed to be triggered manually via an n8n form, allowing users to initiate the review scraping on demand.

What it does

This workflow streamlines the following steps:

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n form. This form is expected to provide the necessary input for the Trustpilot scraper (e.g., a Trustpilot URL or company ID).
  2. Scrapes Trustpilot Reviews: It sends an HTTP request to a Bright Data API endpoint, configured to scrape Trustpilot reviews. The data from the form submission is used to parameterize this request.
  3. Conditional Data Handling: An 'If' node evaluates the response from the Bright Data scraper.
    • If successful: If the scraping operation returns valid data, the workflow proceeds to save this data.
    • If unsuccessful or no data: If the scraping fails or returns no relevant data, the workflow will wait for a short period, likely to prevent rapid retries or to allow for manual inspection.
  4. Saves to Google Sheets: If the Trustpilot scraping is successful, the extracted review data is then appended or updated in a specified Google Sheet.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Bright Data Account: An active Bright Data account with a configured Trustpilot scraper. You'll need your Bright Data API key and the specific endpoint for the scraper.
  • Google Account: A Google account with access to Google Sheets.
  • Google Sheets Credential in n8n: An n8n credential configured for Google Sheets (OAuth 2.0 or Service Account).
  • HTTP Request Credential in n8n: An n8n credential for the HTTP Request node, likely for Bright Data authentication (e.g., API Key or Basic Auth).

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up or select an existing Google Sheets credential.
    • HTTP Request (Bright Data): Set up or select an existing HTTP Request credential for Bright Data. This will typically involve providing your Bright Data API key or other authentication details.
  3. Configure Nodes:
    • On form submission (Node 1225): Review the form fields to ensure they match the expected input for your Bright Data scraper (e.g., a field for the Trustpilot URL).
    • HTTP Request (Node 19):
      • Update the URL to your specific Bright Data Trustpilot scraper API endpoint.
      • Map the data from the "On form submission" node to the parameters required by the Bright Data API (e.g., url or company_id).
      • Ensure the HTTP method (likely GET or POST) and headers are correctly configured for Bright Data.
    • If (Node 20): Configure the conditions to check for successful data retrieval from Bright Data. This might involve checking for the presence of specific keys in the response or a success status code.
    • Google Sheets (Node 18):
      • Specify the Spreadsheet ID and Sheet Name where the data should be written.
      • Map the data from the HTTP Request node (the scraped Trustpilot reviews) to the columns in your Google Sheet.
    • Wait (Node 514): This node is on the 'false' branch of the If node. You can adjust the wait duration if needed.
  4. Activate the workflow: Once configured, activate the workflow.
  5. Trigger the workflow: Access the n8n form URL (provided by the "On form submission" node) and submit the required Trustpilot details to initiate the scraping process.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β€” Manually start the workflow or schedule it to run periodically. Input Setup β€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the β€œSet Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatβ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. πŸ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing πŸ”§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation πŸ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com β†’ API keys (sidebar) Click "Create new secret key" β†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β†’ Dashboard β†’ API Keys Generate a new API key β†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βš™οΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

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