--- name: hubspot-deals-closing-this-month description: "Mondays and Thursdays: the deals with a close date this month, their amount and stage, and how long since anyone touched them. Use when the user asks for this, or when it runs on a schedule." --- # HubSpot deals closing this month Mondays and Thursdays: the deals with a close date this month, their amount and stage, and how long since anyone touched them. Which deals are supposed to close before the end of the month, and has anyone talked to them lately? Most month-end forecast calls come down to that question, and HubSpot answers it only if someone builds the right filtered view and remembers to open it. On Mondays and Thursdays the agent builds that view for you. Each deal comes with its amount, stage and the date of the last logged call, email or meeting, so a $48,000 renewal that nobody has touched in two weeks stands out next to the deals already in Contract sent. ## 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 - Read access to HubSpot deals and owners, through a private app token (`HUBSPOT_ACCESS_TOKEN`) or a HubSpot connector your agent already has. - The account time zone, so the month starts and ends where HubSpot thinks it does. If something is missing, say what and stop; do not invent numbers. ### Steps 1. **Search deals closing this month** (HubSpot): Call `POST /crm/v3/objects/deals/search` with a `closedate` `BETWEEN` filter (`value` the first day of the month, `highValue` the last, in epoch milliseconds for the account's time zone) and `dealstage NOT_IN` the closed stages from `GET /crm/v3/pipelines/deals`. Request `dealname`, `amount`, `dealstage`, `closedate`, `hubspot_owner_id`, `notes_last_updated` and `notes_next_activity_date`. 2. **Add what already closed** (HubSpot): Run the same date range against the closed won stage, so the card can show won so far this month next to what is still open. 3. **Mark the risky ones**: A deal is at risk when `notes_last_updated` is more than 10 days old, when `notes_next_activity_date` is empty, or when its close date has already passed and it is still open. Sort at-risk deals first, then the rest by `amount`. 4. **Write the card**: Won so far and still open (count and amount), then one row per open deal: name, owner, amount, stage, close date and days since last activity. ## Route B: the browser ### What you need - Signed in to HubSpot with permission to view every deal in the pipeline, not just owned deals. - The account time zone (Settings > Account Defaults) decides when This month starts and ends. 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 deals by close date**: Pick the account if you have several, go to **CRM > Deals**, switch to the list view and choose the pipeline. Add the filters **Close date** is **This month** and **Deal stage** is any of the open stages, leaving Closed won and Closed lost unticked. 2. **Show the activity columns**: With **Edit columns**, show Deal name, Deal owner, Amount, Deal stage, Close date, **Last activity date** and **Next activity date**. Sort by Last activity date, oldest first, so the quiet deals come to the top; the record count above the table is the open count. 3. **Read what already closed**: Change the Deal stage filter to **Closed won** only, keep Close date is This month, and read the count and the amount total for won so far. The board view shows the same total in the Closed won column header. 4. **Mark the risky ones**: A deal is at risk when Last activity date is more than 10 days ago, Next activity date is empty, or Close date is already behind today. Keep those first, then the rest by amount, with days since last activity for each. Note: The list view shows up to 100 rows per page; with more deals closing this month, export the filtered view from the table actions menu and read the CSV. Last activity date counts only activities associated with the deal, the same property the API route reads. ## The report - **Won so far this month** and **still open**, as count and amount. - **At risk**: open deals with no activity in 10 days, no next activity booked, or a close date already behind them. - **Every open deal** closing this month: owner, amount, stage, close date and days since last activity. - One line on the deal most likely to slip into next month. ## 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-deals-closing-this-month/", "item_key": "hubspot-deals-closing-this-month", "project": "Acme", "source": "HubSpot deals closing this month skill", "kind": "update", "title": "9 deals worth $312k due to close in October", "summary": "$146k already won this month. **9** open deals worth **$312,000** have an October close date, and **3** have had no activity in over 10 days.", "widget": [ { "type": "Grid", "props": { "columns": 3 }, "children": [ { "type": "Stat", "props": { "label": "Won this month", "value": "$146k", "tone": "ok" } }, { "type": "Stat", "props": { "label": "Still open", "value": "$312k" } }, { "type": "Stat", "props": { "label": "At risk", "value": 3, "tone": "warn" } } ] }, { "type": "Table", "props": { "columns": [ "Deal", "Owner", "Amount", "Stage", "Close", "Last activity" ], "align": [ "left", "left", "right", "left", "left", "right" ], "rows": [ [ "Litware renewal", "Dana", "$48,000", "Decision maker bought-in", "Oct 31", "13 days ago" ], [ "Fabrikam pilot", "Priya", "$41,000", "Qualified to buy", "Oct 28", "18 days ago" ], [ "Coho Winery", "Dana", "$24,000", "Presentation scheduled", "Oct 31", "11 days ago" ], [ "Contoso data platform", "Marco", "$62,000", "Contract sent", "Oct 24", "2 days ago" ], [ "Tailspin annual plan", "Sam", "$38,000", "Contract sent", "Oct 20", "today" ], [ "Wingtip expansion", "Lena", "$35,000", "Presentation scheduled", "Oct 30", "4 days ago" ], [ "Adatum seats", "Theo", "$29,000", "Decision maker bought-in", "Oct 22", "1 day ago" ], [ "Fourth Coffee", "Sam", "$19,000", "Contract sent", "Oct 17", "3 days ago" ], [ "Trey Research", "Priya", "$16,000", "Qualified to buy", "Oct 29", "6 days ago" ] ] } } ] } 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: Mondays and Thursdays at 8:30 (`30 8 * * 1,4`). From cron, with the agent signed in on that machine: ```bash 30 8 * * 1,4 claude -p "Run the hubspot-deals-closing-this-month 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-deals-closing-this-month#schedule Source: https://briefkin.dev/skills/hubspot-deals-closing-this-month