Report Node

Add and label the node

Drag Report from the Basic palette, connect it after the steps that produce its data, and open its properties. Enter a clear Node label and optional description.

Choose how the report is made

Fill a Word template

Choose Fill a Word template, then select a .docx source:

• Upload File — upload the template from your device.
• From Documents — select an existing template in Documents.

Templates can contain {{variable}} or <<variable>> placeholders. The node detects placeholders and fills them with workflow values at runtime. Use Variable Panel to copy exact names.

Enable Fail when template variables are missing when an incomplete report must stop the step. When it is off, missing values are left empty.

AI writes it

Choose AI writes it when the report body should be authored in Flow Builder rather than filled from a Word file. Select the available theme:

• professional
• minimal
• branded

Use AI Builder to describe and author the report, or edit the report HTML directly when that control is available. Review the rendered content and its workflow placeholders before saving.

Output

Choose PDF or DOCX as the output format. Set the output filename pattern and insert workflow variables or available built-ins such as date, time, and workflow name.

The node exposes report results for later steps, including:

• report_path
• file_name
• document_id
• download_url

Use Variable Panel for the exact node-scoped variable names produced by the current design.

Save to Documents

Enable Also save the report into a Documents folder when the generated file should remain in the document library.

• The automatic option saves into the current workflow's Applications location under Generated Reports.
• Turn off the automatic location to choose a specific Documents destination.

If the option is off, the workflow can still use the generated output through the node's variables.

Validation checklist

1. The Report node runs after every variable it uses.
2. A Word template is .docx and its placeholders match Variable Panel.
3. AI-authored content has been reviewed, not only generated.
4. The filename is valid and the correct PDF/DOCX output is selected.
5. Missing-variable behavior matches the business rule.
6. The Documents destination is accessible and appropriate.
7. A test run opens or downloads the expected file.