Build a morning briefing dashboard in Claude

A Claude dashboard turns a question about your data into a page you can read, filter and check. The most useful first one is a morning briefing: the few numbers you look at before you start work, on one page, with a to-do list for the day. This is the prompt, how to make it yours, a version with sample data to try first, and 20 dashboards people actually use.

What changed from the old dashboards

• Before: a dashboard built as an HTML artifact was a snapshot of the data at the moment it was built. To see new numbers you rebuilt it.
• Now: Claude writes a query for each chart and runs it against your data source. Each chart shows its query and when its data was last refreshed.
• Check any number: open a chart's query. In Sources, a row shows the query, the transform and the result.

What you need

• A paid Claude plan. Dashboards is a beta on Pro, Max, Team and Enterprise. On Enterprise, an owner turns it on.
• Your data. Connect the apps you want in Claude (Settings, then Connectors), or use a file or the sample data below.
• To start: nothing else. The sample-data version below needs no connection.

The morning briefing prompt

Open Claude on the web, type /Dashboard in the message box, and paste this. Replace everything in [square brackets] with your own, and delete any section you don't want.

Build me a morning briefing dashboard for [my name or business]. One page I read in two minutes before I start work.

Sections, in this order:
1. Top 5 trending news in [my topic]: headline, source and one line on why it matters to me.
2. Top 5 trending repos on GitHub today: name, stars gained today, total stars and one line on what it does.
3. Revenue from [my app or store]: yesterday, 7-day average, month to date, and a 14-day line.
4. Social posts in the last 7 days from [my accounts]: views, saves and comments, with the best post highlighted.
5. Ad spend on [Meta, Google or both]: spent against daily budget, ROAS, cost per result, and flag any campaign more than [30%] over its target cost.
6. Emails to follow up: people waiting more than [2] days, how long, and a suggested one-line next step.
7. Yesterday's completed tasks, then a to-do list for today of at most [6] items, built from what I finished yesterday, the follow-ups above, and anything outside its normal range. Rank by what unblocks money or a person waiting.

Data: [name each connector, file or sheet to read, or say "use the sample data below"].
Design: [dark, phone-first, one accent colour]. Show where each number came from and when it was fetched.
Rules: describe and prioritise only. If a source can't be read, say "not available" for that section. Never invent a number.

Three ways to make it yours: replace a bracket, delete a section, or add one. Each section is one numbered line, so adding "8. Today's meetings from [my calendar], in order, with one line of context each." works the same way.

Try it first with sample data

Paste this to see the layout without connecting anything. The numbers are made up. The news items and repos are real headlines and trending repos from early October, used as sample data.

Build a morning briefing dashboard for me, a one-person app business. One page I read in two minutes before I start work. Use only the sample data below, which is made up for a demo, and put a small 'Sample data' note in the footer. Sections in this order: 1) Top 5 trending AI news: headline, source and one line on why it matters. 2) Top 5 trending GitHub repos today: name, stars gained today, total stars and one line on what it does. 3) App revenue: yesterday, 7-day average, month to date, and a 14-day line. 4) Social posts, last 7 days: views, saves, comments, with the best post highlighted. 5) Ad spend: spent against daily budget, ROAS, cost per result, and flag any campaign more than 30% over its target cost. 6) Emails to follow up: people waiting more than 2 days, how long, and a suggested one-line next step. 7) Yesterday's completed tasks, then a to-do list for today of at most 6 items, built from what I finished yesterday, the follow-ups above, and anything outside its normal range, ranked by what unblocks money or a person waiting. Dark, phone-first, one accent colour, and show where each number came from. Describe and prioritise only; never invent a number.

SAMPLE DATA.
News: Claude Haiku 5.5 (Anthropic, 7 Oct); GPT-6 and Intelligent UI for everyone (OpenAI, 7 Oct); Claude Dashboards and Motion (Anthropic, 8 Oct); Liquid AI opens its d1 decision models (Liquid AI, 7 Oct); Microsoft Execution Containers, a sandbox for AI agents (Microsoft, 7 Oct).
Repos (stars today / total): morluto/rea 25,599 / 104,007; boykopovar/AnyPS5 3,952 / 30,091; storytold/artcraft 2,957 / 17,866; cathrynlavery/diagram-design 1,083 / 50,325; bilawalsidhu/gods-eye-view 886 / 51,667.
Revenue by day, last 14 days in dollars: 1020, 1088, 1102, 1056, 1187, 1240, 1319, 1058, 1104, 1161, 1199, 1235, 1176, 1284; month to date 14,121; MRR 38,400; new subscribers yesterday 31; trial starts yesterday 46.
Social, last 7 days (post, type, views / saves / comments): Launch day reel, reel, 12,400 / 94 / 41; How it works reel, reel, 9,180 / 61 / 27; Starter pack carousel, carousel, 2,150 / 118 / 9; Customer story reel, reel, 5,640 / 33 / 14; Quick tips reel, reel, 3,870 / 29 / 11.
Ads: Meta campaign 'Spring creators' spent 212 of 250 daily budget, ROAS 2.9, cost per trial 9.60 against a target of 7.00, frequency 3.8; Google campaign 'Brand search' spent 64 of 80, ROAS 3.4, cost per trial 5.90 against a target of 7.00.
Emails waiting: Dana K., Demo follow-up, 5 days; Aisha M., Trial feedback, 4 days; Priya N., Partnership quote, 3 days; Marcus L., Invoice 1042 question, 2 days; Tom R., Press inquiry, 1 day.
Completed yesterday: shipped onboarding email v2; fixed iOS login crash; sent invoice batch; reviewed ad creatives; recorded 2 reels; replied to 9 support tickets.

