I have copied my Hugging face acess token to the n8n credentials but when i save the api key it shows the below message in the screen shot. also i am sharing the error it shows when i run the workflow with Hugging face llm model.
## Information on your n8n setup
- **n8n version:** 1.89.2
- **Database (default: SQLite):**
- **n8n EXECUTIONS_PROCESS setting (default: own, main):** own
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** self hosted via docker in my personal computer
- **Operating system:** linux

I am having the exact same issue. It was working on April 30th, immediately after no luck. I tried generating 5 new keys with varying permissions to no avail. I have also tried running curl commands with my key which are successful, so i know my token is not the problem.
Best I can guess is that there was an update on either n8n or Hugging Face side, and the endpoint it is hitting is no longer valid. However, n8n gives us no way to see what we are hitting, therefore we cannot troubleshoot. Hopefully someone can come up with a solution!
I am self hosting locally without Docker, and have also tried cloud, to no avail. This proves that no matter which method of hosting n8n you are running, the issue persists. I believe this is on n8n and the way they are handling their credentials specifically for Hugging Face
As you mentioned your api key was working with curl command can you share the command ? . i am recieving a no found error with curl i believe there is an error from the api url.
Thanks mate appreciate your reply , will implement this soon and let you know how it went . Also with your setup will i be able to use any model listed in hugging face ?