Parameters and tags reference

Azumuta lets you insert live data into work instructions, docx reports, and webhooks. This can be a parameter you defined or a value Azumuta already tracks. The syntax differs by location, and this article lists it for each. It covers your own parameters and Azumuta’s core built-in tags. Module-specific docx tags, such as ticket, answer, variant, image, and recap tags, are covered in their own articles, linked from Related articles below.

Two kinds of values

• Your own parameter: data you define and link to an article or product order, such as Color or Body Material. See Introduction to parameters for more information.
• Built-in values: data Azumuta already has, like a Product Order, the name of the operator, or a due date. See Built-in values reference for the full list.

Where you can use them, and the exact syntax

The reference format depends on where you are using it.

Work instructions: visual pages, calculations, and checks

Use ${...} wherever you’re adding a live value into a work instruction: a text box on a visual page, a step’s description, or a calculation.

• Your own parameter: ${Parameter_key}
• A built-in value: ${=identifier}
• A calculation: ${=Parameter_key + 3}

See Use parameters in a Work Instruction step, Use parameters on an image in a Work Instruction, and Performing calculations with Parameters for the full walkthroughs, including the available math operators.

Exception: dedicated formula fields. A rule’s Formula evaluates to true (advanced) condition is itself a formula field, not free text with a value embedded in it, so you type the expression directly with no ${...} wrapper at all: dateTime("12/05/2026 14:30", "dd/MM/yyyy HH:mm"), for example. dateTime() reads a date from text, so its pattern uses plain date tokens without the FORMAT: prefix. See Rules: Advanced.

Docx / PDF report templates

Use plain curly braces, without the dollar sign, and a leading = for a built-in value:

• Your own parameter: {p_Parameter_key} (the p_ prefix marks a parameter)
• A built-in value: {=identifier}, {=dueDate}, and so on
• Show a parameter only if it has a value: {#p_Parameter_key}{p_Parameter_key}{/p_Parameter_key}, with {^p_Parameter_key}fallback text{/p_Parameter_key} for when it’s empty

This applies to Product Order, Work Instruction, recording/audit, and issue docx reports alike. See Basic Tags on a Docx Report, Parameter Tags, and Conditional Parameter Tags.

Exception: answer and recap tag loops. Inside a {#answers}...{/answers} loop or a recap section, several built-in values drop the leading = and appear as a bare tag instead, for example {workinstructionName}. See Answer Tags (Basic) for that loop’s own tag list.

Webhooks and export file/folder naming

Use ${...}, the same as in work instructions, since both go through the same engine:

• Your own parameter: ${Parameter_key}
• A built-in value: ${=identifier}

This applies to a trigger’s webhook payload and URL, a peripheral integration’s webhook, and the file name or destination folder path of an exported report. See Calling a Webhook from a Trigger.

Built-in values reference

These are supplied by Azumuta automatically. Write them as {=tag} in docx reports and ${=tag} in work instructions and webhooks.

Availability depends on context. Everywhere means work instructions, docx reports, and webhooks. The other values only resolve while generating a specific export (a work instruction PDF or a recording/audit report), not in a webhook or a live work instruction step.

Product order

Dates

Date formats

today, dueDate, executionDate, and finishDate accept an optional format in parentheses. In a docx report, either start a custom pattern with FORMAT:, for example {=dueDate(FORMAT:dd/MM/yyyy)}, or use a preset name, for example {=dueDate(DATE_SHORT)}. Without a format, the date uses the default for the report language.

Custom pattern tokens

Tokens are case-sensitive. The examples use 6 August 2014 at 14:05:09.

Preset names

Presets follow the report language and time zone. Use the name exactly as written.

User and device

Work instruction and export

treePath accepts an optional slice, for example {=treePath(-2)} for just the last folder, the same way Array.slice would.

issueNumber and auditNumber are also sent automatically as event fields in a trigger’s webhook payload, separate from inserting them yourself with ${=...}. See What Azumuta Sends.

Related articles

Parameters

• Introduction to parameters
• Use parameters in a Work Instruction step
• Performing calculations with parameters

Docx reports

• Basic Tags on a Docx Report
• Parameter Tags
• Conditional Parameter Tags
• Answer Tags (Basic)
• Answer Tags (Advanced)
• Variant Tags
• Displaying Images on a Docx Report
• Ticket Tag
• Recap Tags

Webhooks and rules

• Calling a Webhook from a Trigger
• Rules: Advanced