Skip to main content

How To: Use Title Tokens in Templates

Build template titles that fill in the month, year or frequency automatically when each task is created.

Written by AI Support

Title tokens let a template generate task titles that fill themselves in. Put a token in the template's title and it is replaced with a real value each time a task is created from it.

For example, a template titled Payroll - [StartMonth] that generates a task starting 1 April produces a task called Payroll - April.

Start typing [ in the title field of a template or task and a dropdown appears listing every available token, so you do not need to memorise them.


Available tokens

Examples below assume a start date of 8 July 2024 and a due date of 28 August 2024.

Start date tokens

Token

Example

[StartYear]

2024

[Startyyyy]

2024

[Startyy]

24

[StartMonth]

July

[Startmm]

07

[Startww]

28

[StartDay]

Monday

[Startdd]

08

Due date tokens

Token

Example

[DueYear]

2024

[Dueyyyy]

2024

[Dueyy]

24

[DueMonth]

August

[Duemm]

08

[Dueww]

35

[DueDay]

Wednesday

[Duedd]

28

Frequency token

Token

Example

[ScheduleFrequency]

Monthly


Shifting a token forwards or backwards

You can move the value a token produces by adding or subtracting time. Put the number and a period type straight after the token name, using d, w, m or y for day, week, month or year.

With a start date of 14 July 2023:

  • [StartYear+1y] gives 2024

  • [StartMonth+2m] gives September

  • [StartDay+1d] gives Saturday

You can combine shifted tokens to build a whole date. With a start date of 30 September 2023, the title BAS preparation for [Startdd+5d] [StartMonth+5d], [Startyy+5d] produces BAS preparation for 05 October, 23.


Syntax

  • Spaces are ignored. [StartYear +2y], [DueMonth-3m] and [DueDay + 3d] all work.

  • Case does not matter. [STARTYEAR], [StArTdAy] and [dueyear] are all valid.


If there is no due date

If a template has no due date, XBert uses the start date instead, so due date tokens still resolve rather than being left blank.


Timezones

Dates are calculated using your Connect portal's timezone. If your portal is set to AEST (UTC+10) and a start date is stored as UTC+0, the date is adjusted to UTC+10 before the token is replaced.

So a template titled Project - [StartMonth] to [DueMonth] on an AEST portal, with a start date of 1 April and a due date of 1 June, becomes Project - April to June.


Changing a date after the task exists

Editing a task's start date does not automatically update a token in its title. There is a separate Update Title action for that.


Need help?

If you have any questions, our support team is here to help!

Reach out via the chat widget on the bottom left of your XBert screen (Help), or email us at support@xbert.io

Did this answer your question?