03 / 04

Sending responses

How to send your result back to Nodox.

Option A: respond directly (simplest)

Nodox reads your webhook's own HTTP response. In n8n, set the Webhook node's Respond option to When Last Node Finishes - whatever your final node outputs is your answer, no extra nodes or headers needed. Make sure the final node outputs only your result, not the payload/metadata envelope.

In Make the direct response is not what Nodox grades. Make answers "Accepted" as soon as the webhook is hit, before the scenario runs, so Nodox reads Make's acknowledgement rather than your result. In Make, use the callback in option B.

When to use which

Direct responses are perfect for briefs that finish quickly. Use a callback (Option B) when your workflow runs longer than the webhook window or a brief asks for it explicitly.

Option B: send a callback

After processing, send an HTTP POST request to the callbackUrl with your result. Include the callback token as a header:

Required header

x-nodox-token: token_xyz789

The body is simply your processed result:

Your response body (POST to callbackUrl)

{
  "name": "John Doe",
  "email": "john@example.com"
}

Required fields

Required

x-nodox-token header - callback token from metadata
JSON body - your processed result directly

Common mistakes

Forgetting the x-nodox-token header
Wrapping result in extra fields
Sending to wrong URL

Common mistakes

Don't make these errors

Missing x-nodox-token header (callbacks only) - The response won't be matched to your attempt
Wrong structure - Send your result directly as JSON, don't wrap it or echo the payload/metadata envelope
Wrong URL - Make sure you POST to callbackUrl, not your own endpoint
Timeout - Your response must arrive within 15 seconds (per test case) unless the brief says otherwise