Unable to override request header in HTTP Request Node

Feature Requests
1

The idea is:

Allow user to override HTTP Request Node header.

My use case:

Notion API just release a new version. You may see here: Upgrade guide - Notion Docs

  • To upgrade to this version, we need to set the request header Notion-Version to 2025-09-03
  • I did try to specify Header myself, but the node somehow change mine to lower case while maintaining the original Notion-Version. See attached screenshot.

image
image1324×1003 116 KB

I think it would be beneficial to add this because:

HTTP Request Node should be generic enough for user to build according to their own needs. Having a hardcoded logic, for example, the Notion-Version header does not give the flexibility to user and thus preventing users to use an updated API with updated features etc.

Any resources to support this?

Upgrade guide - Notion Docs

Are you willing to work on this?

I am not technical enough to do so. Hope someone in the community can help. Thanks

2

Hey @StevenChong hope all is good.

From the error message, I see that the problem is actually the URL. See if this is because it has double slash in the middle:

image
image816×312 38.6 KB

إعجاب واحد (1)
3

Oh indeed. My bad for the typo.

I remove the additional / and the request sent successfully.

May I check how to see the request header sent? Dont seem to find a way to do it. Wanted to verify if the header is sent correctly.

The reason I asked is because, the response from Notion API does not have key “data_sources”, not sure if HTTP Node has sent the correct header or not. Or, it is a Notion API issue.

The expected output should be in this format (according to Notion Upgrading to 2025-09-03 )
{ “object”: “database”, “id”: “{database_id}”, “title”: [/* … */], “parent”: { “type”: “page_id”, “page_id”: “255104cd-477e-808c-b279-d39ab803a7d2” }, “is_inline”: false, “in_trash”: false, “created_time”: “2025-08-07T10:11:07.504-07:00”, “last_edited_time”: “2025-08-10T15:53:11.386-07:00”, “data_sources”: [ { “id”: “{data_source_id}”, “name”: “My Task Tracker” } ], “icon”: null, “cover”: null, // … }

The response I got has not data_sources.

4

To see the request headers, open a dev web console and execute the node.

إعجاب واحد (1)