Https://learn.app.n8n.cloud/webhook/course/n8n101/sales-data is not returning any data

n8n Academy N8N101: Essentials: Your First Workflows
1

I am in the Hands-on Exercise: Building a Sales Data Pipeline and when I run the HTTP Request node, I am not getting any data. The node JSON can be found below:

{
"nodes": [
{
"parameters": {
"url": "https://learn.app.n8n.cloud/webhook/course/n8n101/sales-data",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "X-Assessment-ID",
"value": "<REDACTED>"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.4,
"position": [
-112,
64
],
"id": "1a209724-06df-439d-8872-d29bf8743726",
"name": "GetSalesData",
"credentials": {
"httpHeaderAuth": {
"id": "<REDACTED>",
"name": "n8n Academy API Key"
}
}
}
],
"connections": {
"GetSalesData": {
"main": [
]
}
},
"pinData": {},
"meta": {
"instanceId": "9ada57fb1a430627eb39b960d62fc78438bc7f8c87e1fd6302fa222179d1fd9e"
}
}

Is it just me or is there an issue with that endpoint?

2

Hello,

There were some issues last night with the APIs. Can you please try again.

cheers,

3

Thanks for following up. I can confirm it is working now.

4

Looking at the JSON you pasted, your connections block is empty:

connections": { “GetSalesData”: { “main”: [] } }

So GetSalesData isn’t wired to anything — nothing feeds in, nothing comes out. That’s why there’s no data even though your URL and auth header both look fine.

This one catches a lot of people because the node looks completely normal on the canvas. I’ve lost time to it myself — you hit Execute step, the node runs, no error, and the output panel is just empty, so you start suspecting the endpoint or your credentials when the request was never really the problem.

Two things to try:

  1. Drag a connection from your trigger into GetSalesData so it has an input, then run the whole workflow rather than the node alone.
  2. To test that node by itself, open it and use Execute step inside the node — but in a normal run it still needs something upstream to fire it.

If it’s still empty after that, check the JSON tab in the output panel rather than the table view. A single-object response sometimes looks blank in the table but is clearly there in the JSON.

And worth confirming the header name is exactly X-Assessment-ID — that endpoint returns an empty body rather than a 401 when the header is missing or misspelled, which looks identical to “no data” from inside n8n.