Skip to content
← Blog

How to build an internal dashboard with Claude

Build an internal dashboard with Claude: pick the five numbers the team checks, point Claude at where the data lives, and host it on floo behind invite-only sign-in, with a daily job that refreshes the numbers and a Monday summary to chat.

floo team

TL;DR

To build an internal dashboard with Claude, name the few numbers the team argues about, say where each comes from, and let Claude write the queries and the page. On floo it runs behind invite-only sign-in, a scheduled job pulls fresh data into Postgres, and the team gets one link with the same numbers for everyone.

  • Start with five numbers, not fifty charts.
  • A daily job copies data from other tools into Postgres. The page reads from there.
  • Invite-only sign-in, and API keys stay on the server.

Every team has a number that lives in three places and disagrees in all of them: weekly signups, open tickets, revenue this month. A dashboard Claude builds can settle it, because the query is written down once and everyone opens the same link.

1. Pick the numbers

Write down what the team actually checks, and where it comes from today:

Build a dashboard for the support team. Show open tickets by priority, tickets opened and closed per day for the last 30 days, median first-response time this week, and the five oldest open tickets with links. Data comes from our help desk's API. Refresh it every hour.

Five numbers with a source each is a better first version than a page of every chart the data allows.

2. Decide where the data lives

Where the data isHow the dashboard gets it
Another tool's APIA cron job pulls it into the app's Postgres on a schedule
The app's own PostgresThe page queries it directly
BigQueryThe app queries it with its own identity, no key. See private BigQuery

Copying API data into Postgres on a schedule is usually right. The page loads fast, the tool's rate limits don't matter, and you get history the tool may not keep.

3. The config

[app]
name = "support-dashboard"
access_mode = "accounts"

[managed.default]
type = "postgres"

[cron.sync-tickets]
schedule = "0 * * * *"
command = "node scripts/sync-tickets.js"
service = "web"

Store the help desk key once:

floo env set HELPDESK_API_KEY --stdin --app support-dashboard

Then invite the team: floo apps invite, or "Invite the support team" in Claude chat with the floo connector.

4. Test the sync before the page

Run the job now and read its output:

floo cron run sync-tickets --app support-dashboard
floo logs --cron sync-tickets --app support-dashboard

If the numbers in Postgres match the help desk, the page will too. Then ask Claude for the page.

Make it useful past week one

  • Show when the data was last refreshed. A stale number someone trusts is worse than none.
  • Link each number to its rows. "12 urgent tickets" should open the 12 tickets.
  • Send the summary where people already look. A Monday job that posts the numbers to chat gets read more than the page. See how to run a daily job in an app Claude built.

For the general case of turning a recurring task into an app, see how to automate an internal process with Claude.

Frequently asked questions

Can Claude build an internal dashboard?

Yes. Tell Claude which numbers the team checks, where the data comes from, and who should see it. Claude writes the queries, the charts, and the page. On floo, the dashboard runs behind invite-only sign-in, with a Postgres database and a scheduled job to refresh the data.

How does the dashboard get data from other tools?

A scheduled job pulls from each tool's API into the dashboard's Postgres, using API keys stored with floo env set. The page reads from Postgres, so it loads fast and the numbers are the same for everyone. A dashboard can also query an existing database or BigQuery directly.

Who can see a dashboard hosted on floo?

Only people you invite. Set access_mode = "accounts" and every page asks for sign-in first. The app also knows who is looking, so it can show some numbers only to admins.

Get your app live.

read https://getfloo.com/agents.md and set me up on floo

Get an API key
Usage-based pricing. See plans →