I am using Files API to upload self-contained html file(s) to fibery. I have the link of the file and I am able to store the link in a rich text field. However, when I click on the link, the html gets downloaded and is not rendered. My question is:
-
Is there a way to upload files that render in browser instead of downloading?
-
Can we access the same content storage mechanism that AI automation uses? I have seen that AI automation can create web pages that are accessible through links of type https://{customer_name}.fibery.io/api/ai-answer/page/{id} . Those are directly rendered in the browser, not downloaded - this is the behavior that I want for my files as well.
-
Are there plans to add content-type control to file uploads?
I bet something can be done rather fast. Can you describe your use case? What is the best desired flow?
Here is our usecase:
We programmatically generate company dashboards from Fibery and other data sources as standalone, self-contained HTML files.
We want these dashboards to live directly within Fibery spaces, close to the data they represent. Since we consider Fibery our “company OS,” it makes sense to keep everything centralized rather than hosting dashboards elsewhere.
External hosting would complicate permission management and goes against our principle of having one centralized location for company data.
A way to upload HTML files to Fibery that render directly in the browser would give us the best of both worlds: programmatically generated dashboards that live natively within Fibery’s ecosystem.