# Update Date Properties Dynamically Through Workflow

**URL:** <https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696>\
**Category:** HubSpot Ideas\
**Tags:** workflows\
**Created:** [June 7, 2019, 1:54am UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696 "2019-06-07T01:54:54Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![RBlonk](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@RBlonk](https://community.hubspot.com/u/RBlonk)\
**Post date:** [November 21, 2022, 10:12am UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/21 "2022-11-21T10:12:08Z")

</div>

Why does this require another upgrade, seems like a basic feature…

---

<div class="post-metadata">

**Author:** ![NPW](https://avatars.discourse-cdn.com/v4/letter/n/bcef8e/32.png) [@NPW](https://community.hubspot.com/u/NPW)\
**Post date:** [February 1, 2023, 9:20pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/22 "2023-02-01T21:20:32Z")

</div>

Hello All,

If anyone is still searching for a workflow action to set a future date and/or specific date X days from Y, please upvote the following thread: [https://community.hubspot.com/t5/HubSpot-Ideas/More-workflow-options-for-date-properties/idc-p/750300#M134361](https://community.hubspot.com/t5/HubSpot-Ideas/More-workflow-options-for-date-properties/idc-p/750300#M134361)

Thank you!

---

<div class="post-metadata">

**Author:** ![vanessahunt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/vanessahunt/32/38885_2.png) [@vanessahunt](https://community.hubspot.com/u/vanessahunt)\
**Post date:** [June 7, 2023, 5:12pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/23 "2023-06-07T17:12:26Z")

</div>

We need to be able to calculate these types of dates without Operations Hub. Other CRMs include this capability as part of their calculated field functionality.

---

<div class="post-metadata">

**Author:** ![ElBr](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@ElBr](https://community.hubspot.com/u/ElBr)\
**Post date:** [November 21, 2023, 12:44pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/24 "2023-11-21T12:44:42Z")

</div>

Currently enrolling everyone in a workflow but using a delay for all customers until 30 days before the end of their lender agreement (using close date in the photo as an example). Perhaps this could work for you as well?

 ![Screenshot 2023-11-21 at 13.46.49.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/3/53f073942a76276e5820a1d86388e1443ce9d48e.png)

---

<div class="post-metadata">

**Author:** ![AAdkins99](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@AAdkins99](https://community.hubspot.com/u/AAdkins99)\
**Post date:** [March 6, 2024, 6:14pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/25 "2024-03-06T18:14:33Z")

</div>

@MeganLegge hey Megan, on a similar note, I’m wondering if it’s possible to use data formating with _conditions._ My use case is:

When a company churns, we have our CSMs fill out a form that includes two date properties 1) Churn Request Date and 2) Churn Effectice Date. Effective Date is defined as the last day the customer has access to our platform, and should always be set as the last day of the next month, as this concludes our final billing cycle. For example, if I request to cancel on March 6th, 2024, the effective date should be set to April 30th, 2024. Our CSMs don’t apply this logic manually 100% of the time, so I’d like to put some guardrails in place to prevent this. It doesn’t seem possible but I wanted to at least ask you for advice. Thanks in advance!

---

<div class="post-metadata">

**Author:** ![MeganLegge](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/meganlegge/32/20466_2.png) [@MeganLegge](https://community.hubspot.com/u/MeganLegge)\
**Post date:** [March 13, 2024, 1:01pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/26 "2024-03-13T13:01:01Z")

</div>

@AAdkins99 That’s a super interesting example, and yes, pretty complex. We don’t have a way to do this today, but we’ve considered adding a concept of local data variables to workflows that could potentially help with cases like this. For example if you had a variable called "last day of the month that you could use in the workflow. I’m not totally sure what else we’d need to bring it to fruition but you sharing your use case is super helpful for me and the team to think about. Thank you!

---

<div class="post-metadata">

**Author:** ![JPs12](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jps12/32/5125_2.png) [@JPs12](https://community.hubspot.com/u/JPs12)\
**Post date:** [May 29, 2024, 1:17pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/27 "2024-05-29T13:17:48Z")

</div>

Hello Everyone!

We had this same issue, Project Start date was supposed to be 30 days after the Close date and end date 121 days after the close date so approximately 3 months of project time (btw _HubSpot product team_, it would be great to have EOMONTH as a function when creating calculated properties; Everyone, if you see this valuable, please [upvote this idea](https://community.hubspot.com/t5/HubSpot-Ideas/End-of-Month-EOMONTH-function-in-Calculated-properties/idi-p/984382) as it further enchances this workarounds potential). This can be done with calculated properties and workflows so for example Sales Pro is sufficient subscription for this. You can follow these steps to dublicate the process or contact me for consultancy if needed until HubSpot adds in a better solution:  
**1)** I created two new calculated properties:  
“Automatic Start Date” and “Automatic End Date” and set those calculative fields to **Close date + 30 \* 86400000** (this is 1 day in milliseconds) and **Close date + 120 \* 86400000**.

Please note that I already have set up properties for Start and End date values. Do this (or whatever dates you need) if you haven’t already.  
**2)** I created Custom property **“Overwrite automatic dates” (Yes/No)** and used a workflow to set either value to all deals. This was done because sometimes projects are longer or shorter so the PMs can change values to be more accurate when necessary. You can skip this step if you don’t need this functionality.

**3)** I created a deal based workflow that is triggered when _Close date is known_ (and _“Overwrite automatic dates” is “No”_) and set re-enrollment on. Then the workflow copies property value from _“Automatic Start Date” to “Start date”_ and _“Automatic End Date” to “End date”_.

This way these static properties are now dynamic and if the user needs to change the values to something else they simply change the _“Overwrite automatic dates” to “Yes”_ and then the values won’t change. If they at some point change that back to “No” it automatically updates the values.  
Hopefully this helps as a workaround for at least some of you.

When now thinking this you could as well have a custom property that determines how many days you want to add or substract from the date you are basing your new date on. If doing this just update the calculative field formula to e.g. **Close date + New Property that has number of days \* 86400000.**

---

<div class="post-metadata">

**Author:** ![HMcDowell](https://avatars.discourse-cdn.com/v4/letter/h/ccd318/32.png) [@HMcDowell](https://community.hubspot.com/u/HMcDowell)\
**Post date:** [January 22, 2025, 3:39pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/28 "2025-01-22T15:39:21Z")

</div>

We would love if a dynamic date value could be applied to the close date property within workflows in order to specify by pipeline which deals should have a close date within X amount of days

---

<div class="post-metadata">

**Author:** ![MStrebor75](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@MStrebor75](https://community.hubspot.com/u/MStrebor75)\
**Post date:** [March 26, 2025, 5:20pm UTC](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696/29 "2025-03-26T17:20:14Z")

</div>

In case anyone is still reading this one, this Format Data feature would be great for Sales Hub. We have Enterprise and I really thought it was an option at this level. Now this becomes a manual operation for someone when it could be done in the workflow, as intended. Something for the product team to think on.

[Previous page](https://community.hubspot.com/t/update-date-properties-dynamically-through-workflow/14696.md?page=1)
