Skip to main content
An Artifact is the report, dashboard, analysis, exception queue, or interactive interface generated from a Flow. It is how the people who need a result see it, filter it, and act on it without opening the canvas. Most teams already produce these outputs. They export to a spreadsheet, paste into a deck, or rebuild a chart in a BI tool. The difference with an Artifact is what sits behind it.

Why build them in Prowork

Connected to the data

An Artifact is generated from the Flow’s data, not copied out of it. Each time the Flow runs, on demand, on a schedule, or from a trigger, the Artifact regenerates on the latest results.

Governed like the rest of your data

Viewers see an Artifact under the same permissions as the Flow that produced it. Nothing is exported to a file that travels on its own.

Traceable to the logic

Every number on the page comes from a visible step. Click a bar or a row and trace it back to the exact source rows and rules that produced it.

Connected to the data

A spreadsheet export is right on the day you made it. An Artifact is right as of the latest run. Because the Artifact is generated from the Flow, there is no separate refresh process to maintain. The Flow pulls the sources, applies the matching and calculations, handles the exceptions, and the Artifact reflects whatever came out. Schedule the Flow weekly and the executive summary is current every Monday. Trigger it from an inbound email or webhook and the exception queue updates as the data does. Filtering, sorting, searching, and drill-downs all work on the snapshot from that run. When a newer run exists, viewers click Refresh to see it. See Sharing artifacts for how refreshing works.

Governed like the rest of your data

Sharing a result usually means the data leaves the system that governs it. An Artifact stays inside Prowork.
  • Viewers open the Artifact in Prowork’s own viewer page, signed in to your org.
  • Who can view it is limited to people with access to the Flow, or, if you choose, anyone in your organization.
  • Only someone who can edit or share the Flow can create a link or change who can view it.
  • Downloading the underlying data is an explicit action, not the default way results move around.
The same workspace sign-in and Flow permissions that govern your data govern the Artifacts generated from it. See Sharing artifacts for the specifics.

Traceable to the logic

A chart in a deck is a picture of a number. An Artifact is a view onto a Flow. If a KPI looks off, click the bar or the row and trace it back through the steps that produced it, down to the source rows. Because the Flow is the implementation, the person who owns the Artifact can also fix the rule, rerun, and see the corrected result in the same page. Nobody has to reconcile a screenshot against a spreadsheet to find out where a number came from.
You do not have to decide up front whether you are doing analysis or building a report. Ask a question about your data and Prowork can answer it as an Artifact. If the answer proves useful again, the same Flow can be scheduled or triggered, and the Artifact becomes the recurring version of it, without rebuilding in another tool.

Where to go next

Artifact types

The shapes an Artifact can take and the interactive controls you can build into it.

Prompt an artifact

How to describe what you want, iterate on it, and style or brand the result.

Sharing artifacts

Share a live link, choose who can view it, refresh, and download the data behind it.
Last modified on September 21, 2026