Skip to main content
Report steps extract structured data from an Automation execution. Define the outputs you want (test coverage, dependency counts, build status), and the agent extracts them using prompts or shell commands. Results appear in a table with CSV export. Use Report steps when you need to compare metrics across repositories or track values over time. Report results and the performance chart only appear for executions with more than one action. Single-action executions skip the report view.

​
How it works

  1. Earlier steps in the Automation do the work (run tests, scan dependencies, build).
  2. The Report step defines outputs with typed schemas.
  3. For each output, the agent extracts the value using a prompt or command.
  4. Results display in a table on the execution summary page.

​
Add a Report step

In the Automation editor, click + at the bottom of the step list and select Report. Automation workflow with a Report step showing three outputs

​
Configure outputs

Each output defines one value to extract. A Report step requires at least one output. Report step editor with output configuration

​
Output fields

​
Value types

When you set both min and max on a numeric type, the results table shows a color-coded progress bar: green above 80%, orange 50-80%, red below 50%.

​
Extraction methods

Prompt: the agent reads the execution context and extracts the value based on your instructions. Use for values that require interpretation.
Command: a shell command that outputs the raw value. Use for values you can parse deterministically.

​
Acceptance criteria

Optional CEL expressions that validate extracted values. The expression receives one variable (value) and must return a boolean. Examples:

​
View results

After execution, the results table appears on the execution summary page. Each row is one action (repository), and columns are the output keys you defined.
The report table and performance chart only appear for executions with multiple actions. If your Automation targets a single project or repository, the report step runs but results are not displayed in the summary view.
Click Export CSV to download the results as a spreadsheet for further analysis or reporting.

​
Example: test coverage across repositories

This Automation runs tests across multiple repositories and reports coverage metrics. Step 1 (Prompt):
Step 2 (Report): Schedule this on a weekly trigger to track coverage trends. Export CSV results to build dashboards or feed into other tools.

​
Next steps