Matthieu Berard advises creating a new HubSpot account if permissions or legacy account issues prevent domain publishing.
Michael Shepherd explains Shopify's tax compliance requirements and recommends legal consultation
Rakel resolved the issue herself, mentioning nested fields or hidden controls, but no specific solution was provided in the thread
Scott suggests custom code but Kyle proceeds with Make.com as a no-code solution
Antonio Garcia recommends using the `replace` filter in HubL to modify paragraph tags with inline styles.
Cameron advises using PRE_ACTION_EXECUTION functions to include property data in webhook URLs.
SJ Morris explains the peer-to-peer nature of the community and advises proactive engagement.
Carsten resolves the issue by ensuring field names are in lowercase in API calls.
Jake Kohl confirms that yes, records can be deleted via API using the respective object's DELETE endpoint (e.g., `/crm/v3/objects/contacts/{contactId}`). Since programmable automation (custom code) can make API calls, it can also be used to trigger these delete requests based on defined logic within the workflow.
Cameron suggests using a private app and custom coded workflow actions or third-party tools like Zapier.
Jake Kohl suggests ensuring the workflow trigger uses the correct HubSpot property where the UTM campaign value is stored (e.g., Original source drill-down, a campaign property, or a custom property) as raw URL parameters might be processed differently. The action to assign the contact would likely involve 'Rotate record to owner' or 'Set property value' for an owner property, potentially using IF/THEN branches based on the captured campaign name.
Twentyninetimes suggests using JavaScript to capture UTM values and provides code to inject them into HubSpot properties via the tracking API.
Rob Harris explains HubSpot's built-in cookie banner handles compliance, but notes custom integration is needed for external CMPs.
The issue was resolved without specific changes, indicating a temporary HubSpot service problem.
Michael advised adding delays between API calls to account for indexing latency
Alex Woodbridge confirms that you cannot directly copy a string value (from the webhook token) into a HubSpot property of type 'Phone number' using the standard 'Set Property Value' action. A conversion step is needed, potentially using a 'Format data' action (Ops Hub Pro+) or custom code to handle the type conversion before setting the property.
Matt resolves the issue by using `content_by_id` to fetch the correct image data and provides a code snippet to bypass the default behavior.
Currently, there isn't a built-in method in HubSpot to track module usage like in the Design Manager.
Camille confirms, referencing HubSpot documentation, that webhook-triggered workflows cannot enroll records that don't already exist in HubSpot with a matching unique property. Therefore, this method cannot be used to create new contacts directly. An alternative approach, like having the webhook call an intermediary service that uses the CRM API to create the contact, would be needed.
Documentation in Eric Song's response specifies using Swift Package Manager, indicating CocoaPods is not officially supported.