younifyd
Menu

Connectors

HTTP Response Connector

End a workflow route by sending a custom HTTP response — built directly (status, headers, body) or forwarded from a previous step's own response.

On this page

What this connector is for

Ends a workflow route by sending a specific HTTP response back to whatever called it — either one you construct yourself (Send Raw Response) or one that reuses a previous step's own output (Send Response From Step). Whichever action runs, the route stops there: no step configured after it will execute, so referencing this step's own output from a later step isn't meaningful.

Send Raw Response

Configuring it

  • HTTP Status Code — required, defaults to 200. Must be between 100 and 599.
  • Response Headers — optional key/value pairs.
  • Response Body — optional. If a Content-Type of application/json is in effect (explicitly set or via the default below) and the body parses as valid JSON, it's sent as parsed JSON; otherwise it's sent exactly as typed, even if it looks like invalid JSON.
  • Content-Type — defaults to application/json. Only applied if neither Response Headers nor the body-handling above already set a Content-Type/content-type header explicitly.

Reading the response

  • {{<stepReference>.response.status}} — the status code sent.
  • {{<stepReference>.response.headers.<name>}} — a header sent, including the resolved Content-Type.
  • {{<stepReference>.response.data.<field>}} — the body that was sent (parsed JSON, or the raw string).

Example

HTTP Status Code: 404
Response Headers: Content-Type: application/json
Response Body: {"error": "Order not found"}

Send Response From Step

Configuring it

  • Select Step — required. A previous step's response envelope — pick it from the dropdown, which resolves to {{<stepReference>.response}} (the whole { status, headers, data } object, not just .data). Its status becomes this response's status (only if it's a number between 100–599; otherwise defaults to 200), its headers are copied across (minus a fixed list of hop-by-hop/transport headers that would be wrong to re-serve as-is: content-encoding, transfer-encoding, connection, keep-alive, upgrade, proxy-authenticate, proxy-authorization, te, trailer, cf-ray, cf-cache-status, cf-request-id, x-envoy-upstream-service-time, server, date, etag, vary), and its data becomes this response's body.
  • Additional Response Headers — optional; merged on top of the selected step's headers, and override any of the same name.

If no Content-Type/content-type ends up set by either the selected step's headers or Additional Response Headers, it defaults to application/json.

Reading the response

  • {{<stepReference>.response.status}} — the status code sent (the selected step's own status, or 200).
  • {{<stepReference>.response.headers.<name>}} — a header sent.
  • {{<stepReference>.response.data.<field>}} — the selected step's own body, forwarded as-is.

For example, forwarding a previous "Get Order" step (reference getOrder) straight back to the caller: select {{getOrder.response}} as the step, add no extra headers — the caller receives getOrder's own status, headers, and body unchanged.

Example

Select Step: {{getOrder.response}}
Additional Response Headers: Cache-Control: no-store

Also applies here

Step Name

What it's for

Every step in a workflow gets a name — either one you set or a default based on the connector and action (e.g. "Get Order Details", "Send Welcome Email"). It's shown throughout the UI and in your execution history, and it's also the source for the step's Reference — a camelCase identifier auto-generated from the name (e.g. "Get Order Details" → getOrderDetails) — which is what you actually use in {{...}} expressions to read this step's output from later steps. See Step Reference.

Rules

  • Must be at least 2 characters, and 50 characters or fewer.
  • Must be unique within the workflow — reusing a name that's already taken will be rejected, with a suggested alternative (e.g. "Get Order Details 2").
  • Can't be empty.

Tips

  • Prefer a descriptive, human-readable name over a generic one — "Get Order Details" is easier to work with later than "HTTP Request 2", especially once a workflow has a dozen steps.
  • Renaming a step updates every reference to it elsewhere in the workflow automatically.
HTTP Response Connector — younifyd