Add an HTTP Request block#

The HTTP Request block runs one of your saved requests as a step in a flow. This page covers how to point it at a request, and how to feed it values from earlier blocks.

Pick the saved request#

The block lives in the Actions group of the catalogue. Until you choose a request it reads "No request selected".

Pick a saved request from the dropdown, either on the block itself or from the Collection Request field in the inspector. The list shows every saved request across your collections, grouped by folder, with its method in front of the name. Once you choose one, the block shows the collection it came from, its method and its name.

The block always runs the saved version of the request. To change the URL, headers or body, open that request in its own tab, edit it and save. The next run picks up the change.

Feed it dynamic variables#

A saved request can contain placeholders written as ${name}. The block scans the request's URL, header values and body for placeholders. It lists the ones it finds under the block as dynamic variables. This is how you feed a request live values from earlier in the flow.

Each variable takes its value from one of a few sources. The block matches a detected placeholder to an upstream block's output of the same name. In the inspector you can instead set a variable to come from the params, headers or body of the data passed into the block. To pass a value in, connect an earlier block's output into the block's input.

Branch on Success or Failure#

The block has one input and two outputs.

• Send: runs the request.
• Success: takes a response in the 200 range.
• Failure: takes anything else, including a 3xx, 4xx or 5xx response, or a request the block could not send.

Only one of the two outputs fires per run, so you can branch cleanly on the outcome.

Either way the result is an object. It holds the response status and status text, its headers, the body, and the time and size of the response. When the body is JSON, the block parses it for you. The inspector's Output section shows the result the block emitted.

To run a whole flow rather than a single request, see the Flow block.