The issue is resolved by using Axios instead of the HubSpot Node.js client library
No direct answer provided as Jeff is unsure about the capabilities of the addAlert function.
Elroy finds a Slack thread with relevant information
Anton Bujanowski suggests modifying the fields.json to reference theme.primary_color instead of brand_settings, though the user reports unresolved issues.
Hannah advises submitting feedback through the developer feedback form to request the 'crm.objects.tickets.read' scope
No detailed solution was offered in the responses.
No solution was provided, only an explanation of the issue.
No answer was provided in the thread for Pietro's specific issue.
David suggests that the solution is likely to find the source of these incorrect links. Roslyn should investigate which pages on her website or external sources are linking to these non-existent '/hubfs/' URLs and correct the links there.
No solution provided directly, just seeking best practices from others.
No direct solution was provided in the messages, but Reilly suggested potential workarounds around card descriptor JSON and title duplicity.
Muhammad confirmed that calling serverless functions from a module.js file should work without issues and asked for details about the specific problem encountered.
There is no specific answer provided in the thread for this question.
There is no specific answer provided in the thread for this question.
Lukas suggests checking the HubSpot documentation on creating calculation properties.
Roger Brown identified a trailing comma in the 'scopes' array within the app.json file. Removing this comma corrected the JSON syntax error, resolving the upload failure.
No detailed solution was provided in the responses, but community feedback indicates these limitations do exist, and it is unclear if there's a workaround.
No specific answers provided in this thread.
No specific answers provided in this thread.
Use HubSpot's native Google Sheets workflow action instead of direct API submissions to avoid CORS.