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