Webhook Fails on Production URL: Cannot read properties of undefined (reading 'execute')

When I send any POST request to the Production URL of a webhook, the execution fails immediately with the error: Error: Cannot read properties of undefined (reading ‘execute’)

This happens even with a brand new workflow that contains only a single Webhook node and no other nodes connected. The “Test URL” works perfectly when listening for an event, but the Production URL always fails with this error.

Crucial Diagnostic Step:

To isolate the problem, I have tested the Production URL using an external tool (ReqBin and Postman). The error still occurs. This confirms the issue is on the n8n side and is not related to the original client (Forminator) sending the data.

My Environment:

  • n8n Version: 1.107.4
  • Database you’re using (e.g., SQLite, Postgres): postgresdb
  • n8n EXECUTIONS_PROCESS setting (if you know it): main
  • Running n8n via: railway
  • Operating System: Linux (on Railway)

Troubleshooting Steps Already Taken:

I have already tried the following without any success:

  • Deactivating and reactivating the workflow.
  • Deleting the webhook node and creating a new one (which generates a new URL).
  • Creating a completely new, blank workflow with just one webhook node.
  • Restarting my entire n8n instance (using docker-compose restart for my self-hosted setup).

Since the error happens even with a direct POST request from a clean source and persists after recreating the workflow, it feels like an issue with my n8n environment or installation.

Has anyone encountered this specific error at the trigger level before? Are there any deeper logs I can check or environment variables that might be causing this?

Thanks in advance for any suggestions!

Hi there, just making sure, you already setup your WEBHOOK_URL env value and it’s the same with what you see on the webhook url in the n8n display, correct?

Yes, I’ve already set the WEBHOOK_URL environment variable and it matches exactly with the webhook URL shown in the n8n UI. I’ve double-checked it, but the issue still persists. Could you help me identify what else might be causing this?