Uploading a created file to S3

Questions
1

Describe the problem/error/question

Can’t figure out how to upload a file I just created to S3

Monosnap Image 2023-08-28 15-34-37
Monosnap Image 2023-08-28 15-34-37921×811 48.2 KB

The file is there but I don’t see any way to just say “the file from the previous node, upload that”. Have tried every combination I can think of but nothing has worked.

Information on your n8n setup

  • n8n version: 1.x
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): In out K8 cluster
  • Operating system: Linux
2

Hi @zenweasel :wave: Tried this out just now, and was able to upload a file just fine to a test bucket:

I’m noticing that you may not have a binary property set on your file, just judging by the preview, but you’re calling data. Can you make sure these properties match? :+1:

3

Yeah I threw away the “Create Binary File” node as it doesn’t seem like this works. I added a new node that just creates a payload with a binary value and that seemed to work.

What you are doing there is definitely not the same as what I am doing.

1 Like
4

Glad to hear you got this working - if you can share your workflow with a reproducible example of what was happening to you where this wasn’t working for you, we can look further into this.

5

To be clear I don’t think something is wrong with n8n, I just think it’s a matter of getting the output of the previous node to match what the AWS S3 node expects and I could not get the JSON to Binary to create something that would go directly into S3 which does not expect a file object like you see in my screenshot which does not seem to have a “binary” property. Again I am sure this is user error not a problem with n8n. The snippet that I used that worked in a code node was

items[0].binary = {
  data: {
    data: new Buffer(items[0].json.fileData).toString('base64')
  }
};
return items;

That seemed to satisfy that S3 node where the JSON to Binary did not. I tried changing the binary property parameter on the AWS S3 module to all sort of things but nothing seemed to work for me.

Hope I explained that clearly enough.

1 Like