Change Log

HubSpot relaunched its Starter tier and moved several sales tools into it, including the Prospecting Agent, which researches contacts, watches companies for signals and drafts outreach for review, plus Notetaker for recording and logging meetings, AI Meeting Prep and deal pipeline automation. Prospecting Agent and Data Agent runs draw on HubSpot Credits.

Small teams on Starter get AI prospecting and meeting capture without moving to Professional, with agent use metered through credits rather than included.

HubSpot released the HubSpot Sales Plugin for Claude, a free plugin that installs the HubSpot connector for Claude plus eight packaged sales skills: /daily-brief, /call-prep, /follow-up, /import, /log-call, /pipeline-pulse, /contact-lookup and a catch all /hubspot skill. Reps can prep for calls, log call notes, update deal stages, create follow up tasks, draft follow up emails saved as HubSpot drafts, and import contacts with field mapping and duplicate detection from inside Claude. HubSpot states that before Claude writes anything to the account it shows the proposed change and asks the user to confirm.

Sales teams that already work in Claude can read and write HubSpot pipeline data without switching tools, which widens where CRM updates originate. The stated confirm before write step matters for admins deciding whether to allow an outside AI client to change deal and contact records.

HubSpot's 2026.09 developer release expands the Sequences API to create, read, update and delete sequences and adds an Email Template API, both requiring authorization at the user level. New read only Forecasts and Notetaker Recap APIs expose forecast submissions and history and processed call and meeting summaries for Sales Hub Professional and Enterprise. Object Tags and a Task Series API for repeating tasks are open to Sales Hub Starter and above.

Sequences were the part of Sales Hub an integration could watch but not build. With create and update access, outreach setup can be automated, and forecast and meeting data can flow to outside reporting. Check seat entitlements first, because several of these APIs depend on the tier.

With the /2026-09/ version of the HubSpot Pipelines API, which ships on 8 September, a delete request against a pipeline or pipeline stage that is still in use is blocked by default and returns a validation error, matching what the pipeline settings page in the HubSpot UI already does. Integrations that relied on deleting in use pipelines or stages will receive a 400 after moving to /2026-09/ unless they pass validateReferencesBeforeDelete=false, or validateDealStageUsagesBeforeDelete for deal pipelines, or stay on an earlier version. The change was announced ahead of time on the developer changelog and applies only from /2026-09/ onward; the current version and earlier ones are unchanged.

This is a breaking change and a sensible one: an integration that could silently delete a stage with live deals attached was a data loss path nobody asked for. The action for a sales operations owner is to ask each integration vendor whether it has moved to /2026-09/ and, if it deletes pipeline objects, whether it handles the new 400. The same version also carries HubSpot's earlier announced enforcement of admin configured validation rules on CRM write paths, so September is the month the API starts behaving like the UI.

HubSpot's August 2026 developer rollup introduced updates to CRM workflows, including the ability to preserve active workflow enrollments when primary records are merged. The release also adds app object support to association workflow actions, allowing automations to reference third party app data.

Sales operations teams can now merge duplicate contact or company records without accidentally dropping prospects from active automated outreach or internal routing workflows. The expanded app object support also allows revenue teams to build more sophisticated automations that trigger based on integrated third party data.