Artifacts
Distinguish generated ActionFlow artifacts, uploaded run files, Knowledge Base files, and Agent artifacts, including the limits the current runtime enforces.
Artifacts
ActionFlows has separate file surfaces. A file being present in one surface does not make it a generated artifact in another.
| Surface | What it contains | Owner/path context |
|---|---|---|
| Flow artifacts | Files generated by supported Flow file/media nodes during a run | ActionFlow and run |
| Uploaded run files | Files selected for Flow inputs or a file field before the graph is saved | Organization and flow upload folder |
| Knowledge files | Documents uploaded to a Knowledge Base collection | Organization and Knowledge collection |
| Agent artifacts | Files generated by an Action Agent chat turn | Agent and session |
Generated Flow artifacts
When a supported node such as Generate Image, Generate Video, Generate Speech, Create Excel, or Generate File returns file-shaped output, the runtime can resolve the value, upload it to durable storage, and create an artifact record tied to the ActionFlow run and node. The node result is then rewritten to durable storage keys so the UI can render or download the file.
Open generated files from:
- Actionflow Studio → Artifacts;
- ActionFlow → Artifacts; or
- Organization → Storage → Flow Artifacts.
Use Run History to move from a run to the files that run produced. A remote artifact that cannot be fetched or stored is logged and may be absent from the artifact list; do not infer that every provider output was persisted.
Uploaded run files
A file selected in an Actionflow Studio node form is uploaded before the node value is saved. The graph stores a durable reference/URL, and the file is recorded as an uploaded organization file under a flow upload folder. It is not automatically recorded as a generated Flow artifact.
This is appropriate for a one-off input such as a document for a Flow node. For reusable documents, use Organization Files or a Knowledge Base collection.
The Actionflow Studio file picker can read a plan's data.maxFileSizeLimit value. The current upload action does not apply that plan value as a server-side file-size check, so a configured plan value must not be described as an enforced storage quota.
Knowledge files and Agent artifacts
Knowledge Base files are managed by their collection and are shown under the organization storage/knowledge area. They are not flow-run outputs. Agent artifacts are generated from Action Agent chat turns and are tied to an agent/session, not an ActionFlow run. See Agent artifacts and Organization artifacts.
Limits and enforcement
| Value | Current source | What is enforced today |
|---|---|---|
| Remote HTTP response size | MAX_HTTP_RESPONSE_BYTES | HTTP Request response reading stops at 5 MB. |
| Generated/remote artifact constant | MAX_ARTIFACT_BYTES | The current remote-download and Agent-generated artifact paths use a 25 MB guard. Do not infer that every direct provider-output path has the same per-file check. It is not an organization-wide quota. |
Plan data.maxFileSizeLimit | CMS pricing-plan configuration | Used by the Actionflow Studio file-input UI; the current upload action does not enforce it server-side. |
Plan data.storageLimit | CMS pricing-plan configuration | Storage usage is calculated and displayed; the current upload path does not enforce a total organization storage quota. |
Plan run.flowRunLogLimit | CMS pricing-plan configuration | When finite, history creation soft-deletes the oldest rows to keep the configured per-flow history count. This is a history-retention limit, not a file quota. |
Current limitation: Do not present a plan storage value or a file-picker value as a guaranteed organization quota. Only the limits marked as enforced in the table should be described as hard runtime checks.
Related
Subflow
The catalog exposes Subflow-shaped nodes, but the current runtime does not dispatch a child flow, create a nested run, or return child output.
Webhook
Receive external POST deliveries at a saved ActionFlow webhook URL, with token, idempotency, validation, passive-flow, and response-status behavior.