I’m working through the n8n Quickstart course, Generating Reports workflow (Part 1: Retrieving order data), and I’m blocked by an unstable error on the company-data webhook. What’s happening:
The GetOrderData HTTP Request node (GET https://learn.app.n8n.cloud/webhook/courses/n8n-quickstart/company-data) has returned three different errors over the course of troubleshooting:
Forbidden - perhaps check your credentials? / Authorization data is wrong!
The resource you are requesting could not be found / Active version not found for workflow with id “aXsHqpRntXDZOZ2t”
Back to error #1 (Forbidden / Authorization data is wrong!) What I’ve already checked/ruled out:
Recreated the Header Auth credential from scratch with a freshly copied x-assessment-id from my course profile page
Confirmed the value is set to “Fixed” (not Expression) and matches my current assessment ID exactly
Confirmed the URL matches the course instructions exactly (no typos, no trailing characters)
Removed unrelated extra headers
The fact that the error type changes between attempts (auth error → resource/workflow error → auth error again) suggests this is an intermittent issue on the platform side rather than something in my node configuration.
Has anyone else seen this alternating behavior, or is there a known fix in progress?
Tried both Header Auth and Custom Auth credential types with a freshly copied assessment ID — same result both ways:
Forbidden - perhaps check your credentials?
Authorization data is wrong!
Also confirmed no duplicate/empty headers are being sent alongside the credential (turned off “Send Headers” entirely when using Custom Auth, so only the credential’s header goes through).
This rules out a credential-type-specific formatting issue on my end. Combined with the earlier “Active version not found for workflow” error I saw in between attempts, this really looks like something intermittent on the platform side rather than my configuration.
Still stuck — anyone know if there’s a fix in progress, or should I open a separate Help ticket at this point?
@kjooleng Thanks for confirming your config works! Mine is set up identically (Header Auth, Send Headers on, same field structure) and I’ve triple-checked my assessment ID matches my profile exactly — but I’m still getting “Forbidden - Authorization data is wrong!” every time.
Did you run into this error at some point before it started working? Or was it working for you from the start? Trying to figure out if this is something that resolves itself after a delay, or if I need to escalate to Help directly.
Thanks for the test! Tried your ID (7ef5d6a6ebbc2c02fcf9ea1155fa8514) in my exact same setup — still getting the identical “Forbidden - Authorization data is wrong!” error.
This actually rules out the Assessment ID being the problem, since your working ID fails the same way in my environment. So it’s something specific to my account/session/instance, not the ID itself. Might be worth flagging to n8n support as a possible account-level or IP-level block on this specific webhook.
Hi @Virus
The endpoint needs two headers, X-API-KEY and x-assessment-id, and only the first one belongs in the credential. The course sets the Header Auth credential to Name X-API-KEY with your Academy API key as the value, then sends x-assessment-id from the node itself under Send Headers > Using Fields Below.
Every setup described in this thread sends the assessment ID and no API key, so the 403 holds no matter whose ID goes in. Set the credential Name back to X-API-KEY with your Academy API key, turn Send Headers on, and add x-assessment-id there with your own ID.
See this:
