Skip to main content
Two steps. Both are output-kind, which means they produce a real file and are treated as side effects: they short-circuit on a Test Run, and the artifact they write lands on the run for download.
Save to Matter is also an output-kind step, but the palette files it under Document I/O because it takes a document rather than producing one.

​
Export DOCX Report

Kind

Output

Latency

Fast
Renders a markdown body as a Word document and saves it as a run artifact. The most common final step in a custom workflow. Config Outputs
The body field accepts a mix of literal text and upstream references, so you can wrap a generated summary in your own framing paragraphs without post-processing the file.

​
Export Matrix as XLSX

Kind

Output

Latency

Fast
Renders a matrix as an Excel workbook. Use after a Build and Run Matrix step and pick that step from the matrix picker to inherit its id. Config Outputs
Leave Include citations on unless you have a specific reason not to. A matrix export without its citations sheet is a table of assertions with no way to check any of them.

​
What happens to an artifact

Artifacts written by these steps are recorded on the run and exposed as short-lived signed downloads, exactly like built-in workflow artifacts. See Results and artifacts for the download mechanics and expiry behavior.

Results and artifacts

Downloads, expiry, and matter attachment.

Document I/O steps

Save to Matter, the other way to land an output.