Set timestamp with a workflow

[Jacob02]

Dear HubSpot team, 

I would like to set individual timestamps with a workflow since I need to store the exact time and therfore "date of step" is not enough. 

I already tried to add it via "set property value" and the variable "{{to_local_time(local_dt)}}. But this is currently only stored as a simple string (see attached screenshot).



Your support wrote the following about this request:

"At the moment it is not possible to add HubL variables into workflows. This is why adding {{to_local_time(local_dt)}} into the property action would not work and would not save the timestamp.

I did a little bit of digging around this, however, at the moment it is not possible to save time into a property. This is because at the moment, HubSpot does not support custom Time properties."

I hope you will be able to implement this soon (maybe you can make all general variables usable with workflows).

[finn]

+1

[mcraciun]

+1. This would be really beneficial. Use case:
Creating a "time between" calculated property, to calculate the amount of time between when a ticket was opened and another custom property. Using a workflow we are only able to set the date for this custom property, but since the create date has a timestamp, ideally this custom property that is set by the workflow would too, so we can accurately calculate the "time between" those two properties. 

[erik_camara]

+1. Its a great idea. In our case we use different lifecycle properties then the original one and would like to set a timestamp on the lifecycle changes, so that we could calculate the distance between each conversion.

[Drew_Cohen]

Totally agree about the necessity for time stamps, especially on ticket submissions. For larger CX/service teams, identifying popular ticket submission trends by time of day is critical for determining staffing and schedules in order to enhance the customer experience.

[LaurelCarden]

This is absolutely necessary. If this doesnt get resolved, we'll likely need to find a new provider. Its impossible to track some of the most meaningful sales activities without this functionality. 

[SuaniaC]

Agree, this functionality is key! 

[dk91]

This is super important for us to be able to track things like average first response time to someone requesting a meeting. Worth noting that in addition to being able to set the timestamp via a workflow, we'd need the ability to create 'timedate' properties manually and not only via API as is the case currently. 

[Temirovich]

+1. Its a great idea and super important

[TSantos0]

+1 to this, this will be helpful. Hopefully this will be implemented soon.

[DBroughton]

agreed. this would be extremely useful.

[KMellert]

We would also like to set individual timestamps into a workflow and a custom field property around deals. Example: If the deal was updated by the sync in the last 24 hours, do not take action.