HTTP + BASEROW | I'm completely stuck

Questions
1

Hi
I’m having a problem with the HTTP node and Baserow.

I’ve deployed n8n locally, and also deployed a Docker desktop and BaseRow locally.

My workflow is as follows: I enter text manually, creating a “on form submisson” for this. Then it sends it to HTTP for conversion to audio (mp3). TTS Edge converte it, and there are no problems at this stage. I now have my mp3 file, and I can listen to and download it.

2
22472×1168 136 KB

4
4499×897 35.4 KB

5
5518×1133 62.8 KB

The next step is to transfer information about this file via HTTP, including creating the URL for this file, the file name, and so on.

I’ve added credentials from my local BaseRow, and that’s fine too.

But then I encounter a 400 error, which states: “The request contains invalid values, or the JSON could not be parsed.”

6
62519×1187 159 KB

8
8514×872 48.5 KB

And that’s where the problem lies…

It turns out that the first HTTP node is transferring data about the element, but the second HTTP node can’t parse it.

As I understand it, in addition to the JSON file, information about the MP3 file should be transferred along with these elements, but it’s interpreting the second HTTP incorrectly because it doesn’t create a URL, and I can’t transfer this data to my base table.

Has anyone encountered a similar problem? How can I solve it?
I really appreciate your help. I spent the day yesterday trying to figure this out, but to no avail.

I’ll add screenshots of my nodes to this thread. Thank you.

2

Screenshot_20251117_143531_w8JulVzQ@2x
Screenshot_20251117_143531_w8JulVzQ@2x1734×1348 455 KB

Put the wrong name in the field

If your binary is speech.mp3

You need to put speech.mp3 in that field.

3

Thanks for this answer but..

Are you sure?
I thought it was supposed to be filled out like this?

1
11543×1090 106 KB

4

Yeah my screenshot is copy from yours

So after you chagne to speech.mp3.

Did you get the same error or another error?

5

The 400 Bad Request error only happens when I set:

  • Name: file
  • Input Data Field Name: speech.mp3

However, when I use the configuration you suggested:

  • Name: speech.mp3
  • Input Data Field Name: empty(or any other)
    I get a different, internal n8n error: Cannot read properties of undefined (reading 'value').
6

According to this post :

Input Data Field Name should be the orange text - the binary field name from your previous node (e.g., data, speech.mp3, or whatever is shown in the Binary tab).

If in your case is not working, maybe change the actual name of output from form to something else than speech.mp3 since the extension is mpga anyway… and maybe it’s a conflict, or where do you upload it it requires specific format… :thinking:

7

what do you mean by Input Data Field Name: empty(or any other)

Can you share another full screen when this happen?

8

Thanks to everyone who responded. I figured out the problem was that I was running my workflow on a local computer.

After many errors, I decided to run it on a VPS and everything worked. I’m thrilled and overjoyed.

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.