File Operation Nodes
File nodes interact with the platform's file storage system. All file operations work against the BizFirstAI file storage layer — not the local filesystem of the application server. Files can come from form submissions, upstream API responses, or the file storage vault.
read-file
Reads a file from storage and makes its content available to downstream nodes.
| Field | Description |
|---|---|
| File Path / Key | Storage path or expression resolving to a file key (e.g., {{$json.attachmentKey}}) |
| Read Mode | Text (UTF-8 string), Binary (base64), Auto-parse (JSON/CSV/XML detected automatically) |
| Encoding | Character encoding for text mode (default: UTF-8) |
Output: { key, name, mimeType, size, content }
write-file
Writes content to a file in storage.
| Field | Description |
|---|---|
| File Name | Output file name (supports expressions) |
| Content | Text string, JSON object, or base64 binary data (auto-detected) |
| Storage Path | Target folder in file storage |
| Overwrite | If a file with the same name exists: overwrite or version |
Output: { key, name, url, size, uploadedAt }
delete-file
Deletes a file from storage. Typically used for cleanup — removing temporary files created during processing.
| Field | Description |
|---|---|
| File Key | Storage key of the file to delete (expression supported) |
| Fail if Not Found | Toggle: fail with error, or skip silently if file does not exist |
File Storage Architecture
File nodes do not interact with a local disk. They call the BizFirstAI file storage service, which abstracts:
- Azure Blob Storage (cloud deployments)
- AWS S3 (cloud deployments)
- Local MinIO (on-premise deployments)
All file keys follow the pattern: {tenantId}/{executionId}/{filename}. Files created during an execution are automatically tagged with the execution ID for audit and cleanup purposes.