Michal explains that form submissions create contacts asynchronously, suggesting creating the contact directly via API first to avoid delays.
No responses or updates in the thread.
SJ Morris confirms it's a known bug and offers to assist affected users
Michael advises placing 'allowUserInput' inside the 'quickReply' object structure, correcting the payload format.
Nathan confirms the merge API endpoint works and provides a Postman example. The solution involves using the PATCH request to the /crm/v3/objects/{objectType}/merge endpoint.
Robert Ainslie explains automatic image optimization and suggests using resize_image_url() for manual control
Nicholas confirms tracking works despite URL encoding by ESPs.
Anton recommends using custom blog templates or a global snippets file linked in KB settings
HubSpot support clarifies that the 'searchableProperties' in the object schema must be updated, as global search settings don't affect the CRM Search API.
Robert Ainslie provides solutions using the Conversations SDK, mobile SDKs, and tracking code requirements
Nicholas suggests using multiple filter groups for OR logic. Later, Robert recommends using the Batch Associations API to find deals associated with companies, and ultimately GraphQL is confirmed as the solution for filtering deals by stage and nested associations.
While no specific solution is provided in the thread, the timing coincides with a HubSpot issue regarding the callback completion endpoint (see messages from Scott Hemmeter [231277] & Lew Talon [232659]). This HubSpot-side issue caused similar failures and timeouts for custom actions and was resolved by HubSpot reverting a change.
Scott Marion suggests footer placement is better for performance, though Matt argues for header usage with async/defer
Justin Givens and Anand Narasimhan explain that conditional scopes tied to HubSpot tiers (e.g., Enterprise) control app compatibility.
Suggestions would be beneficial in the thread, yet no direct solutions appear to have been offered.
Lew confirms experiencing the same issue. HubSpot later acknowledged (via Lew) that a recent change to validate callback IDs caused the problem. HubSpot reverted this change, resolving the 400 errors.
Zack Wolfson confirms a known issue and shares the HubSpot status page for updates
Anton advises using HubSpot's Content Staging or CMS Developer Sandbox accounts, with GitHub integration as an alternative for deployment
James solves it by initializing a new dict and updating it with defaults before custom values.
Anton recommends using membership pages/portals with HubSpot's CMS memberships feature, though Design Manager permissions may be required