No direct answer in the thread. However, once the custom action is defined and the app is installed in the HubSpot portal, the custom action should become available for selection within the workflow editor UI, usually under a section named 'Custom Actions' or grouped by the connected app's name.
Jennifer Nixon states conditional logic requires Marketing Pro and recommends custom coding or hiring a developer for a multi-step form solution.
One way to achieve this without reloading is to consider using client-side state management or querying a public API that can accept parameters.
Ben was given hints to look for the correct API endpoints to pull the email template while retaining necessary details.
Danielle Urban explains the scripts are standard for analytics, form tracking, and event visualization, with details on each script's function.
Camille Markentive suggests using conditional redirects in form options, which requires Marketing Pro. If unavailable, custom coding or upgrading the plan is necessary.
John clarifies that `get_asset_url()` is designed to work with files uploaded to the Design Manager, not the File Manager (hubfs).
Camille questions the premise, stating that sending marketing emails (including to lists via workflows) is typically included in Marketing Hub Professional. She advises Parul to double-check her Hub subscription features.
The issue is that the initial Lambda function is likely completing the callback immediately. For a blocking action to wait for an asynchronous process, the initial function (Lambda) should receive the request and the callback ID, start the worker, and respond quickly (e.g., 200 OK) *without* calling the HubSpot callback completion endpoint. The asynchronous worker, upon finishing its task (updating contact fields), should be responsible for making the final API call to `POST /automation/v4/actions/callbacks/{callbackId}/complete` to unblock the workflow.
Carter details the features of Journey Automation, describing it as an end-to-end marketing automation tool.
Jon McLaren acknowledged feedback about filtering challenges and mentioned upcoming changelog improvements
Direct client-side fetch calls to external APIs are not permitted from HubSpot UI extensions. Such calls must be routed through a HubSpot serverless function, which can then make the external API request.
Olia explains that the footer's appearance is controlled by CSS. Israe should edit the `child.css` file within their theme (accessible via Design Manager -> Theme Folder -> css/child.css on the left pane) and add or modify the CSS rules for the footer element, likely overriding the `background` or potentially `padding`/`height` properties for the relevant footer class.
Anton Bujanowski recommends adding a cssClass to the form configuration and styling via theme-overrides.css, linking to form embed documentation
The issue may be related to the caching of GraphQL queries. It is suggested to try adjusting the query or possibly purging cache before testing.
Anton explains how to use contact properties in emails for dynamic links and provides code snippets.
Justin Givens explains that custom code outputs cannot be directly inserted into email templates 'on the fly'. The correct method is to add a 'Set property value' action after the custom code action. Use this action to copy the 'reviewLink' output from the custom code into a custom contact property. Then, use the personalization token for that contact property within the email template.
Jennifer advises inspecting the CSS and overriding error styles via theme customizations
Stacey explains the need for a private app token and correct authorization headers, linking to Private Apps documentation.
Stacey suggests, since loops are not possible, to handle this within a single workflow by using delays and conditional branches. After the initial trigger/action, check if the 3 properties are known. If yes, proceed down the desired path. If no, add a delay (e.g., 15 minutes, based on the expected ~10 min update time), and then add another conditional branch to check the properties again. This re-check could be repeated once or twice, potentially creating a task if still not updated.