Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:
Problem in node ‘HTTP Request‘
I am new to n8n with very limited coding experience. I have started working on the level one course. The very first step is setting up an http node for a n8n internal-course database. I have been having a greate deal of difficultly.
I have very carefully followed the instruction many times. I now am getting this error message:
Problem in node ‘HTTP Request‘
Forbidden - perhaps check your credentials?
I also discovered when I entered my api_key value in the credentials, it is not saved correctly, it shows as:
The value __n8n_BLANK_VALUE_e5362baf-c777-4d57-a609-6eaf1f9e87f6 is just what gets echoed into the field to prevent exposing the actual secret value. If you are seeing it, you might have switched that field in the credentials item from fixed to expression. If that’s the case, try switching it back and re-entering your key.
Thanks for the quick reply, I really appreciate it!!! Using “fixed” the node executed correctly, but the output says "
“message”:
“you must specify a unique_id header and value.” Is this an error, or do I simply need to connect another node to the http node output (e.g., AirTable)?
I think the point of the course is to work through those kinds of issues. IMO, the issue with expression values in credentials items is an unusual mistake where the n8n UI could be improved, so it doesn’t seem as counter-productive to help someone get past that. It would probably be better now to re-read the course instructions to see what you might have missed.
I receive the same message when executing the step. Getting data from the data warehouse | n8n Docs says you should see the table output, but it’s only the message. I double checked everything, but I’m 100% sure my node is configured right.
Unfortunately the workflow can’t be completed as it relies on data from the dataset URL.
Update - it works for me now.
I switched “Specify Headers” to “Using JSON”, provided “unique_id” in JSON format and it worked. Switching back to “Using Fields Below” it kept working…