Overview

In Shift Left Studio, Workflows are end-to-end workflows / integration tests: you design them as a visual graph of steps (nodes), run them like other tests, and review outcomes in Reporting when the execution run type is Workflows.

The main Workflows page explains the purpose in one line: create and manage end-to-end workflows / integration tests.

Two surfaces you will use

Surface	Purpose
Workflows list (Integration tests table)	See all workflows for your context, run or delete in bulk, open a workflow to edit, or add a new one.
Workflow Test editor	Build and save the flow: Test details, Test library, Node types, canvas with Launch workflow and Save.

Step-by-step UI tasks: Creating and Running Workflows.

What a workflow contains

Typical building blocks on the canvas include:

Start — entry point for the run.
Request / API steps — calls to HTTP or SOAP endpoints with parameters, authentication (for example environment default profile), and response outputs (body, headers, or fields you map forward).
Logic and utilities — for example log / debug, XML operations, branching on success vs failure.
Stop — end state (for example mark as passed).

Connections usually show success paths (for example solid green), data paths (for example dashed lines between outputs and downstream nodes), and failure / alternate exits where the builder exposes them (for example failure ports on request nodes).

The left panel may offer node type categories such as system blocks, variables and state, data operations, control flow, assertions and validation, execution control, and utilities—exact names depend on your version.

Who uses workflows

QA — full user journeys and regression across multiple calls.
Automation engineers — stable integration scenarios in CI.
Teams — scenarios that a single endpoint test does not fully represent.

Reporting

Workflow executions appear in Test reporting with Run type Workflows and drill through High-level test report → Workflow execution details → Detailed Test Report (Workflow).

Best practices

Keep flows readable: name workflows and nodes clearly.
Capture tokens and IDs as variables instead of hardcoding where possible.
Add checks on critical steps so failures point to the right node.
Include cleanup or idempotent steps when tests mutate data.

Understanding Workflows