Control nodes: HTTP request, jump, loop and call another workflow

Master the four advanced control nodes in Workflows: HTTP request, Jump to node, Loop / for each, and Call another workflow.

Jun 26, 2026

Watch this step in the video · HTTP request

What they're for

These four nodes in the Actions section give you advanced flow control inside a workflow:

  • HTTP request: call an external API (GET, POST, PUT, PATCH, DELETE) and reuse the response in later steps.
  • Jump to node: break out of the normal traversal and continue from a specific node in the same workflow.
  • Loop / for each: iterate over a list and run a branch once per item.
  • Call another workflow: run another workflow as a subroutine and pass data to it.

They're the foundation for integrations and reusable logic, so they suit an intermediate-to-advanced level.

Requirements

  • The HTTP request node requires the Impulsa plan or higher (Lite doesn't include it). On the Lite plan the node is skipped and routes through its error output.
  • The rest are available on all plans (from Lite), within your plan's monthly workflow-run quota.

Steps

HTTP request

  1. Drag HTTP request onto the canvas.
  2. In the inspector pick the method, the URL, the headers (key/value list) and, if needed, the body (JSON or form).
  3. It has two outputs: success (2xx response) and error (4xx/5xx or network failure). Wire each to its branch.
  4. Use the response in later steps with {{$response.status}}, {{$response.body}} or {{$response.json.field}}.

Jump to node

  1. Drag Jump to node.
  2. Select the target node within the same workflow. Handy for retries or returning to an earlier question.

Loop / for each

  1. Drag Loop / for each.
  2. In source enter the list variable, e.g. $response.json.users (a comma-separated string is split too).
  3. Tune the item name (default $item) and index name ($index), and the max iterations (capped at 100 for safety).
  4. Wire the iteration branch (runs per item) and the done branch (after it finishes).

Call another workflow

  1. Drag Call another workflow and pick the target workflow (it must be active).
  2. The called workflow receives $caller.* variables (id, execution and input) so it knows who invoked it.

How to verify

Hit Test and review the trace: you'll see the HTTP request status code, how many times the Loop runs, and which node the Jump lands on. Save and turn the workflow on.

If it doesn't work

  • HTTP request routes to error without calling: your plan doesn't include the node (upgrade to Impulsa or higher) or the URL/credentials are invalid.
  • Headers aren't sent: use the inspector's key/value list; loose text isn't parsed.
  • The Loop doesn't iterate: the source didn't resolve to a list. Check the variable path.
  • Call another workflow does nothing: the target workflow is inactive.

Tips

  • Chain HTTP request → Loop to process each record an API returns.
  • Pull shared logic (e.g. notify the team) into a separate workflow and reuse it with Call another workflow.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp