Parul confirms that this is possible. The recommended approach is to use the HubDB API. This would likely involve triggering code (e.g., via a webhook listener for form submissions or a custom code action in a workflow triggered by the submission) that calls the HubDB API to add a new row with the form data.
Twentyninetimes identifies marketplace themes as the issue and advises contacting the theme author
Dean links to the CRM Custom Objects API documentation, implying pagination is required as no single endpoint bypasses limits.
SJ shares exciting news about having microphones available for the meetup at the community center.
Camille suggests using the Import API with old deal IDs, which successfully updates merged records
Twentyninetimes explained that for external CDN links, one should use the function calls `{{ require_css('CDN_URL') }}` and `{{ require_js('CDN_URL', 'footer') }}` OR place the standard `<link>` and `<script>` tags inside `{% require_head %}` / `{% require_footer %}` blocks, rather than using the block syntax `{% require_css %}` / `{% require_js %}`.
Denis recommends DepositFix, a tool supporting Authorize.net for subscriptions and one-time payments
Sarah explains contacts auto-associate by domain or using Record ID mapping, with additional methods from Thomas and Michael
Miteshkumar and Saad provide steps to create a child theme via HubSpot's documentation
No single summary document is identified. Alex started deciphering the official SDK documentation generated on GitHub (github.hubspot.com/hubspot-api-nodejs/). This generated documentation, combined with examples, is the primary resource.
Anton advises adding an 'operator': 'EQUAL' to the visibility rules in fields.json.
Yiz identifies missing 'from' ID in batch association payload and directs to use the correct API structure for single vs. bulk associations.
No direct answer provided in the thread. Generally, HubSpot webhook subscriptions expect the receiving endpoint to return a 2xx HTTP status code (e.g., 200 OK or 204 No Content) quickly to acknowledge receipt. HubSpot typically does not process or expect a specific response body.
Yiz clarifies that searchableProperties is for HubSpot UI search functionality, not API access. All properties are accessible via API if included in the schema.
Anton clarified that cloning Marketplace modules is generally not allowed by HubSpot due to licensing and ownership policies. Customizations usually require building a new module or working within the options provided by the original module.
Justin clarifies that Note webhooks aren't configured in the standard workflow triggers but through Public or Private App webhook subscriptions. Justin also implies that the 'Expanded Objects' beta feature might need to be enabled in the app settings to access Note webhooks.
Michael suggests using the Engagements API to retrieve notes periodically instead of relying on webhooks, as notes aren't supported in webhook subscriptions.
The error is resolved by nesting the updated data under a 'values' key in the payload, correcting the JSON structure.
Gunnar Normand suggests using template blocks and global partials to dynamically include different header files based on the template
Anton advises against embedding videos due to compatibility issues with email clients and recommends using a play button overlay on a thumbnail that links to the video instead.