Workflows

A workflow is an ordered sequence of monitors that run as a single unit. Each step executes in order, and you can extract values from one step's response and inject them into later steps as variables. This lets you simulate real business processes that span multiple API calls — such as creating a resource, reading it back, and then deleting it.

Why workflows matter

Individual monitors tell you whether a single endpoint is up and returning the right data. Workflows answer a harder question: does a multi-step interaction work end to end?

Common use cases include:

• CRUD sequences — create a record, verify it exists, update it, delete it, confirm deletion
• Authentication flows — obtain a token, then use it to call a protected endpoint
• Data pipelines — post data to an ingestion endpoint, then poll a downstream endpoint to confirm processing

Key characteristics

• Variable passing — extract values (e.g., a user ID or session token) from a step's response using JSON path or XML path, then reference them in subsequent steps
• Step-level results — each step produces its own result with full latency breakdown, so you can pinpoint which step in the chain degraded
• Conditions per step — each monitor in the workflow retains its own pass/fail conditions, and the workflow can be configured to stop on the first failure
• Scheduling — workflows are scheduled exactly like individual monitors and run from the same global node network
• Scoped variables — variables extracted within a workflow persist only for that workflow run; they do not leak into other monitors or workflows

See also

• Creating a workflow — step-by-step guide to building and running workflows
• Environment variables — pre-set and global variables available in monitors and workflows
• Conditions and assertions — how pass/fail rules work at each step