Tokens in Microsoft Word or Microsoft PowerPoint Documents

Variable token

{{token_name}}

Shows the value of a variable that is passed into the document template as a JSON element. The displayed value uses the formatting of the first curly brace. For example, if the first curly brace in the token is italicized, the text in the token is italicized as well. New lines within variable tokens in the generated document aren't supported.

Formatting present in content merged via variable tokens will be disregarded upon token replacement during document generation. This includes any formatting such as bold, italics, new lines (\n) and carriage returns (\r). For example, if content containing \n is sourced from a plain text field, the resulting document won't render the token contents on separate lines; instead, they’ll appear on a single-line . To retain formatting in the generated document, use rich text fields in the objects and RTB tokens in the document templates.

See add a text watermark to a document template to add watermarks on your generated document by using variable tokens.

Repeating content token

{{#token_name}}

<Content to repeat>

{{/token_name}}

AND

{{^token_name}}

<Content to display>

{{/token_name}}

Repeats a content section.

A token beginning with the pound sign (#) indicates that the section repeats as many times as the item occurs in the input JSON array.

A token beginning with the caret (^) indicates what is shown if the input JSON array is empty or doesn’t exist. In this case, the section is shown only one time.

The token itself isn’t shown and values don’t use the token text formatting.

Condition evaluation token

{{#IF_token_name}}

<Content to display>

{{/IF_token_name}}

AND

{{^IF_token_name}}

<Content to display>

{{/IF_token_name}}

Checks a Boolean condition to show a section one time or not to display the section at all.

If the value of a token beginning with #IF_ is true, the section appears one time, otherwise it doesn’t appear.

If the value of a token beginning with ^IF_ is true, the section doesn't appear, otherwise the section appears one time.

The token name from your Omnistudio Data Mapper or Apex and the token name in your document template must both contain IF_ as a prefix. An example is for the condition token {{^IF_token_name}}, where the token name from your Data Mapper or Apex is IF_resident and the token in the document template is {{^IF_resident}}.

The shown values don’t use the token text formatting.

Image token

{{IMG_<imagetokenname>}}

By using image tokens in a Microsoft Word or Microsoft PowerPoint document templates, you can insert dynamic images in the generated .docx and .pdf files.

The image token must start with IMG_. The format is {{IMG_<magetokenname>}}, for example, {{IMG_header}}. Salesforce supports the use of a single image, multiple images, and loop images.

Hyperlink token

{{HYP_<hyperlinktokenname>}}

By using hyperlink tokens in a Microsoft Word or Microsoft PowerPoint document templates, you can insert dynamic URLs in the generated .docx and .pdf files.

The hyperlink token must start with HYP_. The token format is {{HYP_<hyperlinktokenname>}}, for example, {{HYP_Salesforce Website}}.

Rich text token

{{RTB_<richtexttokenname>}}

By using rich text tokens in a Microsoft Word document template, you can insert rich text content in the generated .docx and .pdf files.

The rich text token must start with RTB_. The token format is {{RTB_<richtexttokenname>}}, for example, {{RTB_HeaderRichText}}.

If you must use rich text with images, use the RTB_token instead of the IMG_token.

By using Data True-Up tokens in DOCX templates, you can view and sync field values between the generated .docx document and the associated Salesforce record. These tokens enable side-by-side comparison of values and support updating either the document or the record directly from the Microsoft 365 Word add-in.

A Data True-Up token must start with DT_. The format is {{DT_<FieldName>}}, for example, {{DT_ContractTerm}}. Salesforce supports syncing for tokens on standard or custom parent-level objects. You can pull the latest field values from Salesforce into the document or push updated document values back to the record to maintain consistency.

Use bypass_tokensto retain token text in the generated document when no value is available. By default, tokens without data resolve to empty values, which can remove placeholders required for downstream workflows.

When you include a token name in bypass_tokens, document generation keeps that token unchanged in its original notation in the document, such as {{Sig_es_:signer1:signature}}. This behavior is useful for preserving e-signature tags or other placeholders that must remain for external processing. If a value is provided for a listed token, the value replaces the token. Tokens not included in the list continue to resolve to empty values when no data is available.

Enter the token name without curly braces ({{ }}) and specify values in bypass_tokens by using a comma-separated format. For example, include the token {{Sig_es_:signer1:signature}} in the document template and specify "bypass_tokens": "Sig_es_:signer1:signature" in the token data input.