Analyze sales territory performance with Bright Data MCP & GPT-4o
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 11 nodes and runs on a schedule (every week at 09:00). Along the way it connects Gmail, Google Sheets, OpenAI Chat Model and Mcp (community).
How it runs
Trigger: On a schedule (every week at 09:00).
- Prepare Request Params (Edit Fields (Set)): sets 1 field: url
- Run Bright Data Scraper (AI Agent): runs an AI agent, with model: LLM Prompt Handler; 1 tool (Bright Data MCP Tool); output parser: Auto-fixing Output Parser
- Split Stores to Items (Code): runs custom JavaScript code
- Send Notification Email (Gmail): uses Gmail
- Update Regional Data Sheet (Google Sheets): append
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-mcp is verified or supports 3.0 (used in Bright Data MCP Tool).
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - AI Agent
@n8n/n8n-nodes-langchain.agent - Gmail
n8n-nodes-base.gmail - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Mcp Client Tool
n8n-nodes-mcp.mcpClientTool - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Auto-fixing Output Parser
@n8n/n8n-nodes-langchain.outputParserAutofixing - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured
From the author
This workflow automatically analyzes sales territory performance, comparing revenue, win rates, and activity across regions. Remove the guesswork from territory planning and drive balanced growth. Overview On a weekly schedule, the workflow pulls CRM data for…