Playbook outputs

🚧

Beta

Playbooks are available to selected workspaces while we continue to improve them. Contact your V7 account team if you need access.

Output steps present completed work to the user. Use an output for a report, file, structured record, link, or integration result. Do not use an output step for private reasoning or an intermediate calculation.

Define each deliverable

State the format, required fields, file type, and acceptance criteria for each output. If a run must create more than one file, define each file separately.

Use a resource when an output must follow a reusable template. The Playbook should preserve the template's structure.

Find outputs after a run

V7 Go aggregates all output steps in one overview when a run completes. This gives the user one place to find final deliverables, even when the Playbook used many steps.

Technical notes

An output can be text, a number, JSON, a URL, or a file. File outputs must be created as real files in the run's artefacts area so V7 Go can collect them.

Output previews are optional. Your workspace may not yet support creating or viewing output previews. A preview is a display sample, not a reusable run-time resource.

Audit output claims

Outputs can include citations from steps that have resolvable source evidence. In workspaces where HTML citation display is enabled, an underlined claim links to its source and shows the supporting quote on hover.