How Contact Re-Engagement Scorer Automates Crm Enrichment

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, Gmail, 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. Contact Re-Engagement Scorer automates the crm enrichment and deal intelligence workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Weekly Stale Contact Scan. Scored Re-Engagement Outreach.

The Contact Re-Engagement Scorer pipeline runs 4 agents in sequence. Fetcher pulls data from Pipedrive and Gmail, and Writer delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (HTTP + Code): Dual-trigger activation: weekly schedule or on-demand webhook.
• Researcher (Tier 1 Reasoning + Web Search): the analysis model researches each stale contact's company via web search for business change signals: new funding rounds, leadership changes, product launches, market expansion, and organizational restructuring.
• Analyst (Tier 1 Reasoning): the primary reasoning model scores each contact on Re-Engagement Potential (RPS) across 4 weighted criteria: Timing Relevance (how ripe is the window), Business Change Signals (detected via web search), Relationship Strength (historical interaction quality), and Re-Engagement Ease (email available, past responsiveness).
• Writer (Tier 2 Creative + HTTP): the analysis model generates personalized re-engagement emails for HIGH-scored contacts, referencing specific business changes and past relationship context.

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 34-node n8n workflow — import and deploy
• Weekly automated scan of Pipedrive contacts inactive 90+ days
• automated web research for business change signals at contact companies
• RPS scoring across 4 criteria: Timing Relevance, Business Changes, Relationship Strength, Re-Engagement Ease
• 3-way routing: HIGH (email + activity + note), MEDIUM (note), LOW (log)
• Personalized re-engagement emails referencing specific business changes
• the primary reasoning model Analyst + the analysis model Researcher/Writer at $0.234/contact
• Companion to LDRA (lost deals), CIA (contact enrichment), CDD (data decay)
• ITP test results with 20 records and 14/14 milestones

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Contact Re-Engagement Scorer 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 Contact Re-Engagement Scorer execution flow.

Step 1: Fetcher

Tier: HTTP + Code

The pipeline starts here. Dual-trigger activation: weekly schedule or on-demand webhook. Pulls all contacts from Pipedrive, filters to those inactive for 90+ days (configurable window). Extracts contact metadata, deal history, activity timeline, and last interaction date. Contacts with recent activity are filtered immediately — no wasted processing on active relationships.

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: Researcher

Tier: Tier 1 Reasoning + Web Search

the analysis model researches each stale contact's company via web search for business change signals: new funding rounds, leadership changes, product launches, market expansion, and organizational restructuring. Returns structured evidence with source URLs. No LinkedIn scraping — public news and company announcements only.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: Analyst

Tier: Tier 1 Reasoning

the primary reasoning model scores each contact on Re-Engagement Potential (RPS) across 4 weighted criteria: Timing Relevance (how ripe is the window), Business Change Signals (detected via web search), Relationship Strength (historical interaction quality), and Re-Engagement Ease (email available, past responsiveness). Contacts below the configurable RPS threshold are filtered — only high-potential re-engagements proceed.

This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 4: Writer

Tier: Tier 2 Creative + HTTP

This is the final deliverable — what lands in your inbox or dashboard. the analysis model generates personalized re-engagement emails for HIGH-scored contacts, referencing specific business changes and past relationship context. 3-way routing: HIGH contacts get email draft + Pipedrive activity + note. MEDIUM contacts get a Pipedrive note only. LOW contacts are logged for future review. Non-blocking writes ensure each output completes independently.

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.

We never grep for API keys in the filesystem. We never search shell history for tokens. Every credential lives in n8n's encrypted credential store, accessed by credential name — not by value. If a credential is missing, the blueprint tells you which credential name to create. It never tells you to paste a key into a code node.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Contact Re-Engagement Scorer scans your Pipedrive CRM weekly for dormant contacts, researches business changes, scores re-engagement potential across 4 criteria, and generates personalized outreach at $0.234/contact.

The primary operating cost for Contact Re-Engagement Scorer is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Contact: $0.234/contact (ITP-measured average). 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 $5–10/month (20 contacts/week), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20 records, 14/14 milestones PASS, 70% exact, 100% defensible. 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.

9 files — workflow JSON, system prompts, configuration guides, and complete documentation.

When you purchase Contact Re-Engagement Scorer, 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
• contact_re_engagement_scorer_v1.0.0.json — n8n workflow (main pipeline)
• docs/TDD.md — Technical Design Document
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/researcher_system_prompt.md — Researcher system prompt
• system_prompts/writer_system_prompt.md — Writer system prompt

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.

Contact Re-Engagement Scorer is built for Sales, Revops 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 sales or revops 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 (any plan), Gmail account
• You have API credentials available: Anthropic API, Pipedrive API, Gmail OAuth2
• 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 monitor active deals or deal movement — that is what Deal Intelligence Agent and Deal Stall Diagnoser do
• Does not re-activate lost deals — that is what Lost Deal Re-Activation Agent does
• Does not scrape LinkedIn or personal social profiles — public news only
• Does not auto-send emails — creates Gmail drafts for rep review
• Does not work with HubSpot, Salesforce, or other CRMs — Pipedrive only

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 monitor active deals or deal movement — that is what Deal Intelligence Agent and Deal Stall Diagnoser do

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 re-activate lost deals — that is what Lost Deal Re-Activation Agent does

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 scrape LinkedIn or personal social profiles — public news only

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 Contact Re-Engagement Scorer bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Gmail. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import contact_re_engagement_scorer_v1_0_0.json into n8n. Configure Pipedrive API token, Anthropic API key, and Gmail OAuth2 credentials following the setup guides.
2. Step 2: Configure inactivity window and RPS threshold. Set the contact inactivity window (default: 90+ days) and RPS score thresholds for HIGH/MEDIUM/LOW routing. Review the RPS scoring guide for criteria definitions.
3. Step 3: Activate and verify. Enable the workflow in n8n. Wait for the next weekly run or trigger manually via webhook. Verify Gmail drafts appear with personalized re-engagement emails and Pipedrive notes are created.

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 Contact Re-Engagement Scorer product page for full specifications, pricing, and purchase.