Catch HubSpot deals that went quiet before they slip

Every Wednesday: open HubSpot deals with no logged activity in 14 days or more, and one question on which of them to follow up.

Runs
Wednesdays at 9:00
Uses
HubSpot
For
Sales
Posts
Asks you

From your apps to your board

How the skill works: your agent reads deals with old activity from HubSpot, wednesdays at 9:00, and gives you a question for you and a telegram ping and the report in the chat.

Reads

  • HubSpotDeals with old activity
reads
Your agentClaude Code, Codex, Cursor or GeminiWednesdays at 9:00
posts

You get

  • A question for youOn your board, answered with a tap
  • A Telegram pingOnly when it needs your answer, if you connect Telegram
  • The report in the chatEvery run, with or without Briefkin

What you get

  • Quiet deals: open deals with no activity in 14 days or more, largest first, with owner, stage, days silent and the last touch.
  • The ask: which of them to follow up.
  • After you answer: a task on each chosen deal for its owner, with a check-in draft.

The card on the right is a sample. Yours shows your own numbers and updates in place every run.

What lands on your board

AcmeHubSpot stale deals · Claude Code

7 open deals with no activity in 14+ days

Which of these deals should get a follow-up task for their owner?

$214,000 of open pipeline has had no logged call, email or meeting for two weeks or more. The quietest, Woodgrove Bank, last heard from us 37 days ago.

DealOwnerAmountStageSilentLast touch
Woodgrove BankTheo$54,000Presentation scheduled37 daysDemo, Sep 9
RelecloudMarco$46,000Decision maker bought-in21 daysEmail, Sep 25
Alpine Ski HouseLena$33,000Qualified to buy31 daysCall, Sep 15
Lucerne PublishingDana$28,000Contract sent16 daysNote, Sep 30
Wide World ImportersSam$24,000Appointment scheduled19 daysEmail, Sep 27
Margie's TravelPriya$17,000Qualified to buy15 daysCall, Oct 1
VanArsdelDana$12,000Presentation scheduled14 daysMeeting, Oct 2
Resolve
An example with made-up numbers. Your agent posts your real ones.

What it does

Fourteen days without a logged call, email or meeting is usually the point where a deal stops being late and starts being lost. HubSpot will show you those deals if you filter Last Activity Date by hand; most teams find them at the end of the quarter instead.

This skill checks every Wednesday, lists the quiet deals with amount, owner and what last happened, and asks one question: which ones get a follow-up? Answer on the card and the agent creates a task for each owner, with a two-line check-in they can send.

How it works

  1. 1Find deals with old activity

    Search POST /crm/v3/objects/deals/search with two filter groups, which HubSpot ORs together: notes_last_updated LT 14 days ago, and notes_last_updated NOT_HAS_PROPERTY with createdate LT 14 days ago. Put dealstage NOT_IN the closed stages in both groups.

  2. 2

    2Skip deals that are already handled

    Drop deals whose notes_next_activity_date is in the future, since someone already has a task or meeting booked, and deals with a close date more than 90 days out unless you ask for them.

  3. 3Read the last touch

    For each remaining deal, list its calls, emails, meetings and notes with GET /crm/v4/objects/deals/{dealId}/associations/{type} and read the newest by hs_timestamp, so the card can say "Call, Sep 15" instead of just a number of days.

  4. 4

    4Ask who to chase

    Post the list, largest amount first, with days silent, stage, owner and last touch, and ask which deals should get a follow-up.

  5. 5Create the follow-ups

    Read your choice from Briefkin with GET /v1/cards/hubspot-stale-deals (it is in response). For each chosen deal, create a task for its owner with POST /crm/v3/objects/tasks, associated to the deal and due the next working day, with a short check-in draft in the body.

  6. Post it to the board

    With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.

Install and run it

Pick your agent, where the data comes from and how to schedule it; the commands below follow.

