In Sprinthub, you can work with several tokens related to date and time. By default, date values are stored in the format ISO, always in the UTC — for example: 2024-10-11T16:12:47.750Z. However, it is possible to format these dates or even generate relative dates, as we will see throughout this article.
Additionally, the platform allows creating custom fields of Date and Time or just Date, offering flexibility to adapt to your process needs, as shown in the example below:
'Trial Class' field in the field listing.
'Trial Class' field in the lead's full data.
Formatting Lead Fields
To format a field of the type Date and Time, you can use different token options:
[date] → displays only day, month and year in the Brazilian format.
[datetime] → works like [date], but also includes the time.
[yyyy-mm-dd] → keeps the international standard (ISO 8601).
The value inside brackets must be placed before the token alias at the time of substitution.
For example:
Below is a practical example showing how this token is replaced in each of the formats:
Tokens used in a SAC360 service interaction.
Date Functions
In some cases, it can be useful to generate relative dates in real time, for example, get the current date at the moment an automation runs, calculate the next day or even one week ahead.
This is done through tokensfunction.
To the right of the equal sign is the time reference (e.g.: yesterday, tomorrow).
The formatting (optional) can be placed in the middle of the token.
Common examples:
One year ago → {function=lastYear}
Last month → {function=lastMonth}
Yesterday → {function=yesterday}
Last week → {function=lastWeek}
Today → {function=today}
Also works for nextYear, nextMonth, tomorrow, etc.
Example with formatting, executed on 09/27/2025:
These tokens can be used in different places in Sprinthub, such as in service interactions, message-sending automations or even in Webhook integrations with external platforms.
