HubSpot Pipelines API V1 Sunset: What Breaks in n8n and Make on December 4
HubSpot shuts down the Pipelines API V1 on December 4, 2026, and the endpoints stop responding after that. In the n8n node, the source code ties three editor dropdowns to it, but not the saved values in running workflows. If you also move write calls to version 2026-09 along the way, HubSpot starts checking your portal's required-field rules as well.
The Pipelines API reads and manages deal and ticket pipelines, including their stages. HubSpot announced the end of V1 on August 14 and corrected the new rules for write calls on October 27. So far, hardly anyone has looked at either change from the Make and n8n side.
What exactly happens on December 4?
The V1 endpoints stop answering. HubSpot's wording: "V1 endpoints will stop responding after this date." That sets this deadline apart from September 2027, when paths with /v1/ through /v3/ lose support. We broke down the rest of the timeline in our article on Private Apps.
HubSpot's notice names no specific paths. Our take: /crm-pipelines/v1/ is included, since the version sits right in the path. As the target, the notice first says 2026-03 or newer, then recommends 2026-09. Going to 2026-09 satisfies both.
What breaks in the n8n node?
According to the source code, the editor breaks, not the saved values. We read this from the code. It can only be tested once the shutdown has happened. The HubSpot node calls /crm-pipelines/v1/ in three places, including in the n8n 3.0.0 code. All three populate dropdowns: Deal Stage, Ticket Pipeline, and Ticket Stage.
- Existing workflows: At runtime, the node reads the saved value from the field. The three dropdowns aren't loaded for that.
- New or edited nodes: The dropdowns will likely stay empty or show an error. Deal Stage when creating a deal, and Pipeline and Stage when creating a ticket, are required fields. The workaround: switch the field to Expression and enter the ID.
- Older nodes: Node version 1 contains the same three calls.
An n8n update could still fix this. As of November 3, we found no issue or pull request on it at n8n. A side finding: the Deal Stage dropdown only reads results[0], so today it already shows only the stages of the first pipeline.
And in Make?
For the prebuilt modules, you can't tell from the outside. The HubSpot app documentation lists the module "List Deal/Ticket Pipelines" and names no API versions. You can only clearly place what you wrote yourself.
| Connection | On December 4 | Your next step |
|---|---|---|
| n8n: HubSpot node | Editor dropdowns affected unless an update arrives | Note the IDs, watch for n8n updates |
| n8n: HTTP Request with /crm-pipelines/v1/ | Call fails | Change the path, check field names |
| Make: "Make an API Call" or HTTP with /crm-pipelines/v1/ | Call fails | Change the path, check field names |
| Make: "List Deal/Ticket Pipelines" | Unknown | Ask Make support if a process depends on it |
| Your own code | Call fails | Change the path, check field names |
Is swapping the path enough?
No, check the field names too. /crm-pipelines/v1/pipelines/deals becomes /crm/pipelines/2026-09/{objectType}, and the docs show type ID 0-3 for deals. The docs name id as the identifier for pipelines and stages, while the n8n code still reads stageId and pipelineId from V1. If you process those fields further, look at a real response. In addition, 2026-09 checks by default whether pipelines and stages are still in use on DELETE, and whether pipelines are still in use on PUT and PATCH. If you do that through the API, plan for it.
Why can required-field errors appear after the switch?
Because starting with version 2026-09, HubSpot enforces your portal's rules on API write calls too. Reading pipelines isn't affected. But if you move your deal calls in the same pass, you get the validation along with it.
| Rule in your portal | Error from 2026-09 |
|---|---|
| A field becomes required based on a value, such as close date at stage "Closed Won" | 400, MISSING_CONDITIONAL_REQUIRED_PROPERTY |
| Required field on creation (Create Record) | 400, MISSING_REQUIRED_PROPERTY |
| User OAuth without the "Edit Associations" permission | "Missing 'Edit Associations' permission." |
Without such rules in your portal, HubSpot says nothing changes. Portal-level tokens aren't affected by the third item. After the October 27 correction, required associations still apply only in the HubSpot interface. The notice says nothing explicit about older paths and ties the check to the version. The n8n node, for example, still creates deals through /deals/v1/deal, which puts it on the September 2027 timeline.
What does this mean for you?
You have about a month. Here is the order we would follow:
- Search: Export your n8n workflows and Make blueprints as JSON and search them for
crm-pipelines. - Ask HubSpot: Under Development, Migrations, APIs, your account shows usage of old APIs. The docs don't say whether calls from third-party apps like Make appear there, so this doesn't replace the search in step 1.
- Save the IDs: Call /crm/pipelines/2026-09/{objectType} once for deals and tickets and store the IDs. That also helps with the Expression workaround in n8n.
- Check the rules: Conditional required fields under Properties, Create Record per object, permissions of the installing user.
- Test: HubSpot recommends a test account. If you have such a rule, use the new path there to set a deal with no close date to "Closed Won".
- Handle errors: HubSpot says to correct the request, not to repeat it unchanged.
Our take: Move the pipeline calls now, because that's where the hard deadline sits. Treat the write paths as a separate step with their own test. Otherwise, when an error shows up, you won't know which change caused it.
The bigger issue is organizational. With 2026-09, a new required field in your HubSpot settings can stop an automation that used to write past it. Anyone changing rules in the portal should know which processes write there. A list with process, object, and required fields is enough. If you want help with your existing setup: this is our daily work as an n8n and Make agency, and we ran the numbers on choosing a tool here.
Frequently asked questions
Will I lose my pipelines or deals in HubSpot on December 4?
The announcement only covers the API's V1 endpoints. It says nothing about changes to the pipelines themselves or to deals.
Does December 4 apply to other old HubSpot paths too?
No, only to the Pipelines API V1. According to HubSpot, paths with /v4/ lose support on March 30, 2027, and /v1/ through /v3/ in September 2027.
How long will version 2026-09 last?
HubSpot supports each date-based version for at least 18 months and releases a new one twice a year, in March and September. So plan for the path as recurring maintenance.
Does 2026-09 change anything for date fields?
Yes. The API accepts date values more tolerantly, normalizes them, and reports that in a new `warnings` field. Error messages contain more detail, so adjust anything that parses a fixed error format.
Sources
Tell us what you're planning. You'll get an honest assessment within 24 hours.
More articles