| | Hello there. HubSpot gave developers a dated heads-up today: the CLI stops supporting Node.js 20 in January. There is also a product walkthrough of Agent Hub from UNBOUND, three new Marketplace apps, and a practical thread on what to do with leads that stop replying. In today’s newsletter, we’ll get into: - From January 8, 2027 the HubSpot developer CLI needs Node.js 22 or higher, and GitHub Action users will need the next action version.
- An UNBOUND session shows Agent Hub, HubSpot's new place to manage agents, with Agent Builder and Breeze Assistant bringing them to teams.
- One user's quiet-lead setup: a sequence for the first 4 to 5 touches, a task after 14 days of silence and closed lost after 60 to 90 days.
| |
|
| | 🧰 The HubSpot CLI stops supporting Node.js 20 in January. Node.js 20 reached end of life on April 30, so HubSpot will drop Node.js 20 from its developer CLI on January 8, 2027. From then on the CLI needs Node.js 22 or higher, and older CLI versions on Node.js 20 may break. You can update any time with npm i -g @hubspot/cli@latest, and teams using the HubSpot GitHub Action should move to the new version once it ships. 🤖 A walkthrough of Agent Hub from UNBOUND. In a 21-minute UNBOUND session, Adam Cuzzort from HubSpot product walks through Agent Hub, the new home for managing agents inside HubSpot. He shows how Agent Builder lets you shape agents around the way your business works and how Breeze Assistant brings them to teams where they already work. The pitch is that agents running on your own CRM data do not start cold. | |
|
| | 🧩 Three new apps in the Marketplace. Associated Values by Plugivo turns properties on associated CRM records into reusable workflow outputs, handy when a deal workflow needs a value from its company. IndexPilot by Inbound Design Partners monitors HubSpot content and submits it to IndexNow automatically, and Clicksign adds native electronic signatures so you can send documents and close deals from the CRM. 📝 Users want Notetaker summaries in reports. One admin uses HubSpot Notetaker summaries as a weekly team update on which meetings happened and what came out of them, but there is no tidy way to pull them into a report. Their idea asks HubSpot to make Notetaker summaries and action items reportable. Back the idea if you already copy meeting notes into a dashboard by hand. | |
|
| | 🔔 One broken workflow, 200 notification emails. An admin says a single workflow error, permission change or recurring meeting invite can send users 100 or 200 notifications about the same event, which is hard on new users. Their idea asks HubSpot to bundle notifications that fire close together into one email, like a faster Task Digest, with admin limits or a short pause before sending so mistakes can be caught. 📊 Dashboard right, export wrong after imports? A user updated several properties through imports in the morning and found the report looked correct on screen in the dashboard table, but several of the updated fields came out differently when exported to Excel. If you are finishing a report straight after a big import, compare the export with the dashboard before you send it on. 📮 A forwarding address for each deal is still an idea. A firm whose subcontractors work on up to 10 deals at once wants a unique email forwarding address for every deal, the way Monday.com and BuilderTrend do it. A community moderator pointed to an existing idea for deal-specific BCC addresses and suggested adding votes and the subcontractor use case there, since HubSpot's BCC address today is generic. | |
|
| | 🔁 What to do with leads that go quiet. Asked how teams handle leads that stop replying, one HubSpot user shared a simple setup: a sequence covers the first 4 to 5 follow-ups and stops on reply, a workflow creates an owner task after 14 days with no activity, then contacts move to a nurture list and deals idle for 60 to 90 days are closed lost with a reason. Another reply says a relevant reason to reconnect beats more automated touches. | |
|
| | 🗓️ Find a HubSpot User Group in your area. HubSpot User Groups meet virtually and in person so users can learn best practices from each other. If a Node.js upgrade or an agent rollout is on your list this quarter, a local group is a good place to ask how other teams handled the same work. | |
|
| | Three remote roles posted in the last two weeks, each linked to its own posting with the source named. Each posting is linked from the source named on its line, with the date it was posted. Check the details on the posting itself. | |
|
|
|
