# What is the Respond to Webhook node in n8n? > The n8n Respond to Webhook node answers a form only after the work is done, so its success message is true. How it pairs with the Respond setting. Source: https://learn.ynteractive.com/content/glossary/respond-to-webhook · Updated 2026-10-01 · Free from Stepthrough (https://learn.ynteractive.com) [n8n and automation](https://learn.ynteractive.com/content/glossary#topic-n8n-and-automation) · [AI glossary](https://learn.ynteractive.com/content/glossary) Updated October 1, 2026 · By [Robert Breen](https://learn.ynteractive.com/content/about) The Respond to Webhook node sends the reply back to whatever called an n8n webhook, such as a web form, at the moment you choose. It lets a workflow finish its real work first and then tell the form it succeeded, instead of answering the instant the data arrives. ## Why it matters for a small business When someone submits a form, the form waits for an answer before showing "thanks" or "something went wrong." If n8n answers right away, the form says thanks even when the workflow fails a second later, and the customer believes a request went through that never landed. That's how leads and service requests disappear without anyone noticing. Answering at the end makes the form's message true. The customer sees success only after the request is saved and the email is sent, and sees the error message, with whatever fallback you wrote there, like a phone number, when something breaks. ## In a real lesson: Build an AI Emergency Request Form for Your Plumbing Company In the [emergency request form lesson](https://learn.ynteractive.com/content/plumbing-emergency-request-form-ai-lovable-n8n), Blue Maple Plumbing, the made-up plumbing company in the lesson, gets a Lovable form for urgent problems. Its prompt sets two outcomes: on success, "Request received! Check your email for next steps." and on failure, "Something went wrong. Please call us instead." Which one a homeowner sees depends on how n8n answers. So right after adding **On webhook call**, you open the **Respond** dropdown and change it from responding immediately to **Using 'Respond to Webhook' Node**. Then, after the AI Agent (which sets the priority, saves the row to Google Sheets and emails a confirmation), you click the **+** on its right edge and add **Respond to Webhook**. There's nothing to configure; it sends the success response back. In the test, a burst pipe is marked Emergency, the row is saved, the email with shutoff steps goes out, and only then does the form show its confirmation. For an emergency, that order matters: if anything fails, the homeowner is told to call instead of waiting for an email that isn't coming. [Try this lesson free](https://learn.ynteractive.com/modules/lovable-n8n-plumbing) or [read the step-by-step guide](https://learn.ynteractive.com/content/plumbing-emergency-request-form-ai-lovable-n8n). ## Common confusions ### The Respond setting vs the Respond to Webhook node They work as a pair. The [Webhook](https://learn.ynteractive.com/content/glossary/webhook) node's **Respond** setting says who answers; the Respond to Webhook node is the answer. Pick the setting without adding the node and n8n has nothing to send, so the form shows an error. ### Responding vs emailing the customer The node replies to the app that called the webhook, not to the person. The confirmation email in the lesson comes from the Gmail tool. The response only decides what the form shows on screen. ## Tips - Place Respond to Webhook after the steps that matter, so success really means the work is done. - If the caller needs data back, like a reference number, the node can return JSON or text and a response code instead of the default. - Keep the workflow quick. A form left waiting too long may give up and show its error. ## Related terms [Webhook](https://learn.ynteractive.com/content/glossary/webhook) · [Test URL vs production URL](https://learn.ynteractive.com/content/glossary/webhook-test-url-vs-production-url) · [Web form](https://learn.ynteractive.com/content/glossary/web-form) · [HTTP status code](https://learn.ynteractive.com/content/glossary/http-status-code) · [Error handling](https://learn.ynteractive.com/content/glossary/error-handling) ## Where you use it: free lessons - [Build an AI Emergency Request Form for Your Plumbing Company](https://learn.ynteractive.com/content/plumbing-emergency-request-form-ai-lovable-n8n) (Lovable and n8n, 15 min) - [Lovable + n8n: Build a Web App with an AI Backend](https://learn.ynteractive.com/content/lovable-n8n-web-app-ai-backend) (Lovable and n8n, 15 min) - [Build an AI Service Request Form for Your HVAC Company](https://learn.ynteractive.com/content/hvac-service-request-form-ai-lovable-n8n) (Lovable and n8n, 15 min) ## Frequently asked questions **Do I always need a Respond to Webhook node?** No. If the caller doesn't care about the result, the Webhook node can answer immediately. You need it when the caller should only hear success after the work is done, like a form showing a confirmation. **Why does my form show an error even though the workflow ran?** Usually the Webhook node is set to wait for a Respond to Webhook node that isn't there, or the run failed before reaching it. Open the execution to see how far it got. [All AI glossary terms, A to Z](https://learn.ynteractive.com/content/glossary) · [Free prompt templates](https://learn.ynteractive.com/content/prompts)