Webhook Not Returning Custom Response on n8n.cloud (v1.11.0)

Questions
1

Hello n8n Team,

I am experiencing an issue on my n8n.cloud instance where my webhooks are not returning the custom response from my workflow. They consistently return the default {"message":"Workflow was started"} message, even on active workflows using the production URL.

My Environment Details:

  • n8n Version: 1.11.0

  • Hosting: n8n.cloud

  • Instance ID: (You can find this in your “About n8n” screenshot)

What I’ve Tried:

I have worked extensively to debug this and can confirm the following:

  1. The issue occurs on active workflows using the Production URL.

  2. The workflow execution log shows a successful run all the way to the final node.

  3. I first tried using a Respond to Webhook node, but the automatic detection failed to send the custom response.

  4. I then tried a workaround using the Webhook node’s “Response Data: Last Node” option, with Set nodes creating the final output. This also failed and returned the default message.

  5. I have tried this with a minimal two-node test case (Webhook → Set with Response Data enabled) and it still fails.

Here is the JSON for the simple workaround workflow that is still not working correctly. This should be a perfect minimal reproducible example for you to test.
2

hello @Garima_Juneja

This example works fine

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.