Preparing your Word templates

Introduction

Tags in the template should match the name of the respective column in the /monday.com board e.g. a column named “Request Date” should be described with a tag of {Request Date} in the Word template. Column names are case sensitive.
The Item name column is unique in that it can be labelled with different names (e.g. Item, Project, Contact, etc) in monday.com, but it should always be reference as {Item.Name} in the Word template.
Subitems can be added as lists or table rows see the example templates in the Document template gallery for further details of how to achieve this, but basically they can be listed using:
CODE
```
{#Subitems}{Item.Name} {Column Name}{/Subitems} 
```
Numeric columns in Subitems are conveniently totalled up for use in table footers
- If the Subitems contain a numeric column named “Price”, add {SubitemsTotals.Price} as the total at the bottom of the table.
All tag names are case-sensitive, so ensure that they exactly match the column names

Columns

Columns are available by matching the name of the respective column in the /monday.com board e.g. a column named “Request Date” should be described with a tag of {Request Date} in the Word template. Column names are case sensitive.

Some column types (such as Date, People and Link), have more functionality that allows you to format the data in additional ways:

Date columns

For a column of type Date, named Request Date, the following tags are available:

{Request Date} – the date as displayed in the column
{Request Date.UTC} the date/time at Coordinated Universal Time (UTC)
{Request Date.language} the language of the automation user
{Request Date.time_zone_identifier} the time zone of the automation user
{Request Date.local} – the date/time of the column in the local timezone for the automation user
{Request Date.local_format} – the date/time of the column in the local timezone and format for the current user e.g. 11 September 2024 or September 9, 2024 at 08:00 or similar dependent on the automation user’s language & timezone settings
{Request Date.time_zone_identifier} the time zone of the current user
{Request Date.ISO} e.g. 2024-09-11 or ISO 8601 date format
{Request Date.DMY} e.g. 11/09/2024 or international format
{Request Date.MDY} e.g. 09/11/2024 or American format

People columns

For a column of type People, named Owner, the following tags are available (where each is a comma separated list of values, when there are multiple people displayed in the column):

{Owner} – normally displays the name(s) of the people in the column
{Owner.IDs}
{Owner.Names}
{Owner.Emails}
{Owner.PhoneNumbers}

Link columns

For a column of type Link, named Website, the following tags are available:

{Website} – normally displays the text and the URL
{Website.URL}
{Website.text}

Formula columns

Not supported.

Currently, formula columns are not supported, but this will change with the full release of API v2025-01.

Items

Item specific data can be access using:

{Item.ID}
{Item.Name}
{Item.URL}

Subitems

Subitems can be added as lists or table rows see the example templates below for further details of how to achieve this, but basically they can be listed using:

CODE

{#Subitems}{Item.Name} {Column Name}{/Subitems}

Numeric columns in Subitems are conveniently totalled up for use in table footers

If the Subitems contain a numeric column named “Price”, add {SubitemsTotals.Price} as the total at the bottom of the table.

Boards

Board specific items can be accessed using:

{Board.ID}
{Board.Name}
{Board.URL}

Users

User specific data can be access using:

{monday.User.ID}
{monday.User.Name}
{monday.User.Email}
{monday.User.Phone}
{monday.User.ProfileURL}

Accounts

Account specific data can be access using:

{monday.Account.ID}
{monday.Account.Name} e.g. Your Team Name
{monday.Account.Slug} e.g. your-team-name
{monday.Account.URL} e.g. https://your-team-name.monday.com

Dates

Today’s date in various formats:

{Date.Today.ISO} e.g. 2025-01-31 or ISO 8601 date format
{Date.Today.DMY} e.g. 31/01/2025 or international format
{Date.Today.MDY} e.g. 01/31/2025 or American format
{Date.Today.local_format} e.g. January 01, 2025 or similar dependent on the automation user’s language & timezone settings