# 401 when setting up HTTP node in N8n

**URL:** https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105
**Category:** Technical Help
**Created:** [May 5, 2025, 10:13am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105 "2025-05-05T10:13:19Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![jesse\_m](https://community.baserow.io/letter_avatar_proxy/v4/letter/j/6f9a4e/32.png) [@jesse\_m](https://community.baserow.io/u/jesse_m)
#### Post date: [May 5, 2025, 10:13am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/1 "2025-05-05T10:13:19Z")

</div>

### Are you using our SaaS platform ([Baserow.io](http://Baserow.io)) or self-hosting Baserow?

SaaS

### What are the exact steps to reproduce this issue?

1. Configure the http node to get a field  
URL: [https://api.baserow.io/api/database/fields/4128607/](https://api.baserow.io/api/database/fields/4128607/)  
Value: Token mydatabasetoken

The token has been configured to have full access. I’m at a loss and have exhausted all AI troubleshooting.

### Attach screenshots, videos, or logs that demonstrate the issue.

 ![Screenshot 2025-05-04 at 9.36.26 AM.png](https://community.baserow.io/uploads/default/original/2X/8/8ba194244bf96077649439e9e90eac2447ad4494.png)

---

<div class="post-metadata">

### Author: ![frederikdc](https://community.baserow.io/user_avatar/community.baserow.io/frederikdc/32/2086_2.png) [@frederikdc](https://community.baserow.io/u/frederikdc)
#### Post date: [May 5, 2025, 10:55am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/2 "2025-05-05T10:55:40Z")

</div>

Hi,

Your setup seems correct at first sight. The HTTP node should look like this:

 ![image](https://community.baserow.io/uploads/default/original/2X/5/50402fcec4c4f6814998a3728005de2a2e166b71.png)

where the Header Auth account has the following information  
Name: Authorization  
Value: Token \<token\_to\_your\_database\>

 ![image](https://community.baserow.io/uploads/default/original/2X/7/7ae541e36b6f0deee117bc60de9f897fa093c645.png)

The only common mistake I can think of is that the Value is not preceded with the word `Token ` (make sure the space is also there).

If the problem still persists, I would recommend using a tool like postman to make the HTTP request to check if it is a problem specific to n8n or a problem with the request.

---

<div class="post-metadata">

### Author: ![jesse\_m](https://community.baserow.io/letter_avatar_proxy/v4/letter/j/6f9a4e/32.png) [@jesse\_m](https://community.baserow.io/u/jesse_m)
#### Post date: [May 5, 2025, 4:28pm UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/3 "2025-05-05T16:28:32Z")

</div>

There is a space between Token and the generated baserow token.

This seems to be an issue with the request and not an N8N.

When I tested on Webhook.site, as well as running a CURL test and I get the same results: “Authentication credentials were not provided.” I can clearly see them in this screenshot.

 ![Screenshot 2025-05-05 at 7.06.31 AM](https://community.baserow.io/uploads/default/original/2X/8/823c02bda6cf0ecd32faa70e3f6a9bd47b67c0d3.png)

---

<div class="post-metadata">

### Author: ![frederikdc](https://community.baserow.io/user_avatar/community.baserow.io/frederikdc/32/2086_2.png) [@frederikdc](https://community.baserow.io/u/frederikdc)
#### Post date: [May 5, 2025, 7:24pm UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/4 "2025-05-05T19:24:42Z")

</div>

So this http requests makes a call to webhook.site. But where do you make a call to the baserow API?

---

<div class="post-metadata">

### Author: ![jesse\_m](https://community.baserow.io/letter_avatar_proxy/v4/letter/j/6f9a4e/32.png) [@jesse\_m](https://community.baserow.io/u/jesse_m)
#### Post date: [May 6, 2025, 7:18am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/5 "2025-05-06T07:18:25Z")

</div>

Sorry about that. That was from one of the troubleshooting steps and I missed that detail. Here’s a screenshot from Postman testing the proper Baserow URL showing the 401 and this JSON:

{  
“detail”: “Authentication credentials were not provided.”  
}

 ![Screenshot 2025-05-05 at 1.11.55 PM](https://community.baserow.io/uploads/default/original/2X/e/e14f44fe34d557d0c52f846043e82dd0958cfa24.png)

---

<div class="post-metadata">

### Author: ![frederikdc](https://community.baserow.io/user_avatar/community.baserow.io/frederikdc/32/2086_2.png) [@frederikdc](https://community.baserow.io/u/frederikdc)
#### Post date: [May 6, 2025, 7:35am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/6 "2025-05-06T07:35:42Z")

</div>

Now that I see the url of the endpoint, I think the problem might be in that URL.

The endpoint [https://api.baserow.io/api/database/fields/{field\_id}/](https://api.baserow.io/api/redoc/#tag/Database-table-fields/operation/get_database_table_field) gets all the information for a single field. This is an action that requires a JWT token instead of a database token.

If you need all the fields for a table, you can use the endpoint [https://api.baserow.io/api/fields/table/{table\_id}](https://api.baserow.io/api/redoc/#tag/Database-table-fields/operation/list_database_table_fields)

If you need more information about working with JWT tokens, you can check this article on our blog: [How to authenticate to Baserow using web tokens](https://baserow.io/blog/authenticate-baserow-using-database-json-web-token)

---

<div class="post-metadata">

### Author: ![jesse\_m](https://community.baserow.io/letter_avatar_proxy/v4/letter/j/6f9a4e/32.png) [@jesse\_m](https://community.baserow.io/u/jesse_m)
#### Post date: [May 7, 2025, 1:10am UTC](https://community.baserow.io/t/401-when-setting-up-http-node-in-n8n/10105/7 "2025-05-07T01:10:21Z")

</div>

Thank you. That took care of the issue.
