Header Auth Failure in webhook has me stumped

[Andre_Pemmelaar]

I am trying to use a header auth for a webhook and am testing with Postman.
I constantly get a ‘Authorization data is wrong!’ error
I have checked my Header Auth credentials and they seem correct. To eliminate the possibility of a typo I reduced them to ‘Bearer 12345’. Screenshots of postman and node are below.

Using ChatGPT to helo didn’t find the problem. Kinda stumped on what to check.

Here are screenshots of the node and Postman

Information on your n8n setup

• 1.62.5, version
• n8n cloud
• MAc notebook

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Andre_Pemmelaar]

@Andre_Pemmelaar

## Information on your n8n setup
- 1.62.5, version
- n8n cloud
- MAc notebook

Information on your n8n setup

• n8n version: 1.62.5,
• Database (default: SQLite): None used in the flow so default
• n8n EXECUTIONS_PROCESS setting (default: own, main): Default
• Running n8n via n8n cloud,
• Operating system: MAcOS Sonoma 14.6.1

[ihortom]

Welcome to the community @Andre_Pemmelaar !

Tip for sharing information

Pasting your n8n workflow

---

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!

---

That is really not the expected result. Do you get the same in both modes - Test and Production? Did you happen to try any other Authorization headers in addition to Bearer?

[slinkytoad]

I was having this same issue in 1.64.4. I removed the auth, and it works. I also tried creating a new credential and using it, but had the same issues. Next step for me was to recreate the workflow and try it.