Who This Is For
This lab is useful to you if you are:
Jumping between your project management tool, your calendar, and your task list to see what's due and how last week performed
Managing a sales pipeline and manually checking CRMs (like HubSpot), your calendar, and your inbox every morning before you can think straight
A founder tracking priorities across automations, meetings, and open tasks with no single view of it all
Paying for a dashboard tool, or spending hours in Notion or spreadsheets, that still isn't showing what you actually need
Running weekly reports manually when you'd rather have a live view you can reload in one click
Watching your team's key metrics across disconnected tools with no easy way to bring them together
This is not for someone who tracks one metric in one tool and checks it once a day.
Live Artifacts make the most sense when you are pulling data from at least two different sources and the manual process of checking them separately costs you real time each week.
How the Workflow Runs
Connect tools → Define your metrics → Ask Claude to build → Review the artifact → Reload to refresh
Time to Set Up
Time to set up: 20–30 minutes for the first setup, connector authentication, and dashboard configuration.
Daily time after that: Under 30 seconds to reload and see fresh data whenever you need it.
Tools Needed
Claude desktop app with Cowork mode enabled
Google Calendar connector
Zapier MCP connector
A list of the metrics you want on your dashboard
Optional: HubSpot connector (if available on your plan)
Optional: YouTube connector (if available on your plan)
Step-by-Step Walkthrough
Step 1: Understand what Live Artifacts should and should not do
Before setting anything up, set the right expectations.
Live Artifacts can help with:
Pulling live data from your connected tools into a single visual dashboard
Displaying metrics, upcoming events, tasks, and status updates in one place
Refreshing data each time you open or reload the artifact
Letting you build and iterate on the dashboard conversationally, with no code required
Persisting across sessions so the dashboard is always available when you open Claude
It cannot fully replace dedicated analytics platforms with deep historical data and custom reporting.
It does not cover:
Auto-refreshing in the background; it updates when you open or reload it, not on a timer
Pulling data from tools that are not connected to your Cowork account
Writing or modifying data in any connected tool; it is read-only
Surfacing data from files or attachments not accessible through a connector
Step 2: Set up your connectors in Claude Cowork
Open the Claude desktop app and switch to Cowork mode. From the connector panel, connect the tools you want your dashboard to pull from.
Start with Google Calendar and Zapier MCP. Both are confirmed to work. Google Calendar surfaces upcoming events and deadlines. Zapier MCP bridges tools that don't have a native connector yet, like Beehiiv, so you can pull newsletter stats directly into the dashboard.
Authenticate each connector with the relevant account. Claude only reads from these tools; it does not send, create, or modify anything.
Note: HubSpot and YouTube connectors may be available depending on your plan and which plugins you have installed. If they're not showing up natively, Zapier MCP may be able to route that data. Check your connector panel before assuming a tool isn't supported.
Step 3: Replace the default configuration with your real context
Before asking Claude to build anything, give it the context it needs to build the right dashboard for you.
Tell Claude your:
Role and what you use the dashboard for (e.g., "I run a newsletter and want to track performance and upcoming send dates")
Specific metrics you want to see (e.g., new subscribers this week, open rate for last issue, total subscriber count)
Time period each metric should cover (e.g., last 7 days, this month, today only)
Which connected tool is the source for each metric
Preferred layout (e.g., cards at the top for key numbers, a list below for upcoming events and tasks)
What you want to be able to read in under 30 seconds
The more specific you are here, the faster you get to a dashboard that's actually useful.
Step 4: Teach Claude what a "good dashboard" looks like for you
→ Once your connectors and context are in place, define the structure before Claude starts building.
→ This matters because a generic "build me a dashboard" prompt produces a default layout based on what Claude assumes is relevant, not what you actually look at first. The goal is a dashboard where the most important thing is the first thing you see.
→ Start by picking a primary use case. For example:
Newsletter operator: Open rate, subscriber count, new subs this week, upcoming send dates from Calendar, open tasks from Zapier
Founder: Top priorities due today from Zapier, today's meetings from Calendar, key blockers
Sales leader: Pipeline status from HubSpot, calls booked this week from Calendar, follow-ups due
→ Then specify the visual format. Cards work well for numbers ("452 new subscribers this week"). A list works better for events and tasks ("Thursday 9am: Newsletter send").
→ Tell Claude what to filter out. If Zapier surfaces 40 tasks, specify you only want the top 3–5 due soonest, not the entire backlog.
Without this step, the artifact may pull too much and display it without a clear hierarchy. With this step, the dashboard leads with the numbers you care about and keeps everything else secondary.
The output of this step should ideally comprise:
A prioritized list of the metrics you want, in the order you want to see them
A defined time window for each metric
A layout preference (e.g., cards on top, timeline or task list below)
A filter for noisy or low-value data from each source
One sentence describing what a 5-second glance at the dashboard should tell you
Want the full breakdown?
This is where you get real AI workflows, prompts, and systems you can use to automate your work. If you're serious about using tools like Claude to grow your business, this is for you.
Unlock full access today