Outputs

The Outputs tab provides visibility into all output variables generated by the workflow. Outputs are commonly used to pass data to other workflows, automation pipelines, or external systems, making them a key integration point in Infrastructure as Code (IaC) workflows.

---

1. Outputs Table

This table lists all workflow outputs.

Each output shows:

Field	Description
Name	The output variable name defined in the workflow or Terraform configuration
Type	The data type (e.g. string, number, list, map)
Value	The actual returned value from the workflow execution
Options Wheel	Show the reference string, which can be used in workflows and templates

2. JSON View

When Show JSON is enabled:

• All outputs are displayed in raw JSON format

Sensitive outputs

If the output contains sensitive fields such as credentials, passwords, or API tokens, the leaf values are marked as <sensitive> to prevent accidental exposure.

Example:

{
    "sensitive_outputs": {
        "sensitive": true,
        "type": [
            "tuple",
            [
                "number"
            ]
        ],
        "value": [
            "<sensitive>"
        ]
    }
}

When "sensitive": true, the internal leaf values are masked as <sensitive>. The masking applies to individual values within lists, maps, or other complex types, not the entire structure.

info

Sensitive output masking applies only to workflows executed after January 20, 2026. Outputs from workflows run before this date may still display actual sensitive values.

3. Output Reference

StackGuardian allows referencing of outputs between workflows. Outputs can be referenced inside VCS configuration and in Environment Variables of a workflow using the syntax below.

Terraform Workflow

• Example syntax to reference a value from the outputs generated by Terraform workflow

${workflow::<WORKFLOW_GROUP_NAME>.<WORKFLOW_NAME>.outputs.<VARIABLE_NAME>.value}

• Example syntax to a Stack which is a set of workflows that are closely associated with each other, reference a value from workflow outputs under the STACK as follows,

${workflow::<WORKFLOW_GROUP_NAME>.<STACK_NAME>.<WORKFLOW_NAME>.outputs.<VARIABLE_NAME>.value}

• Example syntax to reference an element inside an array value generated by Terraform workflow

${workflow::<WORKFLOW_GROUP_NAME>.<WORKFLOW_NAME>.outputs.<VARIABLE_NAME>.value.1}

Custom Workflow

• Example syntax to reference a value from the outputs generated by Custom workflow

${workflow::<WORKFLOW_GROUP_NAME>.<WORKFLOW_NAME>.outputs.<VARIABLE_NAME>}

Nested Workflows

To reference outputs from Workflows in a nested Workflow Groups or Stack, add the path to the Workflow Group as follows:

${workflow::<PARENT_WORKFLOW_GROUP_ID>/<WORKFLOW_GROUP_ID>.<WORKFLOW_ID>.<OUTPUT_KEY>}

For more detailed instructions on creating references, refer to the Reference Variables documentation.

---

4. Artifacts Section

Below the Outputs table is the Artifacts section.

Artifacts include files generated or used by the workflow (e.g., Terraform state files, logs).

Common artifact examples:

Artifact	Usage
tfstate.json	Terraform state storage for tracking deployed infrastructure
Logs	Debugging workflow execution
Generated files	Assets created during workflow runs

Actions:

• Download artifacts to inspect or reuse locally
• Upload artifacts such as existing Terraform state to import environments (must be named tfstate.json)

Artifacts are crucial for maintaining state across runs, enabling rollbacks, and debugging deployments.