13 days ago
Subject: Webhook Trigger Not Receiving Data and Automation Failures After Initial Success
Description:
I have deployed my n8n instance on Railway. I use a webhook trigger node in n8n to receive form submissions from Typeform.
The main issues are:
Webhook Trigger Issue
The form submits successfully on the front end, and Railway logs show requests reaching my n8n endpoint.
In n8n, the execution starts but the webhook trigger node shows an error.
The workflow does not receive or display the submitted data in the execution log.
Downstream nodes fail because they have no input.
Automation Failure After Running Initially
When I create a new automation in n8n, it runs correctly at first.
After some time (without changes to the workflow), executions start failing.
This happens even if the same trigger and data source are used.
It suggests either a connection timeout, webhook URL invalidation, or background service suspension in Railway.
Steps to reproduce:
Deploy n8n on Railway.
Create a workflow starting with a webhook trigger node.
Connect Typeform to send submissions to the webhook URL.
Submit any entry in Typeform.
Observe:
Initially, the workflow executes correctly.
After some time, the same workflow begins failing at the trigger node, with no data passed to downstream nodes.
Expected behavior:
The webhook trigger node should consistently capture payloads from Typeform.
Automations should continue working over time without unexpected execution failures.
Actual behavior:
Webhook trigger often fails to capture data despite Railway confirming the request reaches the service.
Workflows that initially run correctly later fail without changes being made.
Environment:
n8n deployed on Railway
Webhook trigger node as workflow start
Typeform submissions as the source of webhook requests
Request:
Please confirm if Railway deployment settings, routing, SSL, or background process handling are causing the webhook connection to break or executions to fail after a period of inactivity.
1 Replies
13 days ago
Hey there! We've found the following might help you get unblocked faster:
🧵 n8n Docker Container Crashes on Railway with Volume-Mount Error
🧵 Issue with Persistent Volume Mount Causing "Error: Command 'start' not found" When Deploying n8n
If you find the answer from one of these, please let us know by solving the thread!