Add option to customize User-Agent in WordPress credentials

Feature Requests
1

The idea is:

To allow customization of the User-Agent header in the WordPress credentials node.

Currently, the User-Agent is hardcoded to n8n, which causes issues with some hosting providers that block requests based on this header.

My use case:

I’m using n8n to automate workflows involving my WordPress site hosted on IONOS.

Unfortunately, any API call from n8n with User-Agent: n8n is blocked by their infrastructure, returning a generic “temporarily unavailable” error.

The same request works perfectly if I change the User-Agent to curl or Mozilla/5.0.

I think it would be beneficial to add this because:

It would allow users to interact with WordPress APIs hosted on restrictive platforms.

Without this, the WordPress credentials integration becomes unusable in certain hosting environments — and there’s currently no workaround other than rewriting requests using the generic HTTP Request node.

Any resources to support this?

This issue is documented with packet captures and tested manually via curl.
I’ve also contacted IONOS support, who confirmed they likely filter requests based on the User-Agent string.

Are you willing to work on this?

I cannot contribute directly to the codebase, but I can help with testing and provide detailed technical examples if needed.

2

we see that also as very beneficial. In our case we need it for the Odoo node.
So I would like to see a global setting to set the user-agent as config object, or as a default setting for any node that is using HTTP

3

Ugh… been banging my head against this for a couple of days with ionos support. Just got through with them again. Maybe they’ll do something on there end. For now though, it seems like I’ll have no choice but to use other nodes like http or code or whatever to try to accomplish my goals. I’d maybe leave ionos, but I’ve already got so much set up there.

Annoying. Will watch this thread a bit to see if any updates to make this easier.

4

Hi, how can i change the User-Agent to curl or Mozilla/5.0?