Jun-te Kim bb0142d6f8 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 <noreply@anthropic.com>		2026-07-14 15:49:42 +00:00
..
scripts	add utilities to hubspot etl dockerfile	2026-07-08 16:49:55 +00:00
tests	Merge pull request #1515 from Hestia-Homes/feature/hubspot-planning-fields	2026-07-08 16:14:01 +01:00
__init__.py	add init file	2026-06-04 15:56:50 +00:00
company_data.py	include missing file	2026-04-08 14:48:29 +00:00
hubspot_deal_differ.py	Merge pull request #1519 from Hestia-Homes/feature/abri-api-integration	2026-07-08 17:18:13 +01:00
hubspot_trigger_orchestrator_trigger_request.py	move everything to etl/hubspot/	2026-04-09 09:41:43 +00:00
hubspotClient.py	Request planning/address-profiling properties from HubSpot deal fetch	2026-07-14 15:49:42 +00:00
hubspotDataTodB.py	Add remaining planning/address-profiling fields to HubSpot ETL sync	2026-07-08 15:12:24 +00:00
project_data.py	hubspot projects data is scraped	2026-05-28 10:54:15 +00:00
requirements.txt	removed hashlib as its from the standard library	2026-03-30 14:42:11 +00:00
s3_uploader.py	revmoed keys	2026-03-31 10:42:02 +00:00
utils.py	Abri deal abandonment requires at least three parseable attempts 🟩	2026-07-03 10:10:03 +00:00