April 23, 2026 / Experimental UI pages creation via AI, Sort improvement

ok! thank you!

Also a quick question regarding this feature :slightly_smiling_face:

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? :thinking:

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 :wink:. 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.