I want to send multiple files using the attachment form data attribute. I have brought up this problem before, but in that topic, we could only pass one file. Now i have to send multiple files as a single attachment.
Kindly refer to the below topic for better understanding and to get the data:
I might be misunderstanding as your example workflow relies a lot on data that we can’t use to reproduce, but could you use a Split in Batches node here in order to upload the files one by one?
Hi @EmeraldHerald , Here is the code that I want to reproduce.
Here, I want to use Form-Data to send multiple images in one attribute of an attachment. The problem with this is that it only sends the image name, not the image’s file format.
Below is screenshot of my application , how it is visible when i am downloading the myFile.txt
Would this be closer to what you’re looking for, or perhaps put you on the right track? It’ll split your attachments into three separate files called data, and then try to upload the data (along with your other fields) through the HTTP request.
Hi @Farheen_I Can you try an expression like {{ $("mapping data").first(0, 0).json.data.custom_fields.depot_name }} (going by what’s in your screenshot), and seeing if that works?
Yeah ! Thank you, @EmeraldHerald, it worked. You are fantastic! :giggling
However, I am still in a bind because the attachment we send with the formdata does not update inside of a single array. Multiple tickets are created for each attachment, and each attachment is sent separately. It should proceed as follows:
Hi @Farheen_I - the HTTP node unfortunately wouldn’t support this in the way you’re looking for
A way to go about this would be to create the ticket in Freshservice previous to trying to upload an attachment (to avoid four separate tickets being created), and then update the single ticket with each attachment one by one as a workaround.
If this fails because Freshservice’s API does not allow for these four items to be uploaded to a single ticket individually, the only other workaround I can think of would be to zip these four attachments and upload that singular file. If you’re self-hosting n8n and you’re handy with cURL, you could also use the Execute Command node as a workaround, too.
I’ll move this over to the feature request section of our forums so that our product team gets their eyes on multiple attachments in a single field sent through one HTTP Request node request
It’ll split your attachments into three separate files called data, and then try to upload the data (along with your other fields) through the HTTP request.
