n8n Respond to Webhook: Return JSON, Status Codes, Redirects and Files

By default an n8n webhook answers "Workflow got started" as soon as it receives a request. That is fine for fire-and-forget events, but not when a form, an app or another system waits for a result. The Webhook node and the Respond to Webhook node let you return exactly what the caller needs: JSON, a status code, headers, a file or a redirect.

The four response modes of the Webhook node

"When Last Node Finishes" has a Response Data option: All Entries, First Entry JSON, First Entry Binary or No Response Body.

Set up the Respond to Webhook node

1. 1 In the Webhook node, set Respond to "Using 'Respond to Webhook' Node".
2. 2 Add a Respond to Webhook node after the nodes that produce the answer.
3. 3 Choose "Respond With": All Incoming Items, Binary File, First Incoming Item, JSON, JWT Token, No Data, Redirect or Text.
4. 4 Add options if needed: Response Code, Response Headers, Put Response in Field.

Example JSON body with an expression:

{
  "ok": true,
  "leadId": "{{ $json.id }}",
  "message": "Thanks, we will call you within one business day."
}

Return a proper status code

APIs communicate through status codes. Use the Response Code option:

• 200 or 201 when the request succeeded or created something;
• 400 when the input is invalid (missing email, wrong format);
• 401 or 403 when authentication fails;
• 409 when the record already exists.

A typical pattern is an IF node right after the Webhook: one branch validates and processes, the other goes to a Respond to Webhook node with code 400 and a clear message such as {"error":"email is required"}.

The multi-item trap

The Respond to Webhook node runs once, using the first item it receives. If the previous node outputs 50 items, the caller gets one. Two documented solutions:

• Choose "All Incoming Items" in Respond With, which returns every item.
• Or put an Aggregate node before it ("All Item Data (Into a Single List)") to build one item that contains the list.

What happens in edge cases

The documentation lists the behaviour precisely:

• The workflow finishes without reaching a Respond to Webhook node: the caller receives a standard message with status 200.
• The workflow errors before the first Respond to Webhook node: the caller receives an error with status 500.
• A second Respond to Webhook node runs after the first: it is ignored.

So put the Respond to Webhook node on every branch that should answer, including your error path.

Return a file

Set Respond With to "Binary File" and select the binary property, for example a PDF generated earlier. Add a Content-Disposition response header if the browser should download it rather than display it:

Content-Disposition: attachment; filename="quote-812.pdf"

Redirect the user

For form submissions from a website, "Redirect" sends the visitor to a thank-you page. Set Redirect URL to an absolute address.

HTML responses are sandboxed

Since n8n 1.103.0, HTML returned to a webhook is wrapped in a sandboxed iframe. JavaScript cannot access the top window or local storage, basic auth headers are not available inside, and relative URLs do not work. Use absolute URLs, or return JSON and render it on your own site.

Long-running workflows

On n8n Cloud, requests go through Cloudflare. If the webhook does not respond within 100 seconds, the caller receives a 524 error. For long jobs, the documentation recommends two webhooks: one that starts the job and answers immediately with a job ID, and a second one the caller polls for the result.

Worked example: a quote calculator API for your website

Your website has a small form: square metres and service type. You want an instant price shown on the page, computed by n8n.

1. 1 Webhook: POST /webhook/quote, Respond: "Using 'Respond to Webhook' Node", Allowed Origins (CORS): https://www.yoursite.com.
2. 2 IF: {{ Number($json.body.sqm) > 0 && ['standard','premium'].includes($json.body.service) }}.
3. 3 Code (true branch): compute the price.

const { sqm, service } = $input.first().json.body;
const rate = service === 'premium' ? 42 : 28;
const price = Math.max(150, Math.round(Number(sqm) * rate));
return [{ json: { price, currency: 'USD', service, sqm: Number(sqm) } }];

1. 1 Respond to Webhook (true branch): JSON { "price": {{ $json.price }}, "currency": "USD" }, code 200.
2. 2 Respond to Webhook (false branch): JSON { "error": "sqm and service are required" }, code 400.

On the website, a few lines of JavaScript call the webhook and display the price:

const res = await fetch('https://n8n.example.com/webhook/quote', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ sqm: 85, service: 'standard' }),
});
const data = await res.json();

The rates in this example are placeholders: use your own.

Respond Immediately, then keep working

For webhooks from payment providers or CRMs, the sender only needs a fast acknowledgement. Set Respond to "Immediately": n8n answers at once and the rest of the workflow keeps running. This avoids sender timeouts and retries, which can otherwise trigger the same workflow several times.

If you need to acknowledge first and still return a custom code, place a Respond to Webhook node right after the Webhook, then continue the work after it. Only the first Respond to Webhook node that runs is used.

Status codes worth using

Troubleshooting table

Production checklist

• A Respond to Webhook node on every branch, including validation failures.
• Status codes that match the outcome (200, 201, 400, 409).
• Lists aggregated or returned with "All Incoming Items".
• A response in under 100 seconds on n8n Cloud, or an asynchronous pattern.

Frequently asked questions

Why does my n8n webhook only return one item?

The Respond to Webhook node uses the first incoming item. Choose "All Incoming Items" or aggregate the items into one before responding.

How do I return a custom status code from an n8n webhook?

Use the Response Code option in the Respond to Webhook node, or in the Webhook node when you do not use Respond to Webhook.

What does n8n return if the workflow fails before responding?

An error with status 500, when the failure happens before the first Respond to Webhook node.

How long can an n8n webhook take to respond?

On n8n Cloud, less than 100 seconds, or the request fails with 524. Self-hosted limits depend on your proxy and server timeouts.

How do I return HTML from an n8n webhook?

Use Respond With "Text", which sends text/html by default. Since n8n 1.103.0 the HTML renders in a sandboxed iframe, so use absolute URLs and avoid scripts that access the parent window.

Can I set cookies or custom headers in the webhook response?

Yes, with the Response Headers option of the Respond to Webhook node.

What happens if two Respond to Webhook nodes run?

Only the first one is used; the second is ignored.

Steve, founder of PURIST

Steve founded PURIST, a workflow automation studio working with n8n, Make and Claude AI, and is the point of contact on every project. Prices and features in our articles come from vendor documentation and public pricing pages. How we research and score tools.