Hi community,
I’m facing a very strange issue with a two-part webhook workflow on n8n Cloud. I’d be grateful for any ideas.
My Goal:
I have a workflow to create Salesforce records from a PDF, with a manual duplicate check step for the user.
The Architecture:
- Workflow A: A web form POSTs a file. The workflow uses AI to extract data and searches Salesforce for duplicates.
- If a potential duplicate is found, Workflow A responds with an HTML “Confirmation Page”.
- This page has a form with two buttons (“Log as Duplicate” / “Create New Record”). The form POSTs the user’s decision to a second webhook, which triggers Workflow B.
- Workflow B: Receives the user’s decision, performs the final action in Salesforce, and should respond with a final “Success” or “Logged” page.
The Problem:
When a user clicks a button on the “Confirmation Page”, the POST request to Workflow B is sent.
- In the n8n Executions log, Workflow B completes successfully.
- In the browser’s Network DevTools, the request to Workflow B’s webhook shows a
200 OKstatus. - However, the browser itself does not render the response. It shows a blank white page or a generic browser error like “Connection Refused”.
What I’ve Ruled Out:
- Workflow Error: The n8n execution log is green (successful).
- Browser Cache: The issue persists even after a hard refresh (
Ctrl+Shift+R). - HTML Content Error: The issue still happens even if the final
Respond to Webhooknode sends a minimal HTML page like<h1>OK</h1>. favicon.icoError: The request forfavicon.icoalso returns a200 OK.- Testing Environment: I am using the Production URL in a separate, normal browser tab (not the n8n editor preview).
My Question:
Has anyone encountered this behavior where a successful 200 OK from a Respond to Webhook node fails to render in the browser? Could this be a specific security policy from n8n Cloud, or am I missing something else?
Details:
- n8n Version: 1.108.1 (Cloud)
- Database: Default
- Running n8n via: n8n Cloud
Thank you for your help!

