Skip to main content

​
Build repeatable business processes

Workflows turn a business process into connected steps. They can collect input, transform data, apply logic, use AI, interact with connected applications, create documents, and return structured output.

​
When to use a workflow

Use a workflow when work has a repeatable sequence, known inputs, and an expected outcome. Good candidates include:
  • Intake and validation
  • Document review and drafting
  • Data extraction and classification
  • Recurring reports
  • Approval and routing processes
  • Updates across connected applications
Do not begin with a workflow when ownership, decision criteria, or the expected result are still unclear.

​
Workflow lifecycle

1

Define the outcome

Identify the trigger, required inputs, expected output, process owner, and review criteria.
2

Build the process

Add blocks for input, data handling, AI work, control flow, connected applications, and output.
3

Test representative cases

Include normal inputs, missing data, invalid values, and conditions that follow different branches.
4

Review permissions and failure paths

Confirm what the workflow can read or change, where approval is required, and how errors are handled.
5

Publish

Publish only after the tested output meets the process owner’s acceptance criteria.
6

Monitor and improve

Review runs, investigate failures, and update the workflow when the business process changes.

​
Create a workflow

Select New Workflow, then choose a starting method:
Give the workflow a specific name and description. A good description states when the workflow should run and what result it produces.

​
Workflow canvas

The canvas is the visual workspace for assembling a process.
  • Add blocks from the block library.
  • Connect output ports to compatible input ports.
  • Edit each block’s settings.
  • Group reusable logic into subflows.
  • Run the workflow and inspect each block’s output.
  • Save draft changes and publish when ready.

Interface

Learn the canvas, panels, controls, and workflow settings.

Blocks

Add, connect, configure, and manage workflow blocks.

Control flow

Add branching, matching, waiting, and other execution logic.

Live debugging

Inspect a run and diagnose unexpected results.

​
Connect workflows to workers

Publish the workflow, then add it to the appropriate worker from the worker’s capabilities. Clear names and descriptions help workers select the correct workflow for delegated work. See Workforce workflows for assignment guidance.

​
Production checklist

Before publishing a workflow used for business-critical work, verify:
  • Inputs are validated.
  • Sensitive values are handled appropriately.
  • Connected applications use the minimum required permissions.
  • Write, send, and destructive steps have suitable approval controls.
  • Errors and partial failures have a defined outcome.
  • Outputs have an owner and review process.
  • Representative test cases pass.
  • The workflow name, description, and version history are understandable to another administrator.
A successful test run does not remove the need for human review. Keep people in control wherever the process requires judgment, authorization, or accountability.