How Pipeline Hygiene Auditor Automates Pipeline Hygiene

Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Pipedrive, Notion, Slack, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.

The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Pipeline Hygiene Auditor automates the pipeline hygiene and data quality workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Weekly Pipeline Hygiene. A-F Grade per Pipeline.

The Pipeline Hygiene Auditor pipeline runs 4 agents in sequence. The Fetcher pulls data from Pipedrive and Notion and Slack, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Retrieves all deals from configured Pipedrive pipelines — deal value, stage, close date, owner, activity history, required field completeness, and stage entry timestamps.
• The Auditor (Code-only): Evaluates each deal against 7 weighted hygiene violation categories: stale_close_date (20%) — close date in the past, zombie_deal (20%) — no activity beyond threshold, missing_fields (15%) — required fields incomplete, ghost_deal (15%) — no activities ever logged, value_mismatch (10%) — value outside stage benchmark, stage_squatter (10%) — exceeds stage duration benchmark, orphan_activity (10%) — recent activity but no owner assignment..
• The Scorer (Tier 2 Classification): Computes weighted hygiene scores per deal and aggregates to per-rep and per-pipeline scores.
• The Formatter (Tier 3 Creative): Generates a Notion weekly hygiene report with pipeline grade, per-category violation counts, worst-offending deals, per-rep scorecards, and prioritized remediation list.

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• ITP-tested n8n workflow (24 nodes + 3-node scheduler)
• 7-category weighted hygiene audit (stale_close_date, zombie_deal, missing_fields, ghost_deal, value_mismatch, stage_squatter, orphan_activity)
• A-F pipeline grade with per-rep scorecards
• Prioritized remediation list ranked by deal value × violation severity
• Week-over-week trend tracking
• Notion weekly hygiene report with full breakdown
• Slack digest with pipeline grade and top 5 violations
• Configurable: pipeline IDs, required fields, stage benchmarks, activity thresholds
• Full technical documentation and system prompts

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Pipeline Hygiene Auditor adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Pipeline Hygiene Auditor execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Retrieves all deals from configured Pipedrive pipelines — deal value, stage, close date, owner, activity history, required field completeness, and stage entry timestamps. Pulls rep-level deal counts for per-rep scoring.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Auditor

Tier: Code-only

Evaluates each deal against 7 weighted hygiene violation categories: stale_close_date (20%) — close date in the past, zombie_deal (20%) — no activity beyond threshold, missing_fields (15%) — required fields incomplete, ghost_deal (15%) — no activities ever logged, value_mismatch (10%) — value outside stage benchmark, stage_squatter (10%) — exceeds stage duration benchmark, orphan_activity (10%) — recent activity but no owner assignment.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: The Scorer

Tier: Tier 2 Classification

Computes weighted hygiene scores per deal and aggregates to per-rep and per-pipeline scores. Assigns pipeline grade: A (≥90), B (80-89), C (70-79), D (60-69), F (<60). Generates remediation priority list ranked by deal value × violation severity.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Formatter

Tier: Tier 3 Creative

This is the final deliverable — what lands in your inbox or dashboard. Generates a Notion weekly hygiene report with pipeline grade, per-category violation counts, worst-offending deals, per-rep scorecards, and prioritized remediation list. Posts Slack digest with pipeline grade, top 5 violations, and week-over-week trend.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

3 of 10 leads scored below threshold during ITP testing. The testing agent tried to relax criteria — "if we lower the threshold to 5, all 10 pass." We rejected it. The fix was the pipeline, not the criteria. Acceptance criteria is locked before testing begins. Post-hoc relaxation is how you ship broken products.

— ForgeWorkflows Engineering

Weekly pipeline hygiene audit with 7 weighted violation categories, per-deal and per-rep scoring, A-F pipeline grade, and prioritized remediation delivered via Notion and Slack.

The primary operating cost for Pipeline Hygiene Auditor is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.05–$0.15 per run. This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is Weekly cost ~$0.05-0.15/run (~$0.20-0.60/month), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 8/8 records, all milestones PASS. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

6 files. Main workflow + scheduler + prompts + docs.

When you purchase Pipeline Hygiene Auditor, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• pipeline_hygiene_auditor_v1_0_0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter system prompt
• workflow/pha_scheduler_v1_0_0.json — Scheduler workflow

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Pipeline Hygiene Auditor is built for Revops, Sales teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a revops or sales function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Pipedrive CRM with active pipelines, Anthropic API key, Notion workspace, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, Pipedrive (API Token), Notion (httpHeaderAuth Bearer), Slack (Bot Token, httpHeaderAuth Bearer, chat:write)
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not modify or update Pipedrive deals — read-only audit with reports as output
• Does not auto-fix hygiene issues — it identifies and prioritizes violations for human remediation
• Does not replace CRM configuration — it audits deal data against your configured standards
• Does not score deal quality or win probability — focused exclusively on data hygiene
• Does not monitor real-time deal changes — weekly batch analysis for trend tracking

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not modify or update Pipedrive deals — read-only audit with reports as output

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not auto-fix hygiene issues — it identifies and prioritizes violations for human remediation

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not replace CRM configuration — it audits deal data against your configured standards

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Pipeline Hygiene Auditor bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import both workflow JSON files into n8n (main + scheduler). Configure Pipedrive API Token, Notion API token (httpHeaderAuth with Bearer prefix), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure pipelines and hygiene thresholds. Set PIPELINE_IDS (array of Pipedrive pipeline IDs), STALE_CLOSE_DATE_DAYS (default 0, meaning any past date), ACTIVITY_RECENCY_DAYS (default 14), REQUIRED_FIELDS (array of field keys), STAGE_BENCHMARKS (stage name to max days mapping), NOTION_DATABASE_ID, and SLACK_CHANNEL in the scheduler Build Payload node.
3. Step 3: Activate scheduler and verify. Update the webhook URL in the scheduler to match your main workflow webhook path. Activate both workflows. Send a test POST with _is_itp: true and sample deal data. Verify the hygiene report appears in Notion and the grade digest appears in Slack.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Pipeline Hygiene Auditor product page for full specifications, pricing, and purchase.