How Instantly Campaign Health Monitor Automates Outbound Intel...

Daily AI health monitoring for your Instantly outbound campaigns — scores deliverability, engagement, domain reputation, sequence fatigue, and ICP response divergence. That single sentence captures a workflow gap that costs sales, sales operations teams hours every week. The manual process behind what Instantly Campaign Health Monitor automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Instantly, Slack, Google Sheets, 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, sales operations teams handling outbound 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 Instantly Campaign Health Monitor fills.

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

Instantly Campaign Health Monitor 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 (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. Specifically, you receive:

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

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

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

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

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

Tier: Tier 3 Creative

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.

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 Formatter 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 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 ITP testing, the measured cost is: Cost per Run: see product page for current pricing. 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 Daily weekday run cost ~$0.03-0.08/day ($0.66-$1.76/month), depending on your usage volume and plan tiers.

Quality assurance: 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.

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:

• instantly_campaign_health_monitor_v1_0_0.json — The 28-node n8n main workflow (AGGREGATE daily CHS scoring)
• instantly_campaign_health_monitor_scheduler_v1_0_0.json — The 3-node scheduler workflow (weekday 8:00 UTC trigger)
• README.md — 10-minute setup guide with Instantly V2, Google Sheets, Slack credentials and split-workflow configuration
• docs/TDD.md — Technical Design Document with CHS taxonomy and SINGLE-MODEL pattern
• system_prompts/analyst_system_prompt.md — Analyst prompt (5-dimension CHS scoring + per-campaign insights)
• system_prompts/formatter_system_prompt.md — Formatter prompt (Slack daily digest + Google Sheets row data)
• 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.

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.

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.