Which rETL destination?:

HubSpot

Additional details:
Would love to have the authenticated HubSpot portal ID and account name exposed through the Activations Destinations API’s connection_details, consistent with the account metadata available for other destinations.
We use previously ingested Contact IDs from Fivetran’s traditional HubSpot ETL connector to update existing contacts through Activations. We need the destination’s portal ID to verify that both connections refer to the same HubSpot account before writing by Contact ID. The account name also helps users distinguish connected accounts in our application.
These fields should be available after authorization, without running a sync or creating an enrichment dataset, and reflect any account change after reauthorization.