How to Set Up Territory Performance Report — Weekly Manager Alert in n8n
Every Monday morning, a sales manager opens their CRM and starts guessing. Which regions are healthy? Which are about to miss quota? The answer is buried across dozens of open deals, and by the time a
Every Monday morning, a sales manager opens their CRM and starts guessing. Which regions are healthy? Which are about to miss quota? The answer is buried across dozens of open deals, and by the time anyone spots a territory going soft, the quarter is already at risk. This article shows you how to build a workflow in n8n that scores every sales territory by weighted pipeline every Monday, flags the ones trending toward a miss, and drops a manager-ready alert into Slack or email — automatically, before deals go cold.
The problem: territory risk is invisible until it's too late
Pipeline data is not the problem. Most teams have plenty of it. The problem is that raw pipeline is a lie. A territory showing $2M in open deals can be in worse shape than one showing $800K, because that $2M is full of stalled deals, low-probability long shots, and opportunities that haven't moved a stage in six weeks. Nobody has time to read every deal every week, so managers rely on gut feel and end-of-quarter panic.
The cost of this blindness is concrete. A territory that dips below its coverage ratio in week 3 is recoverable — the rep can accelerate outbound, pull forward renewals, or get air cover from a manager. That same territory discovered in week 11 is a lost number. The difference between the two is not more data; it's a consistent, weekly, weighted read on where each region actually stands. That's a reporting cadence problem, and reporting cadence is exactly what automation solves.
The solution: a weighted pipeline score, delivered every Monday
Instead of treating all pipeline as equal, this workflow calculates a weighted pipeline score per territory. Each open deal contributes to its region's score based on a blend of amount, stage probability, and freshness (how recently it moved). The workflow then compares each territory's weighted number against its quota-coverage target, ranks regions from healthiest to most at-risk, and sends managers a single digest that says plainly: West is fine, Northeast is soft, Southeast is at risk — here's why.
The whole thing runs on a schedule with no human in the loop. It pulls from your CRM, does the math in a Code node, formats a clean summary, and posts it. Once it's live, your managers get an objective territory read every Monday at 7 a.m. without anyone lifting a finger. Below is how to build it in n8n.
Step-by-step: building it in n8n
The workflow is a linear chain of six nodes. Here's each one and the configuration that matters.
1. Schedule Trigger. Add a Schedule Trigger node as the entry point. Set the trigger interval to Cron and use the expression 0 7 * * 1 — that fires every Monday at 07:00. Set the workflow timezone (Settings → Timezone) so 7 a.m. means 7 a.m. in your managers' region, not UTC.
2. Fetch open deals. Add your CRM node — HubSpot, Pipedrive, or Salesforce. Use the "Get Many / Search Deals" operation and filter to open deals only (exclude closedwon and closedlost). Request the fields you'll need for scoring: amount, deal stage, probability, owner, close date, last-activity or last-modified date, and a territory/region property. If your CRM has no native territory field, map it from the deal owner in the next step. Enable pagination so you pull the full pipeline, not just the first page.
3. Score and aggregate (Code node). This is the brain of the workflow. Add a Code node (JavaScript) that loops every deal, computes a weighted value, and groups the results by territory. A weighted value formula that works well:
weighted = amount × stageProbability × freshnessFactor
where stageProbability comes from your CRM stage (e.g. 0.2 for discovery, 0.6 for proposal, 0.9 for verbal), and freshnessFactor decays deals that have gone stale — for example 1.0 if touched in the last 7 days, 0.7 within 14 days, 0.4 beyond 21 days. Sum the weighted values per territory, then divide by that territory's quota to get a coverage ratio. Tag each region: healthy (ratio ≥ 3.0), watch (2.0–3.0), at_risk (< 2.0). Have the node return one item per territory with its score, ratio, deal count, and status.
4. Filter to what matters (optional IF node). If your managers only want to hear about problems, add an IF node that passes territories where status is watch or at_risk. For a full weekly digest, skip this and format everything. A hybrid works best: send the full ranked list, but lead with the at-risk regions.
5. Format the digest (Set or Code node). Use a Set node or a small Code node to build a readable message. Sort territories worst-first, and for each render a line like: 🔴 Southeast — coverage 1.4x (target 3x), 12 open deals, $310K weighted, 4 deals stale >21d. Include the single biggest driver of the risk so the manager knows where to look. Keep it scannable — this is a Monday-morning glance, not a report to study.
6. Send the alert. Add a Slack node (Post Message to a #sales-leadership channel) or an Email / Gmail node. For Slack, use Blocks to bold territory names and color-code status. For per-manager routing, precede this with a loop that maps each territory to its owner and sends a targeted message instead of one broadcast. Test the full chain with the "Execute Workflow" button before you activate it, then flip the workflow to Active.
Benefits: what changes once it's running
The obvious win is time — you delete a recurring hour of manual pipeline review every week. But the real value is earlier detection. Because the score is weighted and freshness-aware, a territory that's technically "big" but actually rotting surfaces as at-risk weeks before it would in a raw-dollar view. Managers get a consistent, objective read they can act on: reallocate a rep, escalate a stalled deal, or pull forward a renewal while there's still runway.
It also standardizes the conversation. When every manager gets the same weighted score computed the same way, Monday reviews stop being debates about whose pipeline "feels" healthier and start being decisions about where to spend effort. And because it's fully automated, the cadence never slips during a busy quarter — which is exactly when territory drift is most dangerous and most likely to go unnoticed.
Common pitfalls to avoid
Trusting raw amount over weighted value. If you skip the probability and freshness factors, you've just automated the same bad gut-feel read. The weighting is the entire point — don't cut it to ship faster.
Stale stage probabilities. The formula is only as good as your stage-to-probability mapping. If your CRM stages don't reflect real conversion rates, calibrate them from historical win data before you rely on the scores. Revisit quarterly.
Missing timezone configuration. A Schedule Trigger left on UTC will fire Monday alerts at the wrong local hour — sometimes Sunday night. Set the workflow timezone explicitly.
No pagination on the CRM fetch. Large pipelines are paginated by default. If you forget to page through all results, you'll score only the first batch of deals and quietly under-report every territory. Always confirm the deal count matches your CRM total.
Alert fatigue. If everything is flagged, nothing is. Tune your at_risk threshold so only genuinely concerning territories trigger the red flag, and keep the digest to one screen. A signal managers actually read beats a comprehensive report they ignore.
Silent failures. If the CRM API times out, the workflow can finish "successfully" with zero deals and send an all-green report — the most dangerous false signal there is. Add an error branch (or n8n's Error Trigger) that pings you when the deal count is zero or the API errors, so a broken pull never looks like healthy territories.
Ja construimos isso pra voce
Nao comece do zero. O Territory Performance Report — Weekly Manager Alert e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $79 →
