When reviewing executions using any http node with predefined credentials, the execution is showing a warning telling me that the credentials for the service are not set.
That is not a real error, since the execution was successfully, but the warning icon and message create a false positive that is bogging me.
What is going on? I also tried to create new credentials, but the warning is there anyway.
Yes, I created and use different credentials with a different API key from the service (brevo in this case, but that is happening with WordPress and WooCommerce, too). Same behaviour.
@giacomolanzi yeah this is a cosmetic display bug that shows up specifically when using predefined credentials with the generic HTTP node — the execution ran fine, the warning is a false positive from how n8n logs credential references in that context. no actual auth issue.
if it’s bothering you: switching to the native Brevo/WooCommerce/WordPress node (instead of HTTP node) usually eliminates it since those nodes handle credential logging differently. if you need to stick with HTTP node, it’s safe to ignore — the execution result is the ground truth here.
@barn4k fair point — if the Predefined Credential Type is configured correctly in the HTTP node’s auth tab, the warning shouldn’t show. @giacomolanzi sharing a screenshot of the auth settings would help confirm whether it’s a setup issue or something else going on.
Sure, here it is a screenshot from one of the latest execution of a scenario made to show the problem (that is happening with every http node with predefined credentials type):
I am sure the credentials are set correctly because I am using the query param ‘context=edit’ which require correct credentials.
Also, this issue is happening with other services, too, when used with a generic request node. For example, I go the same warning with Brevo, as mentioned in the first post in this thread.
As said: the action is performed, but I got that warning that is annoying since when I open an execution, I am not sure if there is a issue or it’s just a false positive.
Just to add context: I already tried to create a new credentials for the same services. I got the same problem.
@barn4k good catch — the config screenshot will definitively tell us whether it’s a setup issue or the cosmetic bug we identified earlier. the fact that execution succeeds (no auth failure) but the warning shows suggests the credential is set, but let’s confirm through the UI to rule out any edge cases with how predefined types get logged.
@giacomolanzi yeah that confirms it — credentials are set and the auth type matches. this is just the display bug with how n8n logs predefined credential types on the http node, not an actual issue. if you want it fixed upstream, might be worth opening a github issue since the repro is consistent across multiple services
Try updating the HTTP node to the latest version. You will need to open the node panel on the right, search for the HTTP node and place it on the canvas. In the settings page you will se the actual node version.
@barn4k good point — @giacomolanzi that’s worth trying. if you’re on an older typeVersion of the HTTP node, swapping it out for the latest might fix the credential display logging. worth testing quickly before going the GitHub issue route.
Thank you for the suggestion, but I was pretty sure the node was at its latest version, since I created a workflow just to test it and show it to the community.
Anyway, I gave it a try and I got same results:
The workflow is executed correctly, but when the execution is displayed in the executions’ tab, there is a warning in the http module.
Here is the workflow once again, maybe you see something I don’t:
you’ve got consistent repro across multiple typeVersions and services — that’s exactly what the GitHub issue needs to get traction. good work documenting it with screenshots. let’s see what the team says.
