Skip to main content

Use Dynamic Tokens in Templates and Documents - Article

Use context-specific placeholders to create meaningful personalized emails, certificates and documents, and diagnose unresolved or empty output.
Updated: 14 Nov 2026
5 min read

Summary

Dynamic tokens insert record-specific information into reusable text and documents. The same template can identify the right person, training or date without maintaining a separate version for every recipient. Tokens work within a defined context: use the supported choices for the email, certificate, invoice, button or other output you are editing.

Use this article to:

  • Choose tokens from the correct output context
  • Understand data and language dependencies
  • Test meaningful personalized output
  • Distinguish template placeholders from security credentials

Personalize a reusable message without losing meaning

A training confirmation should name the relevant offer and provide the right next action. A certificate should identify the qualified person and the qualification. An invoice should describe the relevant commercial record. Tokens allow that information to be supplied from the record when the output is generated.

Write the surrounding sentence so it still communicates a useful instruction. “Your training [activity title] is available” has a clear purpose; a list of unexplained field values may be technically personalized but difficult to understand. Test the whole message, including its subject, links and optional information.

Use the token list for the current context

Open the template or object you are actually configuring and use its available token-insertion tool or supported token list. In Settings → Email sending, the email editor provides token insertion for the selected System Email. Email Sending owns that procedure.

Do not copy a placeholder from a certificate into an invoice or from one email type into another and assume it will resolve. Different contexts provide different underlying records. A participant-specific token needs a participant context; a transaction token needs a transaction context.

Output contextTypical purposeWhat to verify
System Email or workflow messageIdentify the recipient, training or required next actionThe selected message supplies the required record and recipient
CertificatePresent identity, qualification and applicable datesThe certificate type provides the required learning evidence
Invoice or order confirmationIdentify the buyer, seller and commercial recordThe token belongs to the correct document and transaction context
Supported URL/button or watermark fieldBuild a contextual link or displayed valueThe field supports token substitution and the resulting value is usable

This is a context map, not a universal token catalogue. Use the live selector or current supported list for exact syntax and availability. Custom fields and customer-specific tokens must be verified in the relevant platform configuration.

Keep syntax and underlying data intact

Insert the token as provided. Preserve its brackets, spelling and internal name. Edit the surrounding language, rather than translating the token name or rebuilding it from memory. A token that looks like ordinary text can still be interpreted by the generator.

Check that the source record contains the required value. An empty optional profile field cannot supply meaningful personalized text. Design optional sentences so a missing value does not produce an unclear instruction, and verify the generator’s actual output rather than assuming a fallback exists.

For translated templates, review both the language version and the record value. A token can be syntactically valid while the resulting title or date does not fit the surrounding sentence. Keep translated labels, punctuation and line breaks readable in the final output.

Treat text and links as different outputs

A visible label and a destination URL have different jobs. If a supported button or URL field uses a token, verify that the generated link opens the intended permitted destination for the actual recipient. A title that reads correctly does not prove the URL was constructed correctly.

Do not treat a generated link as a new permission grant unless that specific feature is designed to provide one. A normal content link still relies on the recipient’s access. An invitation or one-time authentication link has its own lifecycle and must be handled under the procedure that owns it.

Test a representative result

Use the available preview where it can supply the necessary context. Some System Emails are user-dependent and show Preview unavailable. In that case, use a controlled representative case through the owning workflow rather than interpreting the absence of a preview as a broken template.

Choose records with realistic names, titles and dates, including a long value and a missing optional field where relevant. For a certificate or PDF, inspect the rendered document as well as the text. A correct value can still be clipped or placed badly in the layout.

Keep placeholders separate from credentials

A template token is a placeholder that inserts supported record data. An API access token is an authentication credential used by a connected application. A one-time sign-in or invitation link can provide a specific access route under its own rules. They are different mechanisms even when people casually call each one a token.

Never paste an API bearer token or client secret into a template as personalization. Use the owning API guide for credential management and the owning invitation or authentication procedure for temporary access links.

Verify the output

Scenario or checkExpected result or evidence
A populated representative recordCorrect person, training, transaction or qualification data appears
A missing optional valueThe output remains meaningful or the template is adjusted deliberately
A translated versionThe surrounding sentence and resolved value form clear language
A contextual button or linkThe actual recipient reaches the correct permitted destination
A PDF or certificate with long textValues remain readable within the final layout

Troubleshooting

ProblemWhat to check
A token appears literally in the outputVerify exact syntax and support in that specific field and context
A value is emptyCheck the underlying record and whether the chosen workflow supplies it
A token works in one email but not anotherDifferent emails can have different record contexts and supported tokens
A translated message reads awkwardlyReview the translated sentence together with real resolved values
A link label is correct but the destination failsInspect the generated URL and the recipient’s actual access
An API credential has been placed in a templateRemove it from the template and handle credential exposure through the organization’s security process

FAQ