From bb0142d6f84ad2f816f1632dd77edb8ffd5cc175 Mon Sep 17 00:00:00 2001 From: Jun-te Kim Date: Tue, 14 Jul 2026 15:49:42 +0000 Subject: [PATCH] Request planning/address-profiling properties from HubSpot deal fetch FIELD_MAP and upsert_deal already map planning_authority, designated_area, article_pd_rights, listed_building, design_constraints, planning_comments, planning_status, and planning_suggested_approach, but from_deal_id_get_info never requested them from the HubSpot API. Since HubSpot only returns explicitly requested properties, these always came back None regardless of the deal's actual data, so refreshes never populated them. Co-Authored-By: Claude Sonnet 5 --- etl/hubspot/hubspotClient.py | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/etl/hubspot/hubspotClient.py b/etl/hubspot/hubspotClient.py index 8be93cc29..c886eb1c2 100644 --- a/etl/hubspot/hubspotClient.py +++ b/etl/hubspot/hubspotClient.py @@ -321,6 +321,14 @@ class HubspotClient: "last_outbound_call", "last_outbound_email", "last_submission_date", + "planning_authority", + "designated_area", + "article_pd_rights", + "listed_building", + "design_constraints", + "planning_comments", + "planning_status", + "planning_suggested_approach", ], ) )