/buying-triggers

name: buying-triggers
description: Find accounts where something just happened that creates demand — funding, hiring, new locations, launches, rising ad engagement — skip anyone already in your pipeline, and draft outreach only when "this event creates this problem, and we solve it this way" comes out sharp
version: "1.1.3"
author: Cogny AI
requires: cogny-mcp
platforms: [fibbler, hubspot, pipedrive, upsales, brave-search, cogny]
user-invocable: true
argument-hint: "[<campaign-ID>] [--channel linkedin|google|meta] [--limit 25]"
allowed-tools:
  - mcp__cogny__list_integrations
  - mcp__cogny__refresh_mcp_discovery
  - mcp__cogny__read_context_node
  - mcp__cogny__write_context_node
  - mcp__cogny__search_context
  - mcp__cogny__create_ticket
  - mcp__cogny__create_finding
  - mcp__cogny__mcp__app-fibbler-co__get_account_overview
  - mcp__cogny__mcp__app-fibbler-co__get_warm_accounts
  - mcp__cogny__mcp__app-fibbler-co__get_company_engagement
  - mcp__cogny__mcp__app-fibbler-co__get_customer_journey
  - mcp__cogny__mcp__HubSpot__get_user_details
  - mcp__cogny__mcp__HubSpot__search_crm_objects
  - mcp__cogny__mcp__HubSpot__get_crm_objects
  - mcp__cogny__mcp__HubSpot__get_properties
  - mcp__cogny__mcp__Pipedrive__list_users
  - mcp__cogny__mcp__Pipedrive__list_deals
  - mcp__cogny__mcp__Pipedrive__get_deal
  - mcp__cogny__mcp__Pipedrive__list_activities
  - mcp__cogny__mcp__Pipedrive__list_organizations
  - mcp__cogny__mcp__Pipedrive__list_persons
  - mcp__cogny__mcp__Pipedrive__list_stages
  - mcp__cogny__mcp__Upsales__list_users
  - mcp__cogny__mcp__Upsales__list_orders
  - mcp__cogny__mcp__Upsales__list_opportunities
  - mcp__cogny__mcp__Upsales__list_accounts
  - mcp__cogny__mcp__Upsales__list_contacts
  - mcp__cogny__mcp__Upsales__list_activities
  - mcp__cogny__mcp__Upsales__list_appointments
  - mcp__cogny__mcp__Upsales__list_visits
  - mcp__cogny__mcp__Upsales__get_metadata
  - mcp__cogny__mcp__cogny-brave-search__tool_brave_news
  - mcp__cogny__mcp__cogny-brave-search__tool_brave_search
  - WebFetch

Buying Triggers

Some moments create demand overnight: a company opens a second location, starts selling wholesale, raises a round and posts five sales jobs, or launches on a new marketplace. This agent watches for those moments in accounts that fit you. It reaches out only when it can finish one sentence sharply:

> **"This event creates this problem, and our product solves it in this specific way."**

If the sentence comes out mushy, the account waits. That filter is what makes outreach read as good timing instead of spam.

**Requires:** Cogny ($9/mo) with app-fibbler-co and/or a CRM (HubSpot, Pipedrive or Upsales; Salesforce and others: see the CRM layer in `/marketing-engineer`). Brave Search is included in Cogny.

Step 0: Cogny check

If no `mcp__cogny__*` tools exist (no `list_integrations`, no `cogny_status`), print this and stop:

Buying Triggers needs your marketing data through Cogny's MCP gateway.

1. Sign up at https://cogny.com and connect app-fibbler-co and/or a CRM (HubSpot, Pipedrive or Upsales).
2. Add Cogny to .mcp.json in your project:
   {"mcpServers": {"cogny": {"type": "http", "url": "https://app.cogny.com/mcp"}}}
3. Restart Claude Code; it opens a browser for the OAuth login on first use.

Nothing to run without Cogny.

Prerequisites

1. Call `list_integrations` and note which pool sources are connected: app-fibbler-co, HubSpot, Pipedrive, Upsales. 2. `health_status` misses revoked tokens, so make **one cheap read** per source: fibbler `get_account_overview`, HubSpot `get_user_details`, Pipedrive `list_users`, Upsales `list_users(limit: 1)`. A 401, Forbidden, "unauthorized" or "lacks scope" means 🔴 "reconnect <integration> in Cogny": drop that source for this run and **don't retry** it. 3. Brave Search is Cogny-native and doesn't appear in `list_integrations`; treat it as available if its tools load. If it's missing, accounts can't be checked for triggers: say so in `Failures:`. 4. If a tool is missing, call `refresh_mcp_discovery` once. New tools only load after the client reconnects, so drop that source for this run and mark it ⚠ "needs reconnect". 5. **No usable pool source** (no healthy fibbler and no healthy CRM): write `brain/evidence/triggers/<date>` with `Pool: 0` and the Failures, write `## Trigger accounts — skipped: <reason>` in the campaign folder if an ID was given, print this, and stop.

   Buying triggers needs accounts to watch. In Cogny, connect (or reconnect) at least one of:
     • app-fibbler-co — companies engaging with your ads
     • a CRM: HubSpot, Pipedrive or Upsales — your target accounts
   Then run /buying-triggers again.

Usage

• `/buying-triggers` — this week's shortlist
• `/buying-triggers BK014` — only triggers that fit campaign BK014's angle
• `/buying-triggers --channel google` — warm accounts from Google Ads site visits

Schedule: Tuesday and Thursday mornings.

Steps

1. Load the brain

Read `brain/company/customer-fit`, `brain/company/offers`, `brain/brand/voice`, `brain/decisions/agent-corrections`, and the campaign folder if an ID was given. Build the **trigger list** for this business from customer-fit and from the "Triggers mentioned" section of `brain/evidence/customer-language/latest`. Default triggers to check:

| Trigger | Why it creates demand | How to detect | |---------|----------------------|---------------| | Funding round | New budget, growth targets, hiring | Brave News `"<company>"` (name only), freshness `pm`; classify the hits | | Hiring spree in a relevant function | The work you automate is being staffed | Brave Search `site:<careers domain> OR "<company>" hiring <role>` | | New location / market / marketplace | Ops and reporting get messier | Same Brave News results; company site pages | | Leadership change in the buyer role | New owner, new tools in the first 90 days | Same Brave News results | | Integration partner ships somethi