fastest way to find solutions is by using the search function at the upper right.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →
You should handle each method’s output separately, as treating them the same way can cause errors if the expected data structure differs between methods. For example, a POST request might include a body, while a GET request might not, leading to undefined properties if not handled properly and enable “Allow Multiple HTTP Methods” in the node settings.
That’s interesting. Do you see the issue with a workflow with just the trigger? My instance is not on Heroku, it’s on ec2 with a nginx in front. Works fine here:
I don’t see any other errors. Here are the heroku logs:
2025-11-30T08:54:13.007548+00:00 heroku[router]: at=info method=GET path=“/webhook-test/c2cf89b5-8c51-424f-bcdd-9968791ff273” host=n8n.scoutnow.app request_id=7c34f34d-3a54-440f-d5ba-d92befbffeff fwd=“182.185.152.80” dyno=web.1 connect=0ms service=4ms status=500 bytes=77 protocol=http2.0 tls=true tls_version=tls1.3 2025-11-30T08:54:13.005812+00:00 app[web.1]: Cannot read properties of undefined (reading ‘getNode’) 2025-11-30T08:54:13.006849+00:00 app[web.1]: Error in handling webhook request GET /webhook-test/c2cf89b5-8c51-424f-bcdd-9968791ff273: Workflow Webhook Error: Workflow could not be started! 2025-11-30T08:54:13.259807+00:00 app[web.1]: Cannot read properties of undefined (reading ‘getNode’)
I used the following test command on my terminal:
curl ``https://n8n.scoutnow.app/webhook-test/c2cf89b5-8c51-424f-bcdd-9968791ff273 {“code”:0,“message”:“Workflow Webhook Error: Workflow could not be started!”}%