File Upload
Reads, writes, and manages files in a configured storage provider. Supports uploading, retrieving, deleting, and checking existence.
Properties
| Property | Required | Description |
|---|---|---|
| Storage Provider | Yes | The storage backend to use. Populated from your project's configured providers |
| Operation | Yes | The action to perform |
Additional fields appear depending on the selected operation.
Operations
Store (upload)
Saves a file to storage.
| Field | Required | Description |
|---|---|---|
| File | Yes | The binary file to upload. Accepts output from a Webhook Trigger file attachment or another File Upload node |
Output: A BinaryRef — a reference identifier for the stored file. Pass this to downstream nodes that need to access the file.
Retrieve
Loads a reference to an existing file.
| Field | Required | Description |
|---|---|---|
| File Reference | Yes | A BinaryRef identifying the file to retrieve |
Output: The BinaryRef is passed downstream, where it can be used in the HTTP Request node's Binary body or another File Upload operation.
Delete
Removes a file from storage.
| Field | Required | Description |
|---|---|---|
| File Reference | Yes | A BinaryRef identifying the file to delete |
Exists
Checks whether a file exists in storage.
| Field | Required | Description |
|---|---|---|
| File Reference | Yes | A BinaryRef to check |
Output ports: true if the file exists; false if it does not.
Output ports
All operations route to either the true port (success) or the false port (failure), except Exists which uses them to indicate whether the file was found.
Storage providers
Storage providers are configured by an administrator under Settings → Project → Storage. The dropdown in this node is populated automatically from those configured providers. See Storage for details.
Plan limits
Each plan includes a storage quota (in MB) per project. Uploads that would exceed the quota are rejected.