Skip to main content

Redirect Node

What it does​

Returns an HTTP redirect response to the client and ends request processing for the current branch.

Inputs/config​

  • Redirect target URL.
  • HTTP status code (typically 301, 302, 307, or 308).
  • Optional headers (for example cache directives).

Outputs/branches​

  • Terminal behavior for request flow.
  • No matched_output.
  • Downstream edges are generally not used.

Example usage snippet​

{
  "id": "n_redirect",
  "type": "redirect_node",
  "config": {
    "status": 302,
    "location": "https://docs.example.com/new-path"
  }
}

Common pitfalls​

  • Using temporary redirect when permanent redirect is required.
  • Building unvalidated dynamic redirect URLs (open redirect risk).
  • Expecting workflow steps after redirect to affect the client response.