feat: add Revenue Leak Detector agent with HubSpot CRM + Telegram + Gmail integration by Siddharth2624 · Pull Request #5166 · aden-hive/hive

Siddharth2624 · 2026-02-20T20:25:58Z

Overview

Adds a new revenue_leak_detector agent template — an autonomous business health monitor that continuously scans a CRM pipeline, detects revenue leak patterns, sends Telegram alerts, dispatches Gmail follow-up emails to ghosted contacts, and halts automatically when severity reaches critical.

Agent Architecture

monitor ──► analyze ──► notify ──► followup
│
◄───────────────────────────┘
(loops while halt != true)

Node	Type	What it does
`monitor`	`event_loop`	Calls `scan_pipeline()` — fetches open deals from HubSpot CRM
`analyze`	`event_loop`	Calls `detect_revenue_leaks()` — classifies leaks, calculates severity
`notify`	`event_loop`	Calls `send_revenue_alert()` — prints structured report + sends Telegram alert
`followup`	`event_loop`	Calls `send_followup_emails()` — sends Gmail re-engagement emails to GHOSTED contacts

Loop exits automatically when severity = critical (halt = True).

What It Detects

Pattern	Trigger	Risk
GHOSTED	Deal silent for 21+ days	Lost deal value
STALLED	Deal stuck in same stage 10–20 days	Slow pipeline velocity
OVERDUE_PAYMENT	Invoice unpaid past due date	Cash flow leak
CHURN_RISK	3+ open support escalations	Customer churn

Integrations

HubSpot CRM (real data tested ✅)

Fetches open deals via CRM v3 API using hs_lastmodifieddate to calculate days_inactive
Batch-fetches primary contact email per deal via Associations API
Filters out closedwon / closedlost deals automatically
Falls back to empty snapshot if HUBSPOT_API_KEY is not set

Note on testing: During development, because newly created HubSpot deals always have days_inactive = 0 (their hs_lastmodifieddate is today), the GHOSTED threshold was temporarily lowered to >= 0 for demo purposes. Demo deals (DEMO-S01, DEMO-S02, DEMO-S03) were also injected to showcase all 4 leak types visually. Both of these have been reverted/removed in this PR — the agent now runs on clean production logic with the 21-day threshold.

Telegram (real delivery tested ✅)

Sends HTML-formatted alert messages with severity emoji, leak breakdown, and action items
Falls back to console output when env vars not set

Gmail SMTP (configured ✅)

Sends re-engagement emails to every GHOSTED contact with a personalized body
Dry-run preview printed to console when credentials not set

Environment Variables Required

Variable	Purpose
`HUBSPOT_API_KEY`	HubSpot Private App token (scopes: `crm.objects.deals.read`, `crm.objects.contacts.read`)
`TELEGRAM_BOT_TOKEN`	Token from @Botfather
`TELEGRAM_CHAT_ID`	Chat/group ID where alerts are delivered
`GMAIL_USER`	Gmail address used to send follow-up emails
`GMAIL_APP_PASSWORD`	Gmail App Password (requires 2FA enabled on account)

All integrations are optional — the agent runs fully offline without any credentials (console output only).

Running

# Console-only (no credentials needed)
uv run hive run examples/templates/revenue_leak_detector

# With TUI
uv run hive run examples/templates/revenue_leak_detector --tui

# Full integrations
export HUBSPOT_API_KEY="..."
export TELEGRAM_BOT_TOKEN="..."
export TELEGRAM_CHAT_ID="..."
export GMAIL_USER="..."
export GMAIL_APP_PASSWORD="..."
uv run hive run examples/templates/revenue_leak_detector --tui

Working Video of agent : https://drive.google.com/file/d/1_CqNK-SVk8j7ydqF9hEk8W8TqV99AaPL/view?usp=sharing

… Gmail integration - 4-node event_loop graph: monitor → analyze → notify → followup - Detects GHOSTED (21+ days), STALLED (10-20 days), OVERDUE_PAYMENT, CHURN_RISK - HubSpot CRM v3 API integration with contact email batch-fetch - Telegram HTML-formatted alerts via Bot API - Gmail SMTP follow-up emails to ghosted contacts - Graceful offline fallback when credentials not set - Halt loop fix: str(halt).lower() != 'true' to handle any LLM casing

…e loop

bryanadenhq

Hi @Siddharth2624, I just left some comments for you to review. Thanks for your contribution!

bryanadenhq · 2026-02-21T00:28:09Z

examples/templates/revenue_leak_detector/__init__.py

@@ -0,0 +1,7 @@
+from .agent import goal, nodes, edges


Missing agent class, default_agnet instance, and config exports. All other template export these. WIthout an agent calss, this template can't be loaded or run the same way as others.

bryanadenhq · 2026-02-21T00:29:24Z

examples/templates/revenue_leak_detector/__main__.py

+    print("  💰  REVENUE LEAK DETECTOR — Starting Agent")
+    print("=" * 64)
+
+    runner = AgentRunner.load("examples/templates/revenue_leak_detector")


Other templates don't use AgentRunner.load() in main.py, they all import and instantiate their own agent class in init.py per my previous comment.

bryanadenhq · 2026-02-21T00:29:40Z

examples/templates/revenue_leak_detector/__main__.py

+    print("=" * 64)
+
+    runner = AgentRunner.load("examples/templates/revenue_leak_detector")
+    runner._setup()


Private class, shouldn't be called directly

bryanadenhq · 2026-02-21T00:31:22Z

examples/templates/revenue_leak_detector/tools.py

+# Minimal @tool decorator (framework convention)
+# ---------------------------------------------------------------------------
+
+def tool(func):


We should be registering tools using the TOOLS dict + tool_executor() pattern.

bryanadenhq · 2026-02-21T00:31:53Z

examples/templates/revenue_leak_detector/tools.py

+
+# ---------------------------------------------------------------------------
+# Shared in-process state — survives across node calls within the same run
+_CURRENT_CYCLE_DATA: dict = {}


Globals are not thread-sage and not session-isolated.

bryanadenhq · 2026-02-21T00:32:29Z

examples/templates/revenue_leak_detector/README.md

+## Agent Graph
+
+```
+monitor ──► analyze ──► notify


readme no longer up to date

Fixed all. Please check if anything left.

…d README

Siddharth2624 added 3 commits February 20, 2026 20:08

fix: halt after MAX_CYCLES (3) when no leaks found to prevent infinit…

f8e1748

…e loop

refactor: consolidate nodes into __init__.py per repo convention

e0cb725

bryanadenhq requested changes Feb 21, 2026

View reviewed changes

fix: address PR review — TOOLS dict, agent class, contextvars, update…

13643b1

…d README

Siddharth2624 requested a review from bryanadenhq February 21, 2026 10:19

fix: typo RevenueLeakDetectorAgent (was missing 'e')

40f3c46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

feat: add Revenue Leak Detector agent with HubSpot CRM + Telegram + Gmail integration#5166

feat: add Revenue Leak Detector agent with HubSpot CRM + Telegram + Gmail integration#5166
Siddharth2624 wants to merge 5 commits intoaden-hive:mainfrom
Siddharth2624:feat/revenue-leak-detector-clean

Siddharth2624 commented Feb 20, 2026

Uh oh!

bryanadenhq left a comment

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

bryanadenhq Feb 21, 2026

Uh oh!

Siddharth2624 Feb 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Comments

Conversation

Siddharth2624 commented Feb 20, 2026

Overview

Agent Architecture

What It Detects

Integrations

HubSpot CRM (real data tested ✅)

Telegram (real delivery tested ✅)

Gmail SMTP (configured ✅)

Environment Variables Required

Running

Uh oh!

bryanadenhq left a comment

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

bryanadenhq Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Siddharth2624 Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants