younifyd
Menu

Forward Request

Forward HTTP request to a target endpoint with optional routing rules

Use it in a workflow

  1. Add a step and choose the HTTP Proxy connector.
  2. Pick the Forward Request action (under proxy).
  3. Fill in the fields below, then reference the result from later steps as {{forwardRequest.response.data}}.

Fields

baseUrlstringrequired

Default target endpoint base URL - used when no routing rule matches (e.g., https://api.example.com)

methodstring

HTTP method - defaults to trigger's method if not specified

One ofGETPOSTPUTPATCHDELETEHEADOPTIONS

pathstring

Request path - defaults to trigger's path if not specified. Use {{expressions}} for dynamic values.

headerskeyvalue

Additional headers to merge with trigger headers

queryParamskeyvalue

URL query parameters

bodystring

Request body - defaults to trigger's body if not specified

routingRulesarray<any>

Dynamic routing rules - each rule routes matching requests to a specific endpoint. Rules are evaluated in order, first match wins. A rule can additionally require a specific GraphQL operation name and/or type (query/mutation/subscription), useful when multiple GraphQL operations share one endpoint.

Default []

accessDeniedRulesarray<any>

Block specific method and path combinations. If an incoming request matches any rule, a 403 Access Denied response is returned immediately before any routing or forwarding.

Default []

followRedirectsboolean

Automatically follow HTTP redirects

Default true

validateStatusboolean

Throw error on non-2xx status codes (if false, returns response regardless)

Default false

rejectUnauthorizedboolean

Verify SSL/TLS certificates (disable for self-signed certs in development)

Default true

excludeEnvironmentboolean

For rules that route to a workflow: run it against its default published instance instead of the calling workflow's environment.

Default false

Need more? See the HTTP Proxy guide for connection setup and behaviour shared by every action.

Was this page helpful?