Storage
Blokkio supports file storage for workflows that need to handle binary data — file uploads, document processing, image manipulation, and so on.
Storage providers
A storage provider is a backend where files are saved. Providers are configured by an administrator and are project-scoped.
Two provider types are available:
Local file storage
Stores files on the server's local filesystem. Suitable for development and self-hosted deployments where a single server handles all traffic.
File path structure: blokkio-files/{tenantId}/{projectId}/{fileId}
Local storage is not recommended for production deployments with multiple worker nodes. Files written by one node may not be accessible to another. Use Minio instead.
Minio (S3-compatible)
Stores files in a Minio bucket. Compatible with any S3-compatible object store (AWS S3, Cloudflare R2, etc.).
Configuration (set by an administrator in appsettings.json or environment variables):
| Setting | Description |
|---|---|
Endpoint | Minio server address (e.g. minio:9000) |
AccessKey | Minio access key |
SecretKey | Minio secret key |
UseSsl | Whether to connect over HTTPS |
Bucket name: the tenant ID. Object path: {projectId}/{fileId}.
Viewing configured providers
Go to Settings → Project → Storage to see the storage providers configured for your project and which one is set as the default.
Using storage in workflows
Use the File Upload node to interact with storage in a workflow. It supports uploading, retrieving, deleting files, and checking existence.
Storage quota
Each project has a storage quota defined by your plan (in MB). When a workflow attempts to upload a file that would exceed the quota, the upload fails and the File Upload node is marked as failed.
Check your current usage and quota at Settings → General → Subscription.