Currently it’s a cumbersome design if I want to create a task for a specific custom property that is a Hubspot User property. For example, our client has 20+ project engineers that get assigned to a Deal by the Director of Enginering when he decides how to assign the new quote request. Currently, this requires us to create two separate workflows, due to the limitation in the total number of branches that a workflow can have, and it all has to be managed manually because Hubspot only allows a workflow action of “Create Task” to be assigned to these 3 options:
1. Specific User
2. Exisiting Deal Owner
3. No one
We really should be able to have another option for this, and allow us to create the task and assign it to our “Project Engineer” property, which in this case is NOT the Deal Owner, but is still an involved party on the deal, and that custom property is a Hubspot User property, so we should be able to use that custom property to assign the task to that Hubspot user, even though they aren’t technically the Deal Owner. Using the Specfic User method (which is what we currently are forced to do) makes for a very cumbersome management of the workflow, as every time a person leaves the company it has to be manually updated.
Instead this could be a very imapctful workflow, and also extemely simple to build and (more importantly) manage on an ongoing basis. It would be nothing more than a enrollment criteria and one create task action, assigning the task to the “Project Engineer”.
That way, when users come and go, this workflow doesn’t need to be updated manualy, because it’s keying on the Hubspot User property.