How to create a webhook in n8n?

To create a webhook in n8n, you drag a Webhook node into a workflow, set its HTTP method (GET, POST, etc.), set the path (like /new-lead), save the workflow, and then copy the generated URL that n8n gives you. When that URL receives an HTTP request, n8n will start the workflow and pass the incoming data into the next nodes. That is the entire core idea: the Webhook node listens, the rest of the workflow reacts.

 

What a Webhook Is (in n8n terms)

 

A webhook is simply a public URL that n8n exposes so an external service can send data into a workflow. When the URL receives a request, it triggers the workflow instantly. In n8n, this is done using the Webhook node, which is a special “trigger” node — meaning it starts the workflow, not just processes data inside it.

• Trigger node = starts the workflow
• JSON input = the request body, query params, and headers arrive as JSON into the next node
• Method = HTTP method (most commonly POST)
• Path = the part after /webhook/ or /webhook-test/ in the URL

 

Step-by-step: Creating a webhook in n8n

 

This is the real, production-valid way to do it.

• Add a Webhook node as the first node. Webhooks must be the first node unless you explicitly allow “did not start workflow” mode.
• Set the HTTP Method to what your external service expects. Most external services send POST.
• Set the Path to something clean and predictable, like new-lead or github-push. No slashes. n8n will add them.
• Decide how you want to return a response:
  • Respond immediately: external system gets the confirmation instantly.
  • Respond with data returned from the last node: workflow fully runs before replying.
• Save the workflow. Until you save, the webhook URL is not active.
• Copy the webhook URL. n8n generates something like:
  • https://your-n8n-domain/webhook/new-lead (Production)
  • https://your-n8n-domain/webhook-test/new-lead (Test mode)
• Use a tool like curl, Postman, or an external service to send a test request to the URL.

 

Example: Testing a webhook with curl

 

curl -X POST https://your-n8n-domain/webhook/new-lead \
  -H "Content-Type: application/json" \
  -d '{"name": "John Doe", "email": "[email protected]"}'

 

What happens inside n8n when the webhook fires

 

When the request hits the URL, n8n does something very predictable:

• The Webhook node receives request data (body, headers, query params).
• It outputs a JSON item that the next node can use via expressions like {{$json.name}}.
• The next nodes run in order until the workflow ends.

The Webhook node output structure is extremely stable and looks like this:

{
  "body": {
    "name": "John Doe",
    "email": "[email protected]"
  },
  "headers": {
    "content-type": "application/json"
  },
  "query": {}
}

 

Important production tips

 

• Do not build long-running logic inside the webhook response path. If your workflow takes longer than your external service’s timeout (often 5–10 sec), switch the Webhook node to “Respond Immediately”.
• If you use n8n cloud or any load-balanced setup: always test with the /webhook URL (not /webhook-test) before committing the workflow to production.
• If the webhook must be secret, add a header check in the next node or use n8n’s built‑in authentication fields in the Webhook node.
• Always save the workflow after editing the Webhook node. n8n only activates the webhook when the workflow is saved and active.

 

Quick mental model to keep

 

A webhook in n8n is simply: “n8n listens at URL → request comes in → n8n turns it into JSON → your workflow runs.” Once you understand that, most webhook-based integrations become simple wiring: you configure the Webhook node, and n8n handles the rest.