Swap list

When you are ready to use your own data, replace the sample for one section at a time.

Other sections people add: today's meetings, overdue invoices, support tickets, a markets board (below), health numbers, weather.

Have it ready every morning

A page that uses connectors fetches its data when it loads, and it can refresh when you use a refresh control on the page. It does not fetch while it is closed, so on its own it is a page you open, not a message that arrives.

To have it ready each morning, Anthropic documents routines: a saved prompt that runs on a schedule (hourly, daily, weekdays or weekly; the minimum interval is one hour) on Anthropic's cloud, so it keeps working when your laptop is closed. A routine republishes a page you already published without asking only when the page is yours, is not shared publicly, carries no supporting files, and holds no grant that reaches beyond the page, such as connector calls. A page that makes connector calls is therefore not republished without your approval. One way around it is to ask the routine to write the day's numbers into the page, so the page needs no connector calls. (Untested here.) Routines are in research preview on Pro, Max, Team and Enterprise.

On the desktop, Claude Cowork has scheduled tasks. Casey Danielle's 8 AM text and Ileana Marcut's Monday refresh both work this way. They run on your computer, so it has to be on.

If your dashboard reads from a database you fill, the page is only as recent as the last update. Ask Claude: "Make sure this updates my database once a day." It builds a scheduled task. To set one up by hand, open Scheduled, create a new task, and set the instructions, the frequency and the permissions. For many people once a day, or even once a week, is enough.

Keep history over time (optional)

A dashboard that reads an app directly, such as Gmail, shows what is there now. It cannot show change over time. To track change, store the data in a database first and point the dashboard at it. One walkthrough (Mansel Scheffel's) uses Supabase through Claude's Supabase connector. The free plan has a 500 MB limit, and he puts the cheapest paid tier at about $25. The dashboard queries through the connector (MCP), so a command-line tool will not work for this.

The market board

A morning briefing can include a markets section. This is the one we built from TradingView's connector in Claude. It ranks six markets by trend strength with the numbers behind each.

Use my TradingView connector (read-only: market data only, do not create or change any alerts or watchlists) to build a dashboard that answers one question: which of these markets are trending, and which look stretched, right now? Markets: BTCUSDT, ETHUSDT, SPY, QQQ, EURUSD and gold (XAUUSD). For each market show the last price, the 1-day and 1-week change, and RSI(14), ADX and MACD from the daily timeframe, plus a 90-day daily close line. Add a ranking table sorted by trend strength, a filter by asset class (crypto, equities, FX, metals), and show each chart's query and when its data was last refreshed. Dark, phone-first, one accent colour. Show data only, with no buy or sell recommendations.

Then one follow-up colours it by direction and adds a plain-English reading under each market:

Two changes. 1) Colour by direction: uptrend green, downtrend red, ranging grey, on the ranking table, the cards and the chart lines. Stretched markets get an amber outline and keep the Stretch label. Add an arrow (up, down, flat) so colour is not the only signal. 2) Under each card add a one-line plain-English reading of what its indicators say right now: trend direction and strength, whether RSI is stretched, and where MACD sits against its signal. Describe the current state only: no buy, sell, hold, entry or exit wording and no predictions. Keep every number exactly the same.

How it decides direction, from the page's own code: it calculates +DI, -DI and ADX(14) from the last 300 daily bars. If ADX is below 20 the market is flat. At 20 or higher it is up when +DI is above -DI and down otherwise. The cut-offs (20, 25 for "trending", 50 for "very strong") are common values Claude chose, so change them in your prompt. The numbers are calculated by the page from price bars, so small differences from your TradingView chart are normal.

This board reads daily bars and loads once. It suits a daily check, not day trading. If it says the TradingView connector failed, reply "Please try the TradingView connector again."

20 dashboards people actually use

Each of these is a build someone has written about using. "Daily use" means the author says they open it most days. "In use" means they present it as working. "Walkthrough" means a tutorial with steps. "Tested" means a test with checks. The name in brackets after each creator is the Claude surface they used: Dashboards, Cowork live artifacts or Claude Code. Put your own data source in the brackets of each prompt.

