Blocks that do real work#

HTTP Request, Flow, and Script each send, call, or compute something with a side effect.

Actions do work that has a side effect, such as sending a request or running another flow. The category has three blocks: HTTP Request, Flow, and Script. Each one starts from a trigger input and produces a result you can wire downstream.

HTTP Request#

Sends a saved request from a collection. Pick the request on the block face, then set any dynamic variables in the inspector.

The block has one input and two outputs. Both outputs carry the full response as an object.

  • Send: the input that triggers the request.
  • Success: fires when the response has a 2xx status.
  • Failure: fires when the status is outside 2xx, or when the block could not send the request at all.

Wire each output to the path you want that outcome to take.

See HTTP Request block for the detail page.

Flow#

Runs another saved flow as a step inside this one. Pick the target flow in the inspector.

The block has one input and two outputs.

  • Run: the input that triggers the target flow.
  • Output: carries the target flow's final result.
  • Done: a trigger that fires once the target has finished, so you can continue the parent flow from there.

A flow can call another flow up to a fixed nesting depth. Past that depth, the run stops with an error.

See Flow block for the detail page.

Script#

Runs a script you write in the inspector. If a response is wired into the block, the script can read it. The script can set environment variables, send its own requests, and record test results.

The block has one input and two outputs.

  • Run: the input that triggers the script.
  • Next: a trigger that fires when the script runs without error.
  • Result: carries the outcome as an object, including any test results and console output. This is also the path taken when the script errors.

For what you can write, see Scripting.

Which action block to pick#

Pick HTTP Request to call an endpoint saved in your collections. Pick Flow to reuse an existing flow as a single step. Pick Script when you need custom logic, or when you want to run test assertions as part of the flow.