n8n - 💡(How to fix) Fix Send mail and Wait node webhook resume URLs return 404 frontend SPA HTML instead of being processed by backend

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  • error: all

Root Cause

When using the Send Mail and Wait node in a workflow with webhook resume URLs, clicking the generated /webhook-waiting/ URL does not resume the execution. Instead, the n8n server returns a 200 OK response with Content-Type: text/html, serving the frontend Vue.js SPA. The SPA's Vue Router then renders a 404 page because it doesn't recognize /webhook-waiting/ as a frontend route.

RAW_BUFFERClick to expand / collapse

Bug Description

When using the Send Mail and Wait node in a workflow with webhook resume URLs, clicking the generated /webhook-waiting/ URL does not resume the execution. Instead, the n8n server returns a 200 OK response with Content-Type: text/html, serving the frontend Vue.js SPA. The SPA's Vue Router then renders a 404 page because it doesn't recognize /webhook-waiting/ as a frontend route.

The backend webhook handler never processes the request — it falls through to the catch-all that serves index.html.

<img width="421" height="431" alt="Image" src="https://github.com/user-attachments/assets/eef4602e-bb57-485f-ba4d-fae746025e53" /> <img width="1257" height="125" alt="Image" src="https://github.com/user-attachments/assets/7f7930e5-5830-44f9-bc35-2f00d88581fa" />

To Reproduce

  1. Create a workflow with a Wait node configured to resume on webhook call
  2. Trigger the workflow so it reaches the Wait node (execution status shows "Waiting")
  3. Copy the generated resume URL (format: /webhook-waiting/{executionId}/{nodeId}?approved=true&signature=...)
  4. Open the URL in a browser
  5. Instead of resuming the workflow, the n8n editor UI loads and shows a 404 page

Expected behavior

The /webhook-waiting/ URL should be intercepted by n8n's backend server, match the waiting execution, and resume the workflow. The response should be an API response (JSON or redirect), not the frontend HTML.

Actual behavior

The backend does not handle the route. The server responds with 200 OK and the full SPA HTML (index.html). The waiting execution is never resumed.

Both URL formats were tested with identical results:

/webhook-waiting/{executionId}/{nodeId}?params → SPA HTML /webhook-waiting/{nodeId}?params → SPA HTML

Debug Info

Debug info

core

  • n8nVersion: 2.18.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (multi-main)
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 5649a6ee-2ae2-4c8e-af69-ca48ae36ed05

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: database

pruning

  • enabled: false

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-08T06:25:59.834Z

Operating System

Windows

n8n Version

2.18.4

Node.js Version

24.14.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The /webhook-waiting/ URL should be intercepted by n8n's backend server, match the waiting execution, and resume the workflow. The response should be an API response (JSON or redirect), not the frontend HTML.

Actual behavior

The backend does not handle the route. The server responds with 200 OK and the full SPA HTML (index.html). The waiting execution is never resumed.

Both URL formats were tested with identical results:

/webhook-waiting/{executionId}/{nodeId}?params → SPA HTML /webhook-waiting/{nodeId}?params → SPA HTML

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Send mail and Wait node webhook resume URLs return 404 frontend SPA HTML instead of being processed by backend