Skip to main content

Live Apps

Build a live app

What a live app is, and how to build one by describing it, approving its data, picking a look and saving it.

Think of a live app as a wall display for your business that builds itself. You describe what you want to see — "how are sales going", "what did my agents do this week" — and the AI builds a real, clickable app on your own data. Then it stays current on its own: every number recomputes from the source each time you open it or hit refresh.

Revenue cockpitSALES · LIVELIVEUpdated 3m ago7d30d90d
This month
Revenue is running ahead of last month
Every number below recomputes when this app refreshes.
Revenue$41.8k+12%
Orders318+8%
Avg. order$131+3%
Revenue by week
How much you sold each week, newest on the right.
  • Northwind TradersPaid · 2h ago$3,200
  • Acme SuppliesPending · 5h ago$1,840
Shopify · Nirvai databases

A report is a photograph — true the day it was made. A live app is a window. Nothing in it is typed in or pasted; every value is fetched from where it actually lives: your Nirvai work, your connected services and your own databases, mixed in one view.

A good first ask

"Build me an app showing what my agents did this week — conversations by channel, which automations ran, and what it all cost in credits." Everything in that sentence is already in your account.

Live App or Chat App?​

Both are built by AI, and they solve different problems.

Live AppChat App
LivesIn its own Live Apps section, saved for goodBeside one chat conversation
DataRe-fetched from your tools every refreshThe data of that conversation
Best forSomething you'll open again next weekA one-off answer you want to click through
SharingWith your organizationA public link

How building works​

Building one is like briefing a designer who already has the keys to your filing cabinet. You say what you want to see; they go and look at what you actually have, come back with a plan, show you three looks, and only then build it. You approve at every step, and nothing is saved until you say so.

Before you start​

  • The more of Nirvai you already use — agents, databases, automations — the more there is to build on. You need nothing connected at all to build on your own Nirvai data.
  • To pull in an outside service (a store, an ad account, a CRM), it needs a saved connection first. See Credentials.

Step 1 — Describe it​

Go to Live Apps in the sidebar and click Create with AI. Type what you want in plain words:

"An app showing my Shopify sales this month, top products, and which of my agents closed the most conversations."

Say what you want to know, not how to lay it out — the look comes later. If you'd rather not start from scratch, three starter ideas (a sales dashboard, an ops monitor, a content gallery) are one click away, or you can start from a template.

Step 2 — Approve the plan​

The AI looks at what you have and comes back with Proposal ready. Click Review sources and you'll see exactly which data it intends to use, grouped by kind, with a one-line explanation of the app it has in mind.

Proposed appSales & agent performanceThis month's revenue and orders from your store, next to how your agents are handling conversations.
  • ShopifyOrders, products and revenue from your storeConnected tool
  • CustomersYour own table of accounts and their ownersDatabase
  • Agent conversationsConversations your agents had, by channelNirvai data
  • Meta AdsAd spend to compare against revenueAdd Meta Ads credential
You can build with what you have, or set up the missing sources first.Back to chatLooks good — build it

Anything you haven't connected shows up as a to set up row with a button that takes you where to fix it. You don't have to: Build with what I have skips it, and you can add it later.

This is the step worth reading

The sources you approve here are the only data the app will ever touch. It's the app's permission list — so check it, then approve it.

Step 3 — Pick a look​

Next comes Look ready. The AI designs three different directions for your app — not three shades of the same thing, but three genuinely different personalities, each with its own colours, typefaces and shape. If you have a brand, it uses your real logo and colours.

Proposed lookPick a look to build on — or go back to chat to tweak the colours, fonts, or logo.
Modern SaaSPicked
Clean and familiar, in your brand green.
Console
Dense and technical, for watching numbers move.
Editorial
Calm and printed, for reading and sharing.
Use "Modern SaaS"

You can pick one, or just say what you'd rather have — "the calm one, but in our blue" — and it re-designs. The look is only a skin: changing it later never touches your data.

Step 4 — Preview, then save​

The AI writes the app, runs it against your real data (never a made-up example), and tests it — at desktop and phone width, and with empty and failing data — before showing you anything. When it passes, you get Live app ready with a working Preview.

Click through it. When you're happy, hit Save live app and it becomes a permanent app with its own page.

Nothing is saved until you click Save

While you're building, the app lives in the builder as a draft. You'll find unsaved drafts under In progress on the Live Apps page, and you can pick them up where you left off — or discard them.

Changing it later​

Open the app and click Edit with AI. You can ask for anything in words — but the faster way is to point at what's wrong.

Turn on Tweak in the preview, then click any part of the app. Each element you click gets pinned with a note box. Write what should change; the app sends all your notes together as one instruction, so it makes every change in one pass instead of one at a time.

TweaksClick any element in the app to reference it here.
  • 1KPIRevenue overview“$42.6k”
    panel › kpi-rail › kpi-v
    Show last month underneath so I can compare.
  • 2ChartRevenue by week“Revenue by week”
    panel › chart
    Make this monthly instead of weekly.
  • 3TableRecent orders“Northwind Traders”
    panel › table › row
    What should change here? (required)
2 of 3 commentedAdd a comment to every elementSend tweaks (3)

Every pinned element needs a comment before you can send — that's deliberate, since an element with no note tells the AI nothing.

Troubleshooting​

What you seeWhat it meansWhat to do
A source is listed as to set upThe app wants a service you haven't connectedAdd the connection, or build without it and add it later
The AI asks you a question mid-buildIt needs one detail it can't guess (which store, which period)Answer it — you can reopen your answer with Answer again
It's still building after several minutesIt's testing against your real data, which takes time on big accountsLet it finish; you can leave and resume from In progress
The preview shows an errorA data step failed while renderingUse Fix with AI — it reopens the builder with the error already explained
You want to start overRestart clears the session's drafts and messages. Apps you already saved are kept

What's next​