Carter assists by asking if Tristan can see the app under connected apps, seeking to troubleshoot the visibility issue.
Nicholas identifies that the 'type' property is required in the workflow enrollment criteria filters and must be specified.
Nicholas clarifies that reports do not have a direct API; data must be queried from source objects or exported manually via HubSpot's UI.
Manuel found the solution: updating the `@hubspot/ui-extensions` package by running `npm i @hubspot/ui-extensions` resolved the issue.
Outlook flags external senders by default. Internal senders should work with IT to allowlist HubSpot's domain/IPs to bypass security warnings.
Anton suggested using the fromjson filter to potentially assist in formatting the JSON output.
Scott confirms that Axios can be imported using require() and used within the function, providing a code snippet example.
Anton thanks Nicholas for his contributions and inquires about how many questions he addressed.
Nicholas confirms that boolean properties are now stored as enumerations with true/false options, aligning with API behavior observed since September 2024.
Nicholas suggests checking for caching issues and ensuring proper code formatting, but the core solution isn't fully resolved. Manual updates in HubSpot UI temporarily fix visibility.
Nicholas Decker shares a code snippet to convert createDate into a day-of-week number (1-7)
Nicholas Decker states there is no API available for sequence reports as of now.
BJ confirms that the components must be correctly pulled in for proper operation.
Nicholas Decker proposes using an SMS link to trigger the user's subscription response, bypassing direct API updates.
Nicholas explains the limitations of UI Extensions and suggests diving into details of what Daniel is trying to create.
Solution not provided. Likely requires using the correct API endpoint (e.g., CMS or Settings API) with proper payload structure for publicAccessRules.
Nicholas suggests that the issue might stem from the custom object having required properties for creation. Ensure that the form submission includes and correctly maps values to all required fields for the custom object within the form's automation settings.
Carter McKay clarifies that email engagements via API only log activity and suggests using Forms API or Custom Channels for inbox visibility.
Shar Ghavami confirms that dates must be in ISO 8601 format or Unix timestamp and references HubSpot documentation.
Federico Mozzo points out that query parameters must be ordered correctly to match HubSpot's signature generation.