I am having a problem with the HTTP node.
I have an API that is supposed to send me a file attachment when the “accept” header is set to “text/csv” or “application/vnd.ms-excel”.
using postman, I am able to make the correct call no problem.
But I have been unable to make n8n do it, because the “reponse format” option in the http node ALWAYS adds it’s own additional “accept” parameters, even when I specific a custom accept header.
The problem is that the api sees something like this for “accept” as a result:
The end result is that the API doesn’t realize I want the file, and it just sends the typical JSON payload instead, which is not helpful.
For it to work, the accept header can only have this value:
Any additonal data in the accept header and it won’t work.
We need an option on the HTTP node response type that is like “raw” or something, where it sends NOTHING else to the API, including content types, accept, etc…
The typical “raw” switch doesn’t disable these headers.
This is a blocking problem preventing me from migrating from integromat, as I have to be able to get these downloads from the API.
I’ve diagnosed this using webhook analysis tools (webhook.site in this case), vs postman, and this is the only explanation for this failure.
If I was up to speed I would try to fix this myself, but I’m not there yet.