Monitor and track brand Sentiment on Facebook Groups with Bright data

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Workflow documentation updated on 21 May 2025 This workflow keeps track of your brand mentions across different Facebook groups and provides an analysis of the posts as positive, negative or neutra...

Best for

Market Research automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.switch, n8n-nodes-base.wait, n8n-nodes-base.limit, @n8n/n8n-nodes-langchain.sentimentanalysis, n8n-nodes-base.filter, @n8n/n8n-nodes-langchain.lmchatopenrouter, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Zacharia Kimotho.

Original n8n.io source

1.1 Workflow description

Title: Monitor and track brand Sentiment on Facebook Groups with Bright data
Workflow name: Monitor and track brand Sentiment on Facebook Groups with Bright data

Workflow documentation updated on 21 May 2025

This workflow keeps track of your brand mentions across different Facebook groups and provides an analysis of the posts as positive, negative or neutral and updates this to Googe sheets for further analysis

This is useful and relevants for brands looking to keep track of what people are saying about their brands and guage the customer satisfaction or disatisfaction based on what they are talking about

Who is this template for?

This workflow is for you if You

Need to keep track of your brand sentiments across different niche facebook groups
Own a saas and want to monitor it across different local facebook Groups
Are looking to do some competitor research to understand what others dont like about their products
Are testing the market on different market offerings and products to get best results
Are looking for sources other that review sites for product, software or service reviews
Need to keep track of your brand sentiments across different niche facebook groups
Are starting on market research and would like to get insights from differnt facebook groups on app usage, strngths weaknesses, features etc

How it works

You will set the desired schedule by which to monitor the groups This gets the brand names and facebook Groups to monitor.

Setup Steps

Before you begin You will need access to a Bright Data API to run this workflows Make a copy of the sheet below and add the urls for the facebook groups to scrap and the brand names you wish to monitor.

Import the workflow json to your canvas
Make a copy of this Google sheet to get started easily
Set your APi key in the Set up KEYs node
Map out the Google sheet to your tables
You can use/update the current AI models to differnt models eg Gemini or anthropic
Run the workflow

Setup B

Bright Data provides an option to receive the results on an external webhook via a POST call. This can be collected via the recieve results webhook node and passed to a google sheet

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - facebook groups

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 2 - get progress

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 3 - Switch

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.2

Block 4 - Wait

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 5 - Get data

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 6 - Limit

Type / Role: n8n-nodes-base.limit - limit
Config choices: Version 1

Block 7 - Sentiment Analysis

Type / Role: @n8n/n8n-nodes-langchain.sentimentAnalysis - sentimentAnalysis
Config choices: Version 1

Block 8 - Filter brand name

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 9 - OpenRouter Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 10 - Merge

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.1

Block 11 - Set up KEYS

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 13 - Split Out

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 14 - set urls

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 15 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 16 - Information Extractor

Type / Role: @n8n/n8n-nodes-langchain.informationExtractor - informationExtractor
Config choices: Version 1

Block 17 - OpenRouter Chat Model1

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 18 - pull group results

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 19 - insights and sentiments

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 20 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 37 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Monitor and track brand Sentiment on Facebook Groups with Bright data
Complexity	advanced
Nodes	37
Categories	Market Research, AI Summarization
Author	Zacharia Kimotho
Published	20 May 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/4235/4235.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Market Research workflows AI Summarization workflows

Frequently asked questions

What does Monitor and track brand Sentiment on Facebook Groups with Bright data do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI Summarization use case.

Zacharia Kimotho

22 workflows

Nodes

n8n-nodes-base.httprequest n8n-nodes-base.switch n8n-nodes-base.wait n8n-nodes-base.limit @n8n/n8n-nodes-langchain.sentimentanalysis n8n-nodes-base.filter @n8n/n8n-nodes-langchain.lmchatopenrouter n8n-nodes-base.merge

Complexity

advanced

Published 20 May 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/4235/4235.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Monitor and track brand Sentiment on Facebook Groups with Bright data

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Workflow documentation updated on 21 May 2025

Who is this template for?

How it works

Setup Steps

Setup B

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - facebook groups

Block 2 - get progress

Block 3 - Switch

Block 4 - Wait

Block 5 - Get data

Block 6 - Limit

Block 7 - Sentiment Analysis

Block 8 - Filter brand name

Block 9 - OpenRouter Chat Model

Block 10 - Merge

Block 11 - Set up KEYS

Block 12 - Schedule Trigger

Block 13 - Split Out

Block 14 - set urls

Block 15 - Sticky Note

Block 16 - Information Extractor

Block 17 - OpenRouter Chat Model1

Block 18 - pull group results

Block 19 - insights and sentiments

Block 20 - Sticky Note1

Block 21 - Sticky Note2

Block 22 - Sticky Note3

Block 23 - Sticky Note4

Block 24 - Sticky Note5

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions