ok! thank you!
Also a quick question regarding this feature 
Since you mentioned this is currently a prototype — do you plan to keep this functionality further in Fibery?
We’re asking because even at this stage it already works very well and allows us to solve quite a few real use cases. We’ve actually started building parts of our internal workflows on top of it.
So it would be very helpful to understand whether this is something we can rely on long-term as tool in Fibery in future? 
2 Likes
I had the same question
While we may change how pages are created, the pages themselves will stay.
5 Likes
I’ve been experimenting with the AI page agent — some things worked really well, others burned through my tokens before I could finish. Here’s what I tried:
Finance Dashboard (Success!) I built a dashboard that pulls all my financial data onto a single page — income totals, expenses, expenses by category, invoices split by EU/non-EU, etc. — everything I need for taxes and VAT in one place. I just select the year and it all updates. Really impressive!
Agreement Generator (Promising, but ran into issues) I set up an agreement generator using a formula (link + Entity ID) as a workaround, since triggering actions via button isn’t possible yet — which would be a great feature, by the way 
. It auto-populates all the client data (name, address, details, etc.) and renders a preview in HTML with a button so I can review it and edit it, before downloading as a PDF with a second button.
The problems I hit: The agent struggled to format the PDF correctly. The chat hit its context limit about 3 times, forcing me to re-explain the context each time — which costs even more tokens, so I ended up running out of tokens before finishing
The potential here is huge — Quotes, Invoices, Agreements — all auto-generated from entity data. For now, though, I’m falling back to a static HTML template for PDF generation!
1 Like
Do you mean a button in a custom HTML page inside Fibery? I used “helper checkboxes” so the HTML page can update a checkbox called say “Trigger” which will set off the automation
NO, I meant a button that fires the created link to the HTML/UI that the page Agent created. So, for example, I can have a button on my Entity (Where I have all the info about the client) to “Create a proposal”, that would fire the link from the page agent, that open this UI with all the information already filled out.
Testing next iteration of Fibery Apps builder
8 Likes
WTha… Amazing stuff!
Is that an output of the Fibery AI prompt?
Wow! Love it!
Looks very cool! 
This fills me with so much excitement. One of my clients is a local government municipality. In working with them for the past 1.5 years, I have had to many occasions in which I needed to make data available in a training-free, easily digestible form. In some cases, that need is only temporary—maybe a few months, as we’re building other systems—so I don’t want to go through the process of building a website to do API calls. Some of those use cases are:
- Temporary display of data for approval purposes. In this case, permitting requirements. I wanted x number of staff users to be able to connect to a site to see what requirements were defined, and comment if they saw any issues. I didn’t want to create accounts for everyone because most of them would never need to access Fibery again after that.
- Searchable portal on the town’s website of permitting stats. In this case, it would be a permanent search portal viewed through their website. Folks would be able to look up public information about permits in process and completed. (This is worth doing via HTML/API, but that’s time I don’t have right now.)
- Easy “refresh” of Fibery data from their permitting system. Weekly, they need to refresh the data they present to the public. I was hoping to build a super easy tool through which town staff could upload into Fibery the data export they get from their permitting system. Basically, click a button, choose the file, and go away. Fibery takes the file and updates the data for display.
Meaning no disrespect to the employees of this client, but they are not at all technical. They are very task based in everything they do. While I see Fibery as a hub of virtually anything I’d want to do with my business or my clients’ data, they see things in terms of, “which button do I press?”
I’m not sure any of this is aligned with what you have in mind for this, but I’m hopeful. 
3 Likes
What AirDiamond said!
1 Like
Same for me! Most of my clients only need to log in and click a few buttons once or twice per month. So this demo slaps! 
1 Like
Now we are collecting ideas here!
1 Like
Unfortunately I gave false promise. Based on latest experiments you will be able to build full-blown react apps, not single pages.
However, conversion should be relatively easy, one dumb idea we have just copy HTML to this new Agent and ask it to build the app based on the code you already have.
2 Likes
This is super exciting news 
We’re already actively using the current HTML pages functionality for real workflows, and this expands the possibilities even further.
The idea of being able to build full React apps inside Fibery sounds incredibly powerful, especially for custom operational interfaces, matrix systems, planning tools, and workflow-specific UIs.
And it’s great to hear that migration/conversion from existing HTML pages should be relatively straightforward.