Header/Credential Question

Greetings Everyone,

I have really been enjoying the courses introducing n8n and have become very comfortable over the last few days. Its an awesome resource. This morning, I began creating a workflow for the 102 course, but when I execute the gather data step, it says my header credentials:

Forbidden - perhaps check your credentials?
Authorization data is wrong!

These credentials worked yesterday and when I attempt to run previous workflows that I know work, they throw the same error. I also attempted to create new credentials from scratch using the lesson I was on, but this also had the same result. I know in these instances, its almost always new user error, but it feels like its something that might be happening on the n8n side., only because saved workflows that worked yesterday do not today.

Any assistance would be appreciated, if its something I can remedy in what I am doing, or if its something I need to wait to be fixed, I’d just be grateful for some help. Thanks!

From HTTP Request

Error code

403

Full message

403 - "Authorization data is wrong!"

Request

{ "headers": { "x-assessment-id": "159f9716d4caa3b44e65f52a41e8ac96", "**hidden**": "**hidden**", "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7" }, "method": "GET", "uri": "https://learn.app.n8n.cloud/webhook/course/n8n101/sales-data", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "sendCredentialsOnCrossOriginRedirect": false, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }

Hey @Lifecer, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@Parintele_Damaskin, @A_A4, @jabbson - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

I think I resolved it, it seems that the different credentials were not interchangeable, at least mine were not, and then I think I messed something up as well. Lesson for me I think is I will always create new credentials for a new class even if it tells me I don’t need to. I think the good workflows not working were a result of the linked credential system, I basically messed them up retroactively lol. Glad I could work it out on here smh. Sorry for taking up anyone’s time!

Since old workflows fail too, I’d suspect the API key or token on the other end rather than n8n. Many course and demo APIs use keys that expire or reset daily. Test the same request in a tool like curl or Postman with the same header. If that also fails, regenerate the key and paste it into the credential fresh, watching for stray spaces.