N8N Integration failes in streaming mode

[amirali-lll]

Hello everybody. Thanks for developing these great integrations.

In n8n pipeline function I recive this error: "(Empty response received from N8N)"
It streams well and shows the streaming response. but at end it suddenly converts to "(Empty response received from N8N)"

IDK why, but the problem is also in summary, tags, and follow-up question generators. (They all don't work well in streaming mode)

I'm using the actual pipeline with no moderation, and the n8n workflow example provided in the pipeline's description with no moderation. I have removed the authentication section for testing purposes.
And it works well in the non-streaming version.

I use the latest version of this pipeline (v2.2.0)
My n8n version is v1.117.3
My openwebui is v0.6.34

Thanks a lot for your help

[owndev]

Hi @amirali-lll

Currently, N8N isn't sending any tool usage data in streaming mode, so it can't be displayed (see here).

Regarding the other issue with tags and follow-ups, etc., see here.

Tip

In short, use the non-streaming version of the pipeline to generate tags and follow-ups, and also use it if you want to display tool usage.

I hope this helps. 😊

[amirali-lll]

Thanks a lot.

[amirali-lll]

I can update the code to support both the streaming and non-streaming endpoints.
We can use the non-streaming endpoint for the title, tags, and summary, and the streaming endpoint for chats.
If that helps, it would be my pleasure!

[owndev]

The pipeline works automatically with streaming or non-streaming, depending on how the n8n workflow is configured.

The easiest way is to add the n8n pipeline twice, each with different settings. Use one for chats (streaming workflow in n8n) and the other for generating tags and follow-ups (non-streaming workflow in n8n).

You can find example workflows here.

[owndev]

Closing this, since the question about tags, titles and follow-ups is answered above.

n8n pipeline 2.3.1 (#182) also reworks how streamed replies are read. Open WebUI 0.11 reads a pipe's stream line by line, and several cases left an empty or broken answer:

• SSE framing leaked into the answer.
• UTF-8 characters split across network chunks were lost.
• Plain text arriving together with JSON was dropped.
• A streaming chat whose JSON reply contained usage was saved empty.

The recommendation above still applies: use a non-streaming workflow (a second pipeline instance) for tags, titles and follow-ups, because Open WebUI expects a complete answer for these tasks.

If you still get (Empty response received from N8N) with 2.3.1, please open an issue and include the n8n version and a sample of the raw response (Respond to Webhook node / streaming setting). Thanks!