Error uploading binary file with Form-Data: Cannot read properties of null (reading 'name')

[leesilverman]

Bug Description

Trying to upload files using HTTP request node / Body Parameters / Parameter type n8n Binary File.

I am as positive as I can be that I'm including the parameter name and the attachment data field name, but I'm getting the error "Cannot read properties of null (reading 'name')". I'm pretty sure the "Name" field is for the parameter name, but it also fails if I put the filename there. I've included both versions in my example workflow.

It's certainly possible I'm doing something wrong, but if so I think the documentation or tooltips should be updated because I think I'm doing the obvious things.

To Reproduce

Use this workflow to try to submit one or two attachments.

{
"nodes": [
{
"parameters": {
"formTitle": "15/10 Open a Support Ticket",
"formDescription": "Use this form to create a support ticket for 15/10",
"formFields": {
"values": [
{
"fieldLabel": "Attachments (optional)",
"fieldType": "file"
}
]
},
"responseMode": "lastNode",
"options": {
"buttonLabel": "Create Ticket"
}
},
"type": "n8n-nodes-base.formTrigger",
"typeVersion": 2.2,
"position": [
-880,
-928
],
"id": "1c9754be-1eb1-4240-b95a-251035dfd5ba",
"name": "On form submission1",
"webhookId": "bea8b17a-471a-400a-bbdc-c03e8c9e1edb"
},
{
"parameters": {
"method": "POST",
"url": "https://www.postb.in/1754743904955-1335371448658",
"sendBody": true,
"contentType": "multipart-form-data",
"bodyParameters": {
"parameters": [
{
"parameterType": "formBinaryData",
"name": "={{ $json.attachment.filename }}",
"inputDataFieldName": "={{ $json.attachment.attachment }}"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
144,
-1152
],
"id": "e7c24c96-be12-4c81-9fd0-8d756c501372",
"name": "Upload Attachments & get IDs1",
"onError": "continueErrorOutput"
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "0bdb98d6-ea0a-4277-84aa-ba4af9831a8b",
"name": "attachments",
"value": "={{ Object.keys($binary).map(b => Object({attachment: b, filename: $binary[b].fileName})) }}",
"type": "array"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
-512,
-1120
],
"id": "a1efb8c7-98ef-40a7-8333-2978d2377b3d",
"name": "attachment names array1"
},
{
"parameters": {
"fieldToSplitOut": "attachments",
"options": {
"destinationFieldName": "attachment"
}
},
"type": "n8n-nodes-base.splitOut",
"typeVersion": 1,
"position": [
-304,
-1120
],
"id": "b7a38d28-e4c4-405e-ac86-a3302ed6fa53",
"name": "Split Out1"
},
{
"parameters": {
"mode": "combine",
"combineBy": "combineAll",
"options": {}
},
"type": "n8n-nodes-base.merge",
"typeVersion": 3.2,
"position": [
-112,
-944
],
"id": "e8898a71-436a-4f0d-860c-ce592e9abfe8",
"name": "Merge1"
},
{
"parameters": {
"method": "POST",
"url": "https://www.postb.in/1754743904955-1335371448658",
"sendBody": true,
"contentType": "multipart-form-data",
"bodyParameters": {
"parameters": [
{
"parameterType": "formBinaryData",
"name": "file",
"inputDataFieldName": "={{ $json.attachment.attachment }}"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
144,
-944
],
"id": "31afec08-50fd-4421-8cb8-5f8c7aa7cb37",
"name": "Upload Attachments & get IDs2"
}
],
"connections": {
"On form submission1": {
"main": [
[
{
"node": "attachment names array1",
"type": "main",
"index": 0
},
{
"node": "Merge1",
"type": "main",
"index": 1
}
]
]
},
"attachment names array1": {
"main": [
[
{
"node": "Split Out1",
"type": "main",
"index": 0
}
]
]
},
"Split Out1": {
"main": [
[
{
"node": "Merge1",
"type": "main",
"index": 0
}
]
]
},
"Merge1": {
"main": [
[
{
"node": "Upload Attachments & get IDs2",
"type": "main",
"index": 0
},
{
"node": "Upload Attachments & get IDs1",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"meta": {
"instanceId": "56a3b6e808c84fdadd2d80585289500a7b27625c2792fc6c214518fe7ce0a003"
}
}

Expected behavior

The file should be uploaded using the parameter "file"

Debug Info

Debug info

core

• n8nVersion: 1.105.3
• platform: npm
• nodeJsVersion: 22.18.0
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: 6c524f2d-042e-4067-92e4-c47a67b81372

storage

• success: all
• error: all
• progress: true
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 360 hours
• maxCount: 50000 executions

client

• userAgent: mozilla/5.0 (x11; linux x86_64) applewebkit/537.36 (khtml, like gecko) chrome/139.0.0.0 safari/537.36
• isTouchDevice: false

security

• secureCookie: false

Generated at: 2025-08-09T13:11:36.287Z

Operating System

Amazon Linux 2023 latest release

n8n Version

1.105.3

Node.js Version

22.18.0

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

[Joffcom]

Hey @leesilverman,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-3636".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[zhyd1997]

Hi all, first time using n8n, it's very cool for setting up workflows. 🚀

Just wondering — if you change the Body Content Type to n8n Binary File directly, does it work for you?

CleanShot.2025-08-11.at.14.48.39.mp4

[leesilverman]

@zhyd1997 Not with the application I'm trying to upload to. The specific endpoint I'm trying to use is https://supportcandy.net/docs/attachments/, which requires me to upload the file to a parameter called "file". If I just put the file in the body of the post, the endpoint doesn't know what to do with it.

[leesilverman]

I'm using an AWS Lambda as a workaround for this - uploading the file to S3 and then using Axios to upload it to the endpoint. But that's a lot of work - it'd really be a lot easier if I could just do this with the HTTP module.

[n8n-assistant]

Hi @leesilverman 👋

Thanks so much for your patience while we’ve been improving n8n. We know it’s taken some time to review this issue, and we’re currently updating our triage process to better keep up with our growth.

There have been a lot of improvements in recent releases, so we’d really appreciate it if you could check whether this issue still occurs in the latest release.

When you have a moment, please copy and paste the checklist below as a comment so our system can update the status automatically:

[ ] I have updated to the latest stable version of n8n [please specify version number] and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

If we don’t hear from you in the next 14 days this issue will be automatically closed, feel free to reopen - don’t forget to add the checklist above so that our automated systems notify us of the issue.

Thanks again for helping us keep n8n healthy and up-to-date 💚

[spss20]

Facing same issue

If I run the same api without binary file upload, the api is successfull.

I'm on n8n Version 1.118.2

[n8n-assistant]

As we haven’t heard back from you, we’re going to close this issue to keep things organized. But don’t worry, if you have more information or need further assistance, you’re welcome to reopen the issue anytime or create a new one. We’re always happy to help!

Thanks for reaching out and have a great day! If this was closed by mistake and you have been waiting for us let me know and I can also re-open it.