Flow quick reference

Everything the Files API exposes to Flow Builder: the actions, the screen component, the rules that differ from Apex, and two patterns you can copy.

The invocable actions

Six invocable actions, category Sliick Files in Flow Builder.

Action	Inputs	Outputs (plus Success / Error Code / Error Message)
Sliick Files: Upload File	Record ID, File Name, Content Type, File Body (Base64)	File ID, Download URL
Sliick Files: List Files	Record ID	Files (FileInfoOutput collection)
Sliick Files: Get Download URL	File ID	Download URL, Expires At
Sliick Files: Delete File	File ID, Record ID	-
Sliick Files: Rename File	File ID, New Name	-
Sliick Files: Move File	File ID, Source Record ID, Target Record ID	-

Device upload in a screen flow uses the Sliick File Upload screen component (not the Upload File action). Inputs: Record ID, Require Upload. Outputs: File ID, File Name. It uploads browser-direct to the active provider (presigned PUT for external storage - no 4MB cap, thumbnails included; native Salesforce Files upload otherwise).

How the actions behave

The running user needs the same two grants as an Apex caller. See Setup.

• Branch on outputs, not faults. Per-item failures return Success = false with an Error Code - wire a Decision element. The fault path fires only for call-level failures (most commonly a missing custom permission).
• Callout rules apply. Upload File (external) and Get Download URL (external) perform callouts: in record-triggered flows, run them from an asynchronous or scheduled path. List/Delete/Rename/Move are callout-free.
• Device upload uses the screen component. The Upload File action is for files the flow already holds as base64 (generated documents, callout responses). For device uploads in a screen flow, use the Sliick File Upload screen component.
• List Files returns FileInfoOutput records (an Apex-defined type) you can loop over; fields mirror FileInfo.
• The presigned pair and Get File Bodies are not exposed to Flow.

Pattern: screen-flow device upload

1. Screen: collect record fields.
2. Create Records: insert the record; store its id (e.g. recordId).
3. Screen: add the Sliick File Upload component; set Record ID = {!recordId}, Require Upload = true.
4. Files upload browser-direct to the active provider; File ID / File Name are available to later elements.

Pattern: record-triggered attachment routing

1. Record-Triggered Flow, after-save.
2. Sliick Files: List Files (Record ID = source record) → loop the FileInfoOutput collection.
3. Per file: Rename File, then Move File (Source = source record, Target = related record). Both are callout-free.
4. Decision on Success after each action routes per-item failures.