Artifacts
Generated content from workflow executions — how artifacts are stored, previewed, and downloaded.
What is an artifact?
An artifact is the output of a node after execution. It can be text, an image, a video, or an audio file. Artifacts are stored persistently and can be previewed, downloaded, or passed to downstream nodes.
Artifact types
| Type | Storage | Preview |
|---|---|---|
| Text | Database (inline) | Rendered in the node panel |
| Image | Object storage (MinIO/GCS) | Inline image viewer |
| Video | Object storage | Video player in panel |
| Audio | Object storage | Audio player in panel |
Viewing artifacts
After execution, click any green (completed) node to see its artifact in the right panel. For media files, you get an inline preview with a download button.
Artifact gallery
All your generated artifacts are also accessible from Profile → Artifacts. This is a gallery view of everything you've generated across all workflows.
Storage
Media artifacts are stored in S3-compatible object storage:
- Development — MinIO (local)
- Production — Google Cloud Storage
Files are served via signed URLs with expiration for security.
Artifact lifecycle
- Created when a node completes execution
- Linked to the specific WorkflowRun and Node
- Persisted indefinitely (no automatic deletion)
- Can be downloaded at any time from the gallery or node panel
- Used as
example_resultswhen publishing templates
Last updated: 2026-03-27