Table · reads budget_line

Budget

Allocations vs spend by category.

Rows and columns, sortable and filterable.

Four categories, one of them over. The agent wrote every figure from what it was told.
CategoryAllocatedSpentRemainingStatus
Venue€8,000€6,400€1,600On track
Catering€5,500€5,950−€450Over
Photography€2,200€1,100€1,100Deposit paid
Flowers€1,400€0€1,400Not started

How it works

  1. 1

    Every field becomes a column; you choose which to show.

  2. 2

    Sorting and filtering happen on the data, not just the visible page.

  3. 3

    Values stay editable in place where the field allows it.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

Questions

What data does the Budget page use?

It reads budget_line records the agent has collected. Allocations vs spend by category. 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 table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

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.

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

Agents

More

🏪
Find Providers
👤
Profile
FAQ