n8n Webhook nodeConfigure Webhook in n8n.

A webhook answers one method at a time by default: GET or POST, not both. Turning this boolean on in the node settings lifts that, and the node then gets one output per method so the workflow can branch on how it was called.

• Allow Multiple HTTP Methods: off by default; once on, the node accepts GET and POST, and you add others in the HTTP Method field.
• HTTP Method: the list to listen on, among DELETE, GET, HEAD, PATCH, POST, PUT.

This is the tail of the webhook URL. n8n fills it with a random string so two nodes never collide, which is safe but impossible to communicate to a vendor. Replace it with something readable whenever the URL has to be typed into someone else's settings screen.

• Path: a text field, placeholder webhook, that also takes route parameters written with a colon: /:variable, /path/:variable, /:variable/path, /:variable1/path/:variable2 or /:variable1/:variable2. When a dynamic value is used, n8n prepends webhookId to the path.

Nothing stops a stranger from calling an open webhook URL. This selector adds a check in front of the workflow, and a call that fails it never reaches the first node.

• Authentication: basicAuth for a user and password pair, headerAuth for a shared secret sent in a header of your choosing, jwtAuth for callers that already send a signed token, none for a public endpoint.

Decides when the caller gets its answer and what is in it. This is what separates a fire-and-forget listener from an endpoint the caller waits on.

• Respond: onReceived answers as soon as the node runs, with the message Workflow got started; lastNode returns the data of the last node executed; responseNode hands the reply to a Respond to Webhook node placed further down.
• Response Data: with lastNode, choose allEntries for an array, firstEntryJson for a single object, firstEntryBinary for a file, or noData for an empty body.
• Property Name: required with firstEntryBinary, it names the binary property to return.

Incoming requests are read as JSON unless told otherwise. Switch this on and the node accepts a file in the request instead, which is what you need the day a vendor posts a PDF rather than a link to one.

• Binary File: a boolean saying the webhook will receive binary data. It only shows up when the method is POST, PATCH or PUT.

Once a file comes in, it has to be stored somewhere on the item so the following nodes can find it. That is all this option does, and it matters only when binary data is actually received.

• Field Name for Binary Data: the name of the output field the received file is written to.

Paste a webhook URL into a chat tool and its link previewer fetches it on the spot. The workflow runs, an execution appears, and nobody asked for it. This option drops those callers before anything happens.

• Ignore Bots: a boolean that ignores requests from bots such as link previewers and web crawlers.

Authentication checks a secret, this one checks the address. Useful when the caller is a fixed server rather than a browser, because the range of legitimate origins is then small and known in advance.

• IP(s) Allowlist: a comma-separated list of addresses or CIDR ranges, placeholder e.g. 127.0.0.1, 192.168.1.0/24. Empty means every address is allowed.

Some callers want a status code and nothing else, and some are unhappy with an unexpected body. Switching this on sends the response with no body at all.

• No Response Body: a boolean that prevents n8n from sending a body. It is available with Respond set to onReceived.

By default the response carries the whole JSON of the entry. Naming a property here narrows it to that single value, which suits callers that expect a bare string rather than an object.

• Property Name: the name of the property whose value is returned instead of the whole JSON. It appears with Respond on lastNode and Response Data on firstEntryJson.

Turn this on and the node keeps the body as it arrived instead of parsing it. Anything the parser would have reshaped, or rejected, comes through untouched.

• Raw Body: a boolean saying the node receives the body in raw form, as binary.

A successful run answers with a default code. Override it when the caller reads the status to decide what happens next, which is common with vendor integrations that retry on anything unexpected.

• Response Code: pick from 200, 201, 204, 301, 302, 304, 400, 401, 403, 404, or customCode.
• Code: the number to return with customCode, placeholder e.g. 400.

Responses go out as application/json. This field replaces that header when the caller expects another format, and it only changes the declared type, not the data itself.

• Response Content-Type: a custom content-type to return instead of application/json, placeholder application/xml. It shows with Respond on lastNode and Response Data on firstEntryJson.

Rather than returning what the workflow produced, this sends a fixed string back. The reply is decided at design time and does not depend on the run.

• Response Data: the custom text to send, placeholder success. It is available with Respond set to onReceived.

Adds headers to what the node sends back. Each entry is a name and a value, and you can add as many as the caller needs.

• Name: the name of the header.
• Value: the value of the header, which takes an expression such as {{ $json.token }} when it has to come from the workflow.