Awesome; thank you for the confirmation on creation.
Would you happen to know about the visibility of the hs_is_marketable_status property or the various Hubspot/Salesforce sync properties, particularly from the Bulk Load operation (e.g. when initially populating the table using the Explorer+ tier integration)?
On Contact that would be:
salesforcedeleted
salesforcecontactid
salesforceaccountid
salesforceleadid
salesforcecampaignids
salesforcelastsynctime
On Account that would be:
salesforcedeleted
salesforceaccountid
salesforcelastsynctime
On Deal that would be:
salesforcedeleted
salesforceopportunityid
salesforcelastsynctime
(Unfortunately I don't have visibility into the salesforce properties of the Lead model).
Here's why this matters: it is of vital importance when using both Salesforce and Hubspot together to know if a Hubspot record is also syncing with a corresponding record in Salesforce.
A shocking number of organizations will use Salesforce for their sales teams and active customer account management, but rely on HubSpot for tracking marketing activities (unfortunately this includes my organization).
Hubspot maintains a record for ALL contacts, but will treat records in Salesforce as sacrosanct by default if it also exists there. More specifically, if a record exists in Salesforce, then there is a populated value for that field. The HubSpot UPDATE APIs will accept the change and then automatically revert back to the state in Salesforce. Clay (and the user) would get no notification that this field reversion happened.
Knowing ahead of time means the builder of the Clay workflow could decide to:
avoid enriching entirely records that exist in Salesforce
only enrich the fields that are blank
Make an update to these records in Salesforce, rather than Hubspot