Great minds think alike

We represent DevAll, a B2B SaaS team based in Korea, and we're reaching out with a strong desire to integrate HubSpot into our operations. Unfortunately, the lack of Korean language support significantly hinders our ability to do so. This challenge is not unique to us; numerous Korean teams are eager to leverage HubSpot's globally acclaimed user-friendly platform but find themselves at an impasse due to the language barrier. As you may be aware, Korea is renowned for its robust IT industry and represents a substantial market opportunity. Incorporating Korean language support would not only facilitate our utilization of HubSpot but also unlock its potential for countless other teams within this vibrant market. We are keen to understand if there are any initiatives underway to introduce Korean language support in the near future. Enhancing your platform's accessibility with Korean language integration could dramatically increase your footprint in one of the world's leading technology hubs. We look forward to your positive response and any possible roadmap towards this inclusion. Providing support in Korean would be a game-changer for us and many others here. Thank you for considering our request! ...read more

Today when you create a slack channel via workflow you cannot control which types of activities get automatically posted to the slack channel. Only the two default of Notes and Calls are automatically selected for you.  In my company, we need emails to be sent to slack too. This means we cannot fully automate slack channel creation -- there is a manual step for someone to go in and edit the association to check the box for emails. It would be really great if we could edit the list of activities associated with the channel right in the workflow step when we create it. Please add this!  I made a mockup of what this could look like  ...read more

Could be good that, when a contact is enrolled in a Workflow and goes to a send marketing email action and the primary contact email fails, have the possibility to try to send the marketing email to the additional emails that could have the record.   Thanks! ...read more

In an automation, it would be useful to be able to set the owner of a record that is being created (e.g., a Ticket) to the person who enrolled the record in the workflow that is being run.     Example use case: working to create a workflow that will create a copy of a ticket and it's associated tasks (and possibly also a copy of any associated tickets - not sure if I'll succeed).  It would be great if the owner of the ticket that gets created could be set to whichever user enrolled the "template" ticket in the workflow.   p.s. if there's already a way to have template tickets that can be cloned (including tasks and associated tickets), please point me to it.  So far I only found this idea: HubSpot Community - Copying a ticket - HubSpot Community. ...read more

It would be great if we could setup a workflow to create a customer note (so that these items are searchable in hubspot) from different properties in Hubspot. So, if someone from one department writes a note in their section the workflow could automatically create a customer note once that property has been completed. ...read more

Seems we can't use UTM parameters as triggers for a workflow.   I wanted to create a Slack Alert workflow that triggers when someone fills a very common form from a specific social media. Thought adding a UTM parameter for unique tracking would help but that didn't work.   Couldn't really find another workaround for this so if anyone has any ideas then would love to hear them.   If not, then this would probably be a powerful trigger to have for automation AND reporting. ...read more

It would be very helpful to have the ability to create workflows from HubSpot assets. For example, we have a lot of marketing emails and landing pages, it would be great to automatically create and assign a recurring task to the user that created the item to review that the content is still accurate over time (every quarter for example). ...read more

Pt. A Request It would be great if there was an error flag applied to workflows when a properties options that are referenced in branches are updated.   Issue: Currently there is a message on the custom filters that appears is an option has been removed, but can only be if you open the original branch within the workflow itself. It does not appear in the errors to review. If using a "based on single property value" type of branch for multiselect, the error only appears as a red box around the option, and again, only if you open the branch itself.   At first glance, one might assume all is well within the workflow if they weren't already aware of where to look. However, these property option changes can have a major impact on how the branch filters and disrupt operations.   Why? To maintain workflows and make sure they are performing properly.     Pt. B Request Ability to reference this in error history.   Why? To be able to reference when fixes were implemented and what time frame the error was still live to manually review and make adjustments where needed. ...read more

I would like to propose an improvement regarding the error messages displayed in the Workflow History section of HubSpot, particularly in relation to the WhatsApp integration.   Currently, when attempting to subscribe contacts to a WhatsApp subscription workflow based on their WhatsApp phone number alone, an error message is generated stating something like: "Neither an email address nor a phone number is present for the contact" (or in German: "Für den Kontakt ist weder eine E-Mail-Adresse noch eine Telefonnummer vorhanden"). Since a known WhatsApp phone numer is the trigger in this case, this message is misleading and does not facilitate troubleshooting efforts effectively.   Only upon closer examination of the enrollment history and contact details, we discovered a server response error code: "MISSING_SUBSCRIBER_ID" which helped us to realize that we cannot subscribe contacts to the WhatsApp service without prior opt-in messages from them:   Misleading Error Message in HubSpot Workflow History   Consequently, despite having diligently collected consent for WhatsApp conversations via a form, the workflow remains ineffective (the whole problem is stated in this community post, by the way).    To improve user understanding and streamline troubleshooting processes, I suggest revising the error message to provide clear insight into the underlying issue and potential solutions. ...read more