Issue with webhook 'POST' node receiving multipart/form-data

[FlinnBella]

Describe the problem/error/question

• The issue I’m running into is when I post multipart form data to my node, the webhook immediately returns a 200 response and does not execute the rest of the code - so the webhook node is ‘green’, but the rest dosen’t execute

What is the error message (if any)?

• There is no error message when it executes. But, my form uploads an image and a prompt, and whenver I try to - with the pinned image data - use the Analyze Node to parse the image, I sometimes get an error message about ‘image’ field dosen’t exist. The problem with this is that regardless of if I set the image field or not in the webhook node and multipart form-data for the binray image this error still occurs, only sometimes when I tweak it slightly does it work however it breaks again on the next request.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):

• Operating system:
  

[mohamed3nan]

Hi @FlinnBella welcome to the community!

I think you might have “On Error” set to >> Continue, so errors probably aren’t being triggered.

Please set it to the default “Stop Workflow” instead.

This way, you’ll be able to see any errors and decide how to handle them.

[jabbson]

@FlinnBella

whenver I try to - with the pinned image data - use the Analyze Node

pinning data does not preserve binaries

Please read the following note:

Nodes that output binary data
You can’t pin data if the output data includes binary data.

Source:
Data pinning | n8n Docs.

[FlinnBella]

Hey all; I already fixed it. Seemed to be an issue with test vs prod web hook endpoints. The error kept occurring when I was using the test endpoint, however largely resolved itself when I switch to the prod web hook endpoint. There were also some issues with the output json schema I had to correct. But the issue is largely resolved now; I’ve only tested for sending one image though.