Monitor Google Maps reviews with sentiment analysis & RAG agent using Pinecone

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

Analyze and Sync Google Maps Reviews to Pinecone Note: This template requires an Apify account, an OpenAI account, and a Pinecone database. Overview This workflow automates your reputation man...

Best for

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

Tools used

n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.wait, n8n-nodes-base.telegram, n8n-nodes-base.telegramtrigger, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.vectorstorepinecone

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Monitor Google Maps reviews with sentiment analysis & RAG agent using Pinecone
Workflow name: Monitor Google Maps reviews with sentiment analysis & RAG agent using Pinecone

Analyze and Sync Google Maps Reviews to Pinecone

> Note: This template requires an Apify account, an OpenAI account, and a Pinecone database.

Overview

This workflow automates your reputation management by scraping Google Maps reviews, analyzing their sentiment using AI, and storing them in a Vector Database (Pinecone). It also includes a RAG (Retrieval-Augmented Generation) agent that allows you to chat with your review data via Telegram to ask specific questions about customer feedback.

How it works

Scrape: At a scheduled time (or manually), the workflow triggers an Apify actor to scrape the latest reviews from a specific Google Maps URL.
Analyze: It uses GPT-4o to analyze the sentiment of the reviews and generates a summary of complaints and praises.
Notify: A Telegram message is sent with the sentiment score and a summary of the latest reviews.
Store: The review data is embedded and upserted into a Pinecone Vector Store.
Chat (RAG): You can send messages to a Telegram bot to query the database (e.g., "What are people saying about our coffee?"). The AI retrieves relevant reviews from Pinecone to answer your question.
Cleanup: A weekly schedule cleans up the namespace to ensure data freshness (optional).

How to set up

Apify: Create an account and subscribe to the Google Maps Reviews Scraper actor. Set up your Apify credentials in n8n.
OpenAI: Set up your OpenAI credentials in n8n.
Pinecone: Create an Index in Pinecone. Set up your Pinecone credentials in n8n.
Telegram: Create a new bot via BotFather to get your Token and Chat ID. Set up your Telegram credentials in n8n.

Configure the Workflow

Open the ⚠️ CONFIGURATION nodes.
Paste your telegram_chat_id.
Paste the Maps_url of the business you want to monitor.
Define your pinecone_namespace.

HTTP Node Configuration

In the "Empty Namespace" node, update the URL to match your Pinecone Index Host and add your Pinecone API Key in the header or use credentials.

🙋 Support

If you encounter any issues during setup or have questions about customization, please reach out to our dedicated support email: [email protected]

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 - Format Data (Reviews)

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

Block 2 - Sticky Note

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

Block 3 - Trigger at midnight

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

Block 4 - Wait 5s

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

Block 5 - ⚠️ CONFIGURATION2

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

Block 6 - ⚠️ CONFIGURATION1

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

Block 7 - Send a text message

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

Block 8 - Telegram Trigger

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

Block 9 - Sticky Note6

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

Block 10 - Embeddings OpenAI1

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

Block 11 - Pinecone Search Tool

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

Block 12 - OpenAI Chat Model

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

Block 13 - AI Data Analyst

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.6

Block 14 - Confirmation text

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

Block 15 - Sticky Note5

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

Block 16 - Empty Namespace (Keep DB)

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

Block 17 - Every Sunday at 11pm

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

Block 18 - Sticky Note1

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

Block 19 - Sticky Note4

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

Block 20 - Sticky Note3

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 Note7

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

Block 23 - Default Data Loader

Type / Role: @n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices: Version 1.1

Block 24 - Send Alert

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

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

3. Summary Table

Workflow	Monitor Google Maps reviews with sentiment analysis & RAG agent using Pinecone
Complexity	advanced
Nodes	38
Categories	Market Research, AI RAG
Author	Gtaras
Published	01 Dec 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/11381/11381.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 RAG workflows

Frequently asked questions

What does Monitor Google Maps reviews with sentiment analysis & RAG agent using Pinecone do?

Analyze and Sync Google Maps Reviews to Pinecone Note: This template requires an Apify account, an OpenAI account, and a Pinecone database. Overview This workflow automates your reputation man...

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 RAG use case.

Gtaras

4 workflows

Nodes

n8n-nodes-base.set n8n-nodes-base.stickynote n8n-nodes-base.scheduletrigger n8n-nodes-base.wait n8n-nodes-base.telegram n8n-nodes-base.telegramtrigger @n8n/n8n-nodes-langchain.embeddingsopenai @n8n/n8n-nodes-langchain.vectorstorepinecone

Complexity

advanced

Published 01 Dec 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/11381/11381.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 Google Maps reviews with sentiment analysis & RAG agent using Pinecone

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Analyze and Sync Google Maps Reviews to Pinecone

Overview

How it works

How to set up

Configure the Workflow

HTTP Node Configuration

🙋 Support

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Format Data (Reviews)

Block 2 - Sticky Note

Block 3 - Trigger at midnight

Block 4 - Wait 5s

Block 5 - ⚠️ CONFIGURATION2

Block 6 - ⚠️ CONFIGURATION1

Block 7 - Send a text message

Block 8 - Telegram Trigger

Block 9 - Sticky Note6

Block 10 - Embeddings OpenAI1

Block 11 - Pinecone Search Tool

Block 12 - OpenAI Chat Model

Block 13 - AI Data Analyst

Block 14 - Confirmation text

Block 15 - Sticky Note5

Block 16 - Empty Namespace (Keep DB)

Block 17 - Every Sunday at 11pm

Block 18 - Sticky Note1

Block 19 - Sticky Note4

Block 20 - Sticky Note3

Block 21 - Sticky Note2

Block 22 - Sticky Note7

Block 23 - Default Data Loader

Block 24 - Send Alert

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