AI Agent HTTP Request Node treats custom json content-type declarations as binary

[grandfso]

Bug Description

#11219
The above commit introduces a bug where if an API responds with custom content type, e.g. application/custom+json;version=2.1 to complain

{
“response”: “There was an error: “Binary data is not supported””
}

While the returned data is a valid json, the data is not passed back to the agent.

The default (non agentic) HTTP Request node works fine with such responses.

Downgrading to 1.63.4 also makes the Agentic HTTP Request node works with such responses.

To Reproduce

Using (agentic) HTTP Request node, call an API that returns valid json with custom content-type declaration.

Expected behavior

Should allow the user to either ignore the warning about binary data and pass the response to the agent, or be more relaxed with custom type declarations filtering.
Or, better yet, when user specifies the Accept header in the request, that content type should be allowed in the response.

Operating System

Docker

n8n Version

1.74.3 (any from 1.64 onward)

Node.js Version

dunno

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @grandfso,

We have created an internal ticket to look into this which we will be tracking as "N8N-8168"