Artifacts turn a one-time answer into a living tool you can open again and again, with numbers that stay current. This guide explains what an artifact is, why it is worth building, and the one ingredient that makes it genuinely useful: a Connector wired into the systems where your data lives.
Start Here
An artifact is a small, self-contained tool that Claude builds for you and saves so you can return to it later. Picture a single web page that holds everything it needs to run: the layout, the logic, and the instructions for fetching its data. You open it like any other page, but instead of showing a frozen snapshot, it reaches out and pulls in fresh information each time it loads.
The difference between an artifact and an ordinary chat answer is permanence and interactivity. A chat answer is a moment in time. An artifact is a reusable instrument. Common examples include a live metrics page, a project tracker, a budgeting calculator, or a financial dashboard. The CFO Dashboard on this site is one such example: an artifact that surfaces key financial figures in one view rather than forcing you to rebuild the report by hand every month.
In one sentence: an artifact is a saved, interactive mini-application that refreshes its own data, so the work of asking for a report becomes the work of simply opening it.
The Payoff
The value is not the page itself. It is the time you stop spending on repetitive assembly, and the confidence that what you are looking at is current rather than copied from last week.
Each time you open the artifact it pulls live data from your connected systems, so you never wonder whether the numbers are stale.
Build the logic once. After that, a monthly report or a recurring check becomes a single click instead of a fresh request every time.
Filters, sorting, charts, and inputs let you explore the data yourself rather than waiting for a new version to be produced.
Through Connectors, an artifact reads directly from the source of truth, whether that is your ERP, accounting platform, or spreadsheets.
An artifact is a single page, which makes it easy to demonstrate, embed in a portfolio, or hand to a colleague.
You describe the tool you want and the data it should read. There is no lengthy software project behind it.
The Critical Piece
On its own, an artifact is just a well-designed shell. It becomes powerful the moment it can read your actual data, and that is precisely what a Connector provides. A Connector is a secure bridge between the artifact and an outside system: your ERP, your accounting software, a bank feed, a CRM, a spreadsheet store, or a messaging tool. Without a Connector, a dashboard can only show numbers you typed in by hand. With one, it reads the live source and stays honest.
It helps to think of the Connector as the wiring and the artifact as the appliance. You authorize the connection once, granting permission for the artifact to read specific data. From then on, the artifact can call the Connector whenever it loads to fetch exactly what it needs. Behind the scenes the artifact uses a request such as callMcpTool(name, args) to ask the Connector for data, but you never have to touch that plumbing. You describe the data you want in plain language, and the connection handles the rest.
Add the Connector for the platform you want to read, for example your ERP or accounting tool, and sign in to authorize it. This is a one-time setup.
Approve only the data the artifact needs to read. Connectors respect the permissions you set, so you stay in control of what is exposed.
When you ask for the artifact, name the system and the figures it should show, such as monthly revenue, cash balance, or open invoices from the ERP.
The artifact reads live data on load. A built-in reload control pulls the latest figures whenever you want them, with no rebuild required.
Rule of thumb: the quality of an artifact is the quality of its Connectors. A beautiful dashboard wired to nothing is a mockup. The same dashboard wired to your ERP is a tool you will use every day.
Where It Runs
An artifact can run in one of two homes. The choice affects where the work happens and how you reach the tool, but it does not change the most important requirement: in both cases the artifact must be connected to your systems, including the ERP, to be worth anything.
The artifact runs on your own machine through the desktop app.
The artifact runs in the cloud and persists across sessions.
The constant in both setups: the artifact is only as useful as the systems it can reach. For a finance tool, the ERP is the non-negotiable connection, because it is the system of record for the numbers that matter. Connect it first, then layer on accounting, banking, or CRM data as needed.
Connect The Source of Truth
For a finance artifact, the ERP is where the authoritative numbers live: revenue, expenses, cash, payables, and the ledger that everything reconciles back to. If the artifact is not reading from the ERP, it is reading from a copy, and copies drift. Connecting the ERP is what lets a dashboard claim to show the real state of the business rather than an approximation.
Once the ERP is connected, additional Connectors extend the picture. Accounting software adds detail to the close, a bank feed confirms cash positions, and a CRM ties revenue to the pipeline behind it. The pattern is always the same: connect the source of truth first, then enrich it. Build in that order and every artifact you create rests on data you can defend.
Start small. Pick one report you rebuild by hand each month, connect the system it comes from, and describe the view you want. Once you see live numbers load on their own, the rest follows naturally.
Explore the Tools