How Instantly Campaign Health Monitor Scores Outbound

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 Instantly, Slack, Google Sheets, 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. Instantly Campaign Health Monitor automates the outbound intelligence workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Campaign Health Scoring. Slack + Google Sheets Delivery.

The Instantly Campaign Health Monitor pipeline runs 4 agents in sequence. Fetcher pulls data from Instantly and Slack and Google Sheets, and Formatter delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (Code Only): Pulls campaign analytics from the Instantly V2 API for each configured campaign.
• Assembler (Code Only): Computes five CHS dimension metrics per campaign: deliverability score (bounce + spam rates), engagement trajectory (open/reply trends), domain reputation risk (warmup status + health), sequence fatigue (opt-out rates + step count), and ICP response divergence (segment variance).
• Analyst (Tier 2 Classification): Scores each CHS dimension 1-10 using defined rubrics, computes composite CHS (equal 20% weight), classifies HEALTHY/DEGRADED/CRITICAL, generates per-campaign health insights, and flags critical alerts.
• Formatter (Tier 3 Creative): Generates two outputs: (1) Slack Block Kit daily digest with per-campaign health scores, dimension highlights, and critical alerts.

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 28+3 node n8n workflow — import and deploy
• Daily weekday schedule: fires every business day at 8:00 UTC (customizable)
• Five CHS dimensions: deliverability, engagement trajectory, domain reputation, sequence fatigue, ICP response divergence
• CHS classification: HEALTHY (7-10) / DEGRADED (4-6) / CRITICAL (1-3)
• Per-campaign health insights with specific recommendations
• Critical alerts for CHS ≤ 4 or domain reputation ≤ 3
• Slack Block Kit daily digest with per-campaign scoring
• Google Sheets health dashboard with historical tracking
• Split-workflow pattern: scheduler + main pipeline (both included)
• SINGLE-MODEL: the analysis model for analysis and formatting — no the primary reasoning modelneeded
• AGGREGATE pattern: one Analyst call per daily run, not per campaign
• ITP 8/8 variations, 14/14 milestones measured

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

Step 1: Fetcher

Tier: Code Only

The pipeline starts here. Pulls campaign analytics from the Instantly V2 API for each configured campaign. Retrieves send counts, bounce rates, spam complaints, open rates, reply rates, opt-outs, and domain health indicators. Zero LLM cost.

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

Tier: Code Only

Computes five CHS dimension metrics per campaign: deliverability score (bounce + spam rates), engagement trajectory (open/reply trends), domain reputation risk (warmup status + health), sequence fatigue (opt-out rates + step count), and ICP response divergence (segment variance). Pure math. Zero LLM cost.

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

Step 3: Analyst

Tier: Tier 2 Classification

Scores each CHS dimension 1-10 using defined rubrics, computes composite CHS (equal 20% weight), classifies HEALTHY/DEGRADED/CRITICAL, generates per-campaign health insights, and flags critical alerts. the analysis model with chain-of-thought enforcement.

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

Step 4: Formatter

Tier: Tier 3 Creative

This is the final deliverable — what lands in your inbox or dashboard. Generates two outputs: (1) Slack Block Kit daily digest with per-campaign health scores, dimension highlights, and critical alerts. (2) Google Sheets row data for historical health dashboard tracking. the analysis model.

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 built 100 blueprints in 5 weeks. A RevOps team building one from scratch — scoping requirements, configuring nodes, writing prompts, testing edge cases, documenting error handling — that is 40-80 hours. The factory model works because patterns transfer. Blueprint 47 reuses structural patterns proven in blueprints 1-46.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Instantly Campaign Health Monitor scores five CHS dimensions daily across your outbound campaigns — the analysis model for analysis and formatting, daily aggregate cost.

The primary operating cost for Instantly Campaign Health Monitor is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: ~$0.03-0.08/day. 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 Daily weekday run cost ~$0.03-0.08/day ($0.66-$1.76/month), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 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.

9 files — workflow JSON (main + scheduler), system prompts, and complete documentation.

When you purchase Instantly Campaign Health Monitor, 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
• instantly_campaign_health_monitor_scheduler_v1_0_0.json — Scheduler workflow
• instantly_campaign_health_monitor_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

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.

Instantly Campaign Health Monitor is built for Sales, Sales Operations 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 sales operations 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: Instantly account (V2 API key, Growth plan+), Google account (Sheets API enabled), Slack workspace (Bot Token with chat:write scope), Anthropic API key
• You have API credentials available: Anthropic API, Instantly V2 API (httpHeaderAuth Bearer), Google Sheets (OAuth2), Slack (Bot Token, httpHeaderAuth Bearer)
• 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 send or modify Instantly campaigns — it reads analytics only, never writes
• Does not replace your email ops team — it provides daily health signals for human decision-making
• Does not work with Mailgun, SendGrid, or other ESPs — Instantly V2 API only in v1.0
• Does not predict future deliverability — it scores current campaign health from existing data
• Does not guarantee inbox placement — it identifies degrading campaigns for proactive intervention
• Does not manage domain warmup — it monitors warmup status as one dimension of domain reputation

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 send or modify Instantly campaigns — it reads analytics only, never writes

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 replace your email ops team — it provides daily health signals for human decision-making

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 work with Mailgun, SendGrid, or other ESPs — Instantly V2 API only in v1.0

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 Instantly Campaign Health Monitor bundle is designed for the following tools: n8n, Anthropic API, Instantly V2, Slack, Google Sheets. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import instantly_campaign_health_monitor_v1_0_0.json (main) and the scheduler workflow into n8n. Configure Instantly V2 API credential (httpHeaderAuth with Bearer prefix), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), Google Sheets OAuth2 credential, and Anthropic API key following the README.
2. Step 2: Configure campaign IDs and output destinations. Create a Google Sheet with column headers: Date, Campaign ID, Campaign Name, CHS Score, Deliverability, Engagement, Domain Reputation, Sequence Fatigue, ICP Divergence, Status, Alerts. Set GOOGLE_SHEET_ID and SLACK_CHANNEL in the Config Loader. Set CAMPAIGN_IDS to specific IDs or leave empty to monitor all active campaigns.
3. Step 3: Activate and verify. Enable both workflows in n8n. Send a test POST to the main workflow webhook URL with _is_itp: true and sample campaign data. Verify the health digest appears in Slack and rows append to Google Sheets. The scheduler will auto-trigger every weekday at 8:00 UTC.

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 Instantly Campaign Health Monitor product page for full specifications, pricing, and purchase.