How Contact Re-Engagement Scorer Automates Crm Enrichment

Re-engage stale contacts with AI-scored outreach timing. That single sentence captures a workflow gap that costs sales, revops teams hours every week. The manual process behind what Contact Re-Engagement Scorer automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Pipedrive, Gmail, copies it into a spreadsheet or CRM, applies a mental checklist, writes a summary, and routes it to the next person in the chain. Repeat for every record. Every day.

Three problems make this unsustainable at scale. First, the process does not scale. As volume grows, the human bottleneck becomes the constraint. Whether it is inbound leads, deal updates, or meeting prep, a person can only process a finite number of records before quality degrades. Second, the process is inconsistent. Different team members apply different criteria, use different formats, and make different judgment calls. There is no single standard of quality, and the output varies from person to person and day to day. Third, the process is slow. By the time a manual review is complete, the window for action may have already closed. Deals move, contacts change roles, and buying signals decay.

These are not theoretical concerns. They are the operational reality for sales, revops teams handling crm enrichment and deal intelligence workflows. Every hour spent on manual data processing is an hour not spent on the work that actually moves the needle: building relationships, closing deals, and driving strategy.

This is the gap Contact Re-Engagement Scorer fills.

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

Contact Re-Engagement Scorer is a multiple-node n8n workflow with 4 specialized agents. Each agent handles a distinct phase of the pipeline, and the handoff between agents is deterministic — no ambiguous routing, no dropped records. The blueprint is designed so that each agent does one thing well, and the overall pipeline produces a consistent, auditable output on every run.

Here is what each agent does:

• 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. Specifically, you receive:

• Production-ready 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

Every component is designed to be modified. The agent prompts are plain text files you can edit. The workflow nodes can be rearranged or extended. The scoring criteria, output formats, and routing logic are all exposed as configurable parameters — not buried in application code. 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

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 is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Fetcher identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

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.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Researcher identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

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 stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Analyst identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 4: Writer

Tier: Tier 2 Creative + HTTP

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.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Writer identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

The entire pipeline executes without manual intervention. From trigger to output, every decision point is deterministic: if a condition is met, the next agent fires; if not, the record is handled according to a documented fallback path. There are no silent failures. Every execution produces a traceable audit trail that you can review, export, or feed into your own reporting tools.

This architecture follows the ForgeWorkflows principle of tested, measured, documented automation. Every node in the pipeline has been validated during ITP (Inspection and Test Plan) testing, and the error handling matrix in the bundle documents the recovery path for each failure mode.

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 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 at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 20–40 minutes per cycle, that is $17–50 per execution in human labor. 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: 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.

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:

• contact_re_engagement_scorer_v1_0_0.json — The 34-node n8n workflow
• README.md — 10-minute setup guide with Pipedrive, Gmail OAuth2, and Anthropic configuration
• system_prompt_researcher.txt — Researcher system prompt (business change detection, evidence extraction)
• system_prompt_analyst.txt — Analyst system prompt (RPS scoring, 4-criteria framework, threshold logic)
• system_prompt_writer.txt — Writer system prompt (re-engagement email, tone calibration, CTA generation)
• rps_scoring_guide.md — RPS criteria weights, threshold tuning, and scoring examples
• gmail_oauth2_setup.md — Gmail OAuth2 credential setup for n8n (draft mode configuration)
• itp_results.md — ITP test results — 20 records, 14/14 milestones, 70% exact match, 100% defensible
• CHANGELOG.md — Version history

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.

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.