fix(core): Fix CORS issue in waiting webhook responses #23861
Merged
+189
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Shireen Missi <[email protected]> Co-authored-by: Michael Kret <[email protected]> Co-authored-by: Michael Kret <[email protected]>
RomanDavydchuk
approved these changes
Jan 5, 2026
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
n8n-assistant
bot
added
core
This comment has been minimized.
This comment has been minimized.
|
E2E Tests: n8n tests passed after 6m 53.6s Run Details
Groups
This message was posted automatically by
currents.dev | Integration Settings
|
Contributor
|
Got released with |
|
Any idea on when this fix will be available? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes an issue where Telegram “Send message and wait for response” custom forms remain stuck in a loading state after submission.
The backend correctly receives and processes the form data, but the frontend fails due to missing CORS headers on waiting webhook responses (especially when the request origin is "null").
This change ensures proper CORS headers are always sent for waiting webhooks, allowing the form to complete and render the submission confirmation page.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4141/community-issue-telegram-node-custom-form-passes-data-but-still-loads
Review / Merge checklist
release/backport(if the PR is an urgent fix that needs to be backported)