UI bug in the HubSpot node {typeVersion 2.2}

Feature Requests UI
,
1

Hi n8n team,

Quick UI bug in the HubSpot node (typeVersion 2.2): every Custom Properties row shows an empty dropdown with The value "" is not supported!, even though the workflow JSON has all the bindings intact and the node actually executes correctly at runtime (verified — properties are written to HubSpot successfully).

So it’s purely a read/rehydration issue in the UI — the stored property value isn’t being matched back to the dropdown options.

Also confirmed:

  • Credential is healthy, points to correct portal.
  • Property list loads fine when the dropdown is opened.
  • No properties renamed/deleted in HubSpot.
  • Older workflow versions show the same empty state, so nothing was edited.

Is this a known regression, and is there a workaround so I don’t have to manually re-select properties across multiple workflows? Happy to share the exported JSON.

Thanks!

2

Nice catch, thanks a lot for writing this up so clearly.

From what you describe (values saved correctly in the JSON, node executing fine, only the dropdown showing The value "" is not supported!), this really looks like a pure UI re‑hydration bug in the HubSpot node rather than a config problem on your side.

As a short‑term workaround:

  • If you don’t need to change those fields right now, you can safely leave the node as is since runtime behaviour is correct.
  • If you do need to edit them, you can switch the field to Expression and type the internal property name as plain text instead of picking it from the dropdown – that bypasses the UI matching logic.

I’d definitely recommend sharing your exported workflow JSON with the n8n team (either here or in a GitHub issue) so they can reproduce this for typeVersion 2.2 and fix the re‑hydration in the UI.