Documents

Produce files from reusable templates or from DocXML instructions. Both variants share the document node type; the subtype selects the pipeline.

Overview

Document steps turn structured workflow data into downloadable artefacts (for example Word documents). They combine model or author instructions with placeholders bound to expression variables.

Steps in this family

From template

Start from a managed template: map invoke and upstream keys into template placeholders, then generate a file with consistent branding and layout.

DocXML

Drive generation from DocXML instructions when you need finer control over structure than a static template alone provides.

Configuration

Execution tab: model instructions, template selection, and binding surfaces appropriate to the subtype.

Output tab: expose download URLs, filenames, or derived metadata for later steps (email attachments, CRM uploads, and so on).

Data flow

Tags in instructions resolve like other AI-adjacent fields: inbound input, trigger_inputs, global, const, and now helpers. See Expression variables.