What your apps can read
A live app is like a window cut into a wall — it only shows what's on the other side of it. So the useful question is: what can be on the other side? Three things, and an app can look at all three at once.
A live app can read all three at once — the work happening inside Nirvai, the services you have connected, and your own tables.
1. Everything already in Nirvai
This is the one people don't expect. Your Nirvai account is itself a data source — no connection to set up, nothing to configure. If you use Nirvai, you can already build an app about how you use it.
| What it can read | In other words |
|---|---|
| Your agents | Every agent you've built, what it's made of (tools, knowledge, skills, databases, channels) and whether it's running |
| Conversations | Every conversation your agents had — which channel it came from (WhatsApp, Instagram, Slack, your site…), when, and how many |
| Agent tasks | The jobs agents ran on your database records: what was asked, what came back, how long it took |
| Automations | Your workflows — what triggers them, which agents they use, and what steps they take |
| Automation runs | The history of one automation running: each run, whether it worked, and where it failed |
| Credit usage | What you're spending, over any period — by agent, by feature, by resource |
| Memories | Your agents' memory stores: how big they are, who's connected to them, what permission they have |
| Databases | Your spaces and tables — how many columns, which views, who they're shared with |
| Outside assistants | What connected assistants like Claude Code did in your account, from the Activity Feed |
That's what makes a live app a control room rather than a chart. One app can show you what your agents did this week, which automations failed, and what it all cost — pulled from three different corners of Nirvai and lined up side by side.
Apps can read that a conversation happened, not what was said in it — message content is never exposed. The same goes for what's stored inside a memory: an app sees its size and settings, never its contents.
2. The services you've connected
Anything you've connected to Nirvai can feed an app: your store, your ad accounts, your CRM, your helpdesk, your spreadsheets. If you've set up a credential and a tool for it, an app can read from it.
Your sign-in details are never part of the app. When it fetches data, Nirvai supplies the connection on its own side — the app itself never sees or stores your keys, and neither does anyone you share it with.
3. Your own databases
Any Nirvai database table can back an app. The app can look things up, filter, sort and count — and that's all.
A live app can't change a record, send a message, or place an order. When you want to act on something you're looking at, the app hands you a link straight to that record where it really lives — the row in your table, the deal in your CRM, the order in your store. Looking and doing stay separate on purpose.
Mixing them is the point
The apps worth building rarely come from one source. Ad spend from Meta next to revenue from Shopify next to the deals in your own table. Credits spent by an agent next to how many conversations it handled. Each number comes from wherever it lives; the app is what puts them in the same picture.