Actions40
- AI Actions
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Generate Actions
- Operator Actions
- PDF Actions
- Storage Actions
Overview
This node provides permanent file storage capabilities within n8n workflows. It allows users to add, retrieve, delete, and list simple files using a remote storage service. This is useful for automating document management, archiving workflow outputs, or sharing files between different workflow executions.
Practical examples:
- Uploading generated reports or documents for later retrieval.
- Fetching previously stored files for processing or distribution.
- Deleting outdated files from storage.
- Listing all files to manage or audit stored data.
Properties
| Name | Meaning |
|---|---|
| Choose a File Storage Operation | Selects the action to perform: - Add a New File - Get a Gstored File - Delete a Stored File - List All Your Files |
| Binary File Data | (For "Add a New File") The file's binary data in base64 format. |
| File ID | (For "Get a Gstored File" or "Delete a Stored File") The unique identifier of the file. Obtainable via the "list" operation. |
| URL | (For "Get a Gstored File") Whether to return the file as a downloadable URL instead of raw data. |
Output
The output structure depends on the selected operation:
Add a New File:
Returns metadata about the newly stored file, such as its unique file ID and possibly other details like upload status.Get a Gstored File:
- If "URL" is enabled: returns a JSON object containing a URL to download the file.
- Otherwise: returns the file's content, likely as a base64 string or similar representation.
Delete a Stored File:
Returns confirmation of deletion, typically including the file ID and a success status.List All Your Files:
Returns an array of objects, each representing a stored file with properties such as file ID, name, size, and creation date.
Note: The node does not output binary data directly; file contents are handled as base64 strings or URLs.
Dependencies
- External Service: Requires access to the CodeKit API for file storage operations.
- API Key: You must configure the
codeKitApicredential in n8n for authentication.
Troubleshooting
Missing or Invalid API Key:
Error messages related to authentication failures indicate that thecodeKitApicredential is missing or incorrect. Ensure it is set up properly in n8n.File Not Found:
Attempting to get or delete a file with an invalid or non-existent File ID will result in an error. Use the "List All Your Files" operation to obtain valid IDs.Invalid Base64 Data:
When adding a new file, ensure the "Binary File Data" is correctly encoded in base64. Malformed data may cause upload errors.Unexpected Errors:
If the node encounters any error and "Continue On Fail" is enabled, the error message will be included in the output under anerrorproperty.