# Serve a .txt file at a static https: URL

**URL:** <https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314>\
**Category:** FlowFuse\
**Created:** [8 October 2025 14:27 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314 "2025-10-08T14:27:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeremyCee](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jeremycee/32/103727_2.png) [@JeremyCee](https://discourse.nodered.org/u/JeremyCee)\
**Post date:** [8 October 2025 14:27 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/1 "2025-10-08T14:27:38Z")

</div>

We're hoping to leverage our FlowFuse instance as middleware between certain UIs and an ecommerce/payment gateway.

One of the providers needs us to "Verify" all of the domains that will be called out to in a transaction.

What would be the easiest way to serve a static .txt file @:

https://[our-account].flowfuse.cloud/.hidden-dir/my-domain-verification-key-file.txt

Is the .txt file store natively in our FlowFuse resources? Or does it need to be stored elsewhere and called into a Flow to serve up every time an http request comes in looking for it?

---

<div class="post-metadata">

**Author:** ![JeremyCee](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jeremycee/32/103727_2.png) [@JeremyCee](https://discourse.nodered.org/u/JeremyCee)\
**Post date:** [8 October 2025 15:48 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/2 "2025-10-08T15:48:19Z")

</div>

I've tried adding the .txt file to our Assets for the Instance, but I'm being prompted to upgrade our team, even though Persistent Files is shown as a feature in the Starter level services. Are we just not able to use the FlowFuse Asset Manager UI, but we can use a flow module to get the .txt file into the flow storage resource(s)?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [8 October 2025 16:18 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/3 "2025-10-08T16:18:16Z")

</div>

I have sent you a private message - lets see if we can get this resolved for you.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [8 October 2025 19:06 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/4 "2025-10-08T19:06:48Z")

</div>

Starter teams get file storage, they just don't get the extra tools to work with those files via the Forge Web app ("Assets").

You can still interact with files persistently using Node-RED, If you want to expose the file for HTTP access you will need to add it to your flow using the `http-in`/`http-response` pattern and a `file-read` node.

The file should be wrtten to a location under `/data/storage` but it doesn't need to match the path it is served on, you can just set the correct path in the `http-in` node.

To be honest you don't even need to use a file, the content of the text file can just be set to `msg.payload` in a `change` node between the `http-in` and `http-response` as long as the right route is in the `http-in` node

---

<div class="post-metadata">

**Author:** ![JeremyCee](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jeremycee/32/103727_2.png) [@JeremyCee](https://discourse.nodered.org/u/JeremyCee)\
**Post date:** [8 October 2025 20:05 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/5 "2025-10-08T20:05:15Z")

</div>

Thank you for the pointers, @hardillb and @Steve-Mcl

We successfully verified the URL by simply returning the txt contents and proper headers for the http request. We'll keep in mind we'd need to create our own UI/Dashboard interface if we're still on Starter tier and need non-technical users to manage files like Assets features allow.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [12 October 2025 20:06 UTC](https://discourse.nodered.org/t/serve-a-txt-file-at-a-static-https-url/99314/6 "2025-10-12T20:06:07Z")

</div>

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.