HubSpot's APIs now ship as dated versions like 2026-09. Pin the version in every workflow and watch for sunset headers

Your HubSpot integration can work for months and then quietly break the week an old API version retires.

What happened

HubSpot's API reference now centers on date-based versions. The 2026-09 APIs use paths like /crm/objects/2026-09/contacts and follow the previous 2026-03 version. HubSpot says that when a new date version ships, the previous one keeps working until its end-of-life date, giving developers time to migrate, and it advises using the latest date version for new integrations.

The same week, n8n published a guide to API versioning for workflow builders. It covers the four common styles (URL path, header, date and query parameter) and what to watch for when a provider retires a version: a deprecation header as the first warning, a sunset header with an exact end date, and finally a 410 Gone response, which it says should not be retried. n8n recommends setting the version explicitly in the HTTP Request node rather than relying on the provider default, alerting on deprecation warnings, and sending 410 responses to a separate error workflow.

My take

Dated versions are good news for CRM builders, because changes now arrive on a schedule you can plan around. They only help if your workflows say which version they expect.

For HubSpot work, I would do four things:

1. Pin the date version in every raw HTTP call. Write it into the URL, not left to whatever default applies later.
2. Check response headers for deprecation and sunset notices and send them to a shared alert channel with the workflow name.
3. Route 410 and unexpected schema errors to an error workflow that stops the run and tells a human, instead of retrying forever or writing half empty records.
4. Keep a short list of which workflows call which version, so a migration is a checklist, not a hunt.

Built-in nodes handle a lot of this for you, but most real CRM automations end up with a few raw API calls for custom objects or associations. Those are the ones that break.

Tell me which HubSpot workflows you rely on most, and I will help you find the raw calls that need a pinned version. Reach me at romielwillautomate.dev.