Custom · reads custom
Custom page
Owner-composed layout (paid + validated).
A view composed for one purpose.
How it works
- 1
You choose the data kind and how it is shown.
- 2
An optional filter narrows it to the slice you care about.
- 3
It is reviewed before it goes live, then behaves like any built-in page.
Best for
The view your work needs that no standard one covers.
Not the right choice for
Something a built-in page already does — those come with no wait.
Questions
What data does the Custom page page use?
It reads custom records the agent has collected. Owner-composed layout (paid + validated). Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a custom the wrong choice?
Something a built-in page already does — those come with no wait. It is best for: the view your work needs that no standard one covers.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Dev & automation

Seasonal tasting menu

Canapé selection

Service — per waiter

Glassware hire
API connectors
Connected live APIs.
Webhooks
Outgoing event hooks.
Datasets
Elastic uploaded data.

Seasonal tasting menu

Canapé selection

Service — per waiter

Glassware hire
Integrations
Third-party links.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free