I have created a simple webhook workflow but I am finding that when called it returns immediately with no content and not with the content set in the Respond to Webhook node. What am I doing wrong?
@mscherotter
You’re using test mode, a Test URL is only registered when you click Listen for test event or run the workflow in test mode. For normal use, you need to activate the workflow and call the Production URL. Webhook node documentation | n8n Docs
@mscherotter the symptom matches the Webhook node’s Respond setting still being on Immediately, which is the default — that mode returns 200 with no body the instant the webhook fires and never runs the Respond to Webhook node downstream. that’s why you’re seeing the empty response despite having the Respond to Webhook node wired up.
fix is in the Webhook trigger node itself: change the Respond option from “Immediately” to “Using ‘Respond to Webhook’ Node” (it’s a dropdown in the node’s main settings, not buried under Options). save, re-activate the workflow, and the downstream Respond to Webhook node will fire and return your inchesToMeters payload.
hey @mscherotter
can you tell me why my answer was ignored?
Was your wf published after the changes?
was the URL called correctly?
the called execution is not using the current version of the workflow or is not going through the path that executes the response node.
It shows that Respond to Webhook only works when the Webhook is configured to respond using that node.
Explains the Webhook response modes, including immediate response versus response using Respond to Webhook.
Helps justify checking Test URL vs Production URL and whether the workflow is active/published.