Agent
Data
Schedule
  1. Install the skill

    One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.

    shellcurl -fsSL https://briefkin.dev/skills/hubspot-stale-deals/install | sh
  2. Run it

    Ask Claude Code:

    promptRun the hubspot-stale-deals skill

    Or paste the prompt instead of installing:

    promptFind open deals in HubSpot with no activity in the last 14 days: `notes_last_updated` older than 14 days, or empty on deals created more than 14 days ago. Leave out closed stages and deals with a future `notes_next_activity_date`. For each, show deal name, owner, amount, stage, days since last activity, and the last logged touch (call, email, meeting or note) with its date. Sort by amount. Then ask me which ones to follow up. For the ones I pick, create a HubSpot task for the owner, associated with the deal and due the next working day, with a short, specific check-in email draft in the task body.
  3. Put it on a schedule

    Wednesdays at 9:00, from cron on any machine where Claude Code is signed in:

    crontab0 9 * * 3 claude -p "Run the hubspot-stale-deals skill"

    Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.

  4. Send it to your board

    Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a question for you. How setup works

View the SKILL.mdRaw file
SKILL.md---
name: hubspot-stale-deals
description: "Every Wednesday: open HubSpot deals with no logged activity in 14 days or more, and one question on which of them to follow up. Use when the user asks for this, or when it runs on a schedule."
---

# HubSpot stale deals

Every Wednesday: open HubSpot deals with no logged activity in 14 days or more, and one question on which of them to follow up.

Fourteen days without a logged call, email or meeting is usually the point where a deal stops being late and starts being lost. HubSpot will show you those deals if you filter Last Activity Date by hand; most teams find them at the end of the quarter instead.

This skill checks every Wednesday, lists the quiet deals with amount, owner and what last happened, and asks one question: which ones get a follow-up? Answer on the card and the agent creates a task for each owner, with a two-line check-in they can send.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- HubSpot read access to deals, owners and their associated calls, emails, meetings and notes, from a private app token or a HubSpot connector.
- Permission to create tasks, only if you want the agent to log the follow-ups you choose.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Find deals with old activity** (HubSpot): Search `POST /crm/v3/objects/deals/search` with two filter groups, which HubSpot ORs together: `notes_last_updated LT` 14 days ago, and `notes_last_updated NOT_HAS_PROPERTY` with `createdate LT` 14 days ago. Put `dealstage NOT_IN` the closed stages in both groups.
2. **Skip deals that are already handled**: Drop deals whose `notes_next_activity_date` is in the future, since someone already has a task or meeting booked, and deals with a close date more than 90 days out unless you ask for them.
3. **Read the last touch** (HubSpot): For each remaining deal, list its calls, emails, meetings and notes with `GET /crm/v4/objects/deals/{dealId}/associations/{type}` and read the newest by `hs_timestamp`, so the card can say "Call, Sep 15" instead of just a number of days.
4. **Ask who to chase**: Post the list, largest amount first, with days silent, stage, owner and last touch, and ask which deals should get a follow-up.
5. **Create the follow-ups** (HubSpot): Read your choice from Briefkin with `GET /v1/cards/hubspot-stale-deals` (it is in `response`). For each chosen deal, create a task for its owner with `POST /crm/v3/objects/tasks`, associated to the deal and due the next working day, with a short check-in draft in the body.

## Route B: the browser

### What you need

- Signed in to HubSpot with view access to all deals, and permission to create tasks if you want the follow-ups logged.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://app.hubspot.com/contacts/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Filter by last activity**: Pick the account, go to **CRM > Deals** in the list view and open **Advanced filters**. Group one: **Deal stage** is any open stage and **Last activity date** is **more than 14 days ago**. Add an **or** group: Deal stage is any open stage, Last activity date **is unknown**, **Create date** more than 14 days ago.
2. **Skip deals already handled**: In both groups add **Next activity date** is unknown or is before today, so deals with a booked task or meeting drop out. Leave out close dates more than 90 days away unless you want them. Sort by **Amount**, largest first.
3. **Read the last touch**: Open each remaining deal and read the newest entry on its **Activity** tab: the type (call, email, meeting, note) and its date. The **Last activity date** column already gives the days silent if you skip this.
4. **Ask, then create the tasks**: Post the list and ask which deals get a follow-up. For each chosen deal, open it and use **Create task** in the Activity tab: assign it to the deal owner, due the next working day, with a two-line check-in draft in the notes.

Note: Filtering is reliable; opening each deal for its last touch is slow past about 20 deals, so the Last activity date column is the practical substitute for a long list. A task created from the deal record is automatically associated with it.

## The report

- **Quiet deals**: open deals with no activity in 14 days or more, largest first, with owner, stage, days silent and the last touch.
- **The ask**: which of them to follow up.
- After you answer: a task on each chosen deal for its owner, with a check-in draft.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "hubspot-stale-deals/<date of this run, e.g. 2026-10-16>",
  "item_key": "hubspot-stale-deals",
  "project": "Acme",
  "source": "HubSpot stale deals skill",
  "kind": "action",
  "title": "7 open deals with no activity in 14+ days",
  "summary": "**$214,000** of open pipeline has had no logged call, email or meeting for two weeks or more. The quietest, Woodgrove Bank, last heard from us 37 days ago.",
  "action": {
    "request": "Which of these deals should get a follow-up task for their owner?",
    "options": [
      "All 7",
      "The 3 largest",
      "Only 30+ days silent",
      "None this week"
    ]
  },
  "widget": {
    "type": "Table",
    "props": {
      "columns": [
        "Deal",
        "Owner",
        "Amount",
        "Stage",
        "Silent",
        "Last touch"
      ],
      "align": [
        "left",
        "left",
        "right",
        "left",
        "right",
        "left"
      ],
      "rows": [
        [
          "Woodgrove Bank",
          "Theo",
          "$54,000",
          "Presentation scheduled",
          "37 days",
          "Demo, Sep 9"
        ],
        [
          "Relecloud",
          "Marco",
          "$46,000",
          "Decision maker bought-in",
          "21 days",
          "Email, Sep 25"
        ],
        [
          "Alpine Ski House",
          "Lena",
          "$33,000",
          "Qualified to buy",
          "31 days",
          "Call, Sep 15"
        ],
        [
          "Lucerne Publishing",
          "Dana",
          "$28,000",
          "Contract sent",
          "16 days",
          "Note, Sep 30"
        ],
        [
          "Wide World Importers",
          "Sam",
          "$24,000",
          "Appointment scheduled",
          "19 days",
          "Email, Sep 27"
        ],
        [
          "Margie's Travel",
          "Priya",
          "$17,000",
          "Qualified to buy",
          "15 days",
          "Call, Oct 1"
        ],
        [
          "VanArsdel",
          "Dana",
          "$12,000",
          "Presentation scheduled",
          "14 days",
          "Meeting, Oct 2"
        ]
      ]
    }
  }
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Wednesdays at 9:00 (`0 9 * * 3`). From cron, with the agent signed in on that machine:

```bash
0 9 * * 3 claude -p "Run the hubspot-stale-deals skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/hubspot-stale-deals#schedule

Source: https://briefkin.dev/skills/hubspot-stale-deals

What your agent needs

  • HubSpot read access to deals, owners and their associated calls, emails, meetings and notes, from a private app token or a HubSpot connector.

  • Permission to create tasks, only if you want the agent to log the follow-ups you choose.

Connecting HubSpot

  1. HubSpot MCP server, HubSpot's remote server at https://mcp.hubspot.com. HubSpot also offers a Claude connector built on the same server; you sign in with your HubSpot user and it sees what that user can see (docs).
  2. API with a private app token. Create a private app in your HubSpot account settings, give it only the scopes the report reads (crm.objects.deals.read, crm.objects.contacts.read, crm.objects.companies.read, crm.objects.owners.read), and store its token in HUBSPOT_ACCESS_TOKEN.

The MCP server and connector can create and update records, so for unattended reports a private app with only .read scopes is the safer credential.

Questions

Why 14 days?

It is roughly where a slow deal turns into a drifting one for a typical mid-market cycle. Change it in the first step: teams with long enterprise cycles often use 21 days, transactional teams 7.

A deal has a meeting booked next week. Why is it not on the list?

Deals with a future notes_next_activity_date are skipped on purpose. Someone already has a task or meeting on the calendar, so a follow-up would only be noise.

Do I need Briefkin to use the HubSpot stale deals skill?

No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a asks you, so you can glance at it instead of asking again.

Which agents can run it?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.

Can it work without an API or MCP server, from my browser?

Yes. Switch the data source to "Your browser" and the steps change to the HubSpot pages themselves: the agent opens app.hubspot.com/contacts in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.

Answer your agents from one board, or from Telegram

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Free during the open beta. No card.