Add Time to Date
Last updated 3 weeks ago
The Add Time to Date workflow action calculates a new date by adding or subtracting time from an existing date property on a record. Use it to automate renewal dates, follow-up schedules, SLA deadlines, and any other date-based logic.
How It Works
Add the Add Time to Date action to any contact, company, deal, or ticket workflow in HubSpot. When a record reaches this step, the app reads the date you specified, applies the time adjustment, and returns the calculated date for use in later workflow steps.
Action Inputs
When you add the action to a workflow, you will configure the following fields:
| Field | Required | Description |
|---|---|---|
| Input Date | Yes | The starting date (from a date property or static value) |
| Years to Add | No | Number of years to add (use negative numbers to subtract) |
| Months to Add | No | Number of months to add (use negative numbers to subtract) |
| Weeks to Add | No | Number of weeks to add (use negative numbers to subtract) |
| Days to Add | No | Number of days to add (use negative numbers to subtract) |
You can combine multiple time units in a single action. For example, setting Years to 1 and Days to 30 will add one year and thirty days to the input date.
Action Outputs
After the action runs, the following output values are available for use in subsequent workflow steps:
| Output | Type | Description |
|---|---|---|
| Result Date (ISO) | Date | The calculated date in standard ISO format, ready to copy into another date property or use in subsequent actions |
| Result Timestamp | Number | The calculated date as a numeric timestamp, useful when you need to pass the value to other systems |
| Success | Yes/No | Whether the calculation completed without errors. Use this to branch your workflow and handle failures gracefully. |
| Error Message | Text | If the calculation failed, this describes what went wrong |
Tip: To learn how to use these output values in later workflow actions (e.g., copy to a property, use in branching logic), see Using workflow action outputs in the HubSpot Knowledge Base.
Branching on Results
A common pattern is to add a branch immediately after the Add Time to Date action:
- If Success is true - proceed with copying the result date to a property, sending a notification, or continuing your workflow
- If Success is false - send an internal alert, skip the step, or route the record for manual review
Usage Examples
Calculate a Contract Renewal Date
Add 1 year to a contract start date to determine when renewal is due.
- Input Date: Contract Start Date property
- Years to Add: 1
The result date will be exactly one year after the contract started.
Set a Net-30 Payment Due Date
Add 30 days to an invoice date to calculate the payment deadline.
- Input Date: Invoice Date property
- Days to Add: 30
Schedule a Follow-Up Two Weeks Out
Add 2 weeks to the date of last contact to trigger a follow-up task.
- Input Date: Last Contacted property
- Weeks to Add: 2
Calculate a Date in the Past
Subtract 90 days from an event date to determine when to start a promotional campaign.
- Input Date: Event Date property
- Days to Add: -90
Combine Multiple Time Units
Add 1 year and 6 months to a subscription start date to find the mid-point of a multi-year plan.
- Input Date: Subscription Start Date property
- Years to Add: 1
- Months to Add: 6
Tips
- Use negative numbers to subtract. Entering -7 in the Days field moves the date one week into the past.
- Leave unused fields blank. You do not need to enter 0 for every time unit -- just fill in the ones you need.
- Copy the result to a property. After the Add Time to Date action, use a HubSpot "Copy property value" action to save the result date into a date property on the record.
- Month-end dates are handled automatically. Adding 1 month to January 31 will give you February 28 (or 29 in a leap year), not an invalid date.
- The action works with any date property. Close dates, create dates, custom date properties -- anything HubSpot stores as a date can be used as input.
Thank you for your feedback!
Your input helps us improve our documentation.