Start the day

1. "Build my daily work briefing from [project tool], [CRM] and [invoice sheet]. For each client show status and next action, then what is overdue or due today, this week's content plan, open sales opportunities to follow up, and unpaid invoices with days late. Put the five most urgent items at the top."
2. "Build a daily tracker for my online store from [store], [email tool] and [ads]. Show yesterday's sales and profit after my costs ([product cost %], [shipping per order], [fixed monthly costs], [VAT]), a rolling 13-week cash forecast, ad spend and ROAS by campaign tagged Winner, Fatiguing or Testing, and a ranked list of what to do today."
3. "Build my daily command center: today's meetings from [calendar], the emails that need a reply from [inbox], my open tasks from [task tool], and a morning routine checklist with a progress bar."
4. "Build my week on one page: schedule from [calendar], inbox items that need action, tasks due this week, and notes from [notes tool]. Group by day and show what is still unplanned."
5. "Build a personal week view: this week's focus, a task checklist, workout sessions, calendar events and a short reflection box. Add a habit grid for [my habits] with a weekly score."
6. "Build a project dashboard from the notes in [folder]: counts of active projects, tasks and blocked items, then each project's status and current focus. Flag any project not touched in [14] days and suggest the order I should work in."
7. "Build a morning command center: a greeting, an alert banner if two meetings clash or something is overdue, a 'Your day' list of meetings with one line of context each, and a 'While you were away' list of what changed since yesterday. Show when it was last refreshed."

Sales and clients

8. "Build a pipeline overview from [sheet or CRM]: total pipeline value, deal count and value by stage, a leaderboard by owner, and deals with no contact in the last [21] days. Check every total against the raw numbers."
9. "From my open deals in [source], build a dashboard that answers: which deals need attention this week? Rank by days since last activity and deal size, let me filter by owner, and show each chart's query."
10. "Build a sales dashboard from [file or warehouse table]: revenue by region and product category over time, top products and margin. Before totalling, check for repeated IDs and test records and tell me what you left out."
11. "Read my [DMs or inbox] and group the messages by intent: partnership, lead request, question, other. Show the priority replies first as tasks, each with a suggested one-line reply."

Marketing and content

12. "Build a weekly campaign tracker from [ads export], [analytics export] and [targets sheet]: tiles for spend, leads and pipeline created with the change against last week, a line of leads by channel over eight weeks, and a campaign table ranked by pipeline with cost per pipeline. Add a filter for this week, last four weeks and this quarter."
13. "Build an ad spend dashboard from [ad platforms]: spend by channel for the last 30 days, ROAS and cost per result by campaign, and a table of top campaigns. Flag any campaign where cost per result is more than [30%] over target."
14. "Build a content tracker from [content database] and [analytics]: how many pieces ship this week and how many are overdue, a board from brief to live, and the top 10 pieces published in the last 30 days by pageviews."
15. "Build a newsletter dashboard from [stats source]: subscribers gained, lost and net each week, performance of each post, paid subscribers, and where new subscribers come from. Add a forecast to [my goal]."
16. "Build a trend board from [signals source]: viral posts and competitor activity in my niche, with a filter for each platform and a viral-only switch, and the five things most worth reacting to today."

Markets and your own AI use

17. "Build a usage dashboard from [my database of Claude usage metrics]: which skills ran, what each day cost, and what failed. Flag any day more than [30%] above its average."

18. The market board prompt above, with your own markets in place of the six.

Personal

19. "Build a recovery dashboard from [health data]: 30-day trends for heart rate variability, resting heart rate, sleep and steps, and flag any day far from my average."
20. "Build a kitchen board: daily calorie and macro targets, meals I can pick from, next-meal suggestions that fit what is left for the day, and a grocery list sorted by store aisle."

Things to take note of

• Check the numbers against the source before you act on them. In one published test of 400 deals every total was right, but a bar chart drew a 29 percent share at almost full width, and Claude's own layout check had reported everything fine.
• Expect to edit it. One builder has edited their briefing about 20 times. Another says Claude gets 70 to 80 percent right on the first run.
• Give each dashboard an owner who checks it against the source every week. One builder's data feed broke and went unnoticed for four days.
• Change the layout and the refresh instructions together. One builder edited a live artifact's layout, ran its scheduled refresh, and Claude redesigned the page completely, because the saved instructions assumed the old layout.
• A page fetches its data when it loads. It does not run on a schedule by itself.
• A page that uses connectors can't be shared with a public link, and each viewer needs their own connection.
• Dashboards count toward your plan's usage limits.
• It is a beta: a dashboard can say every query ran when nothing loaded. Tell Claude: "I'm getting an error saying nothing loaded. Can you check this? The dashboard needs a fix."
• Let it read, not change. In each connected app's settings, set the write and delete tools to ask for your approval.
• This guide is not from, or endorsed by, TradingView or Anthropic, and the market board describes data. It is not investment advice.