Skip to content

Respond to Webhook

Respond to Webhook controls the HTTP reply sent to the caller of a webhook-triggered workflow. Put it at the end of the request path to return a status, body, and headers based on the workflow result.

  • Category: Triggers
  • Purpose: Sends the response back to whoever called the webhook
  • Inputs: input, plus the response fields below
  • Outputs: None (the response leaves the workflow)
  • Configuration:
  • HTTP Status Code: 200, 201, 202, 204, 400, 401, 403, 404, 422, 500, 502, 503. Default 200
  • Response Config: all_incoming_items (return whatever arrived), no_data (status code only), json (return the body you write). Default json
  • Response Body: The content to return. Supports ${{ }} templating, so an agent's answer can be passed straight through. Shown when json is selected
  • Content-Type: application/json, text/plain, text/html. Default JSON. Must match what the body actually contains
  • Custom Headers: Extra response headers as JSON
  • Max Response Size (KB): 1–10240, default 1024
  • Usage: Pairs well with Condition — return 200 for valid input and 400 for invalid input using two separate response nodes.