Actions108
- AI Actions
- Transcribe
- Detect Brand
- Extract Contact Information
- Mood Detection
- Detect Adult Content
- Enitity Detection
- Language Detection
- Too Long To Read
- Check Content Policy
- Detect Faces
- Generate Python Code
- Picture Text Recognition
- Detect Color
- Generate Image
- PDF OCR
- Translation
- Detect Email Type
- Generate Javascript Code
- Picture Object Recognition
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Date & Time Actions
- Generate Actions
- Image Actions
- Operator Actions
- PDF Actions
- Storage Actions
- Text Actions
- User Actions
Overview
The node provides a set of utilities under the "Storage" resource, specifically supporting operations for managing permanent storage of simple files. It allows users to add new files, retrieve stored files (optionally as URLs), delete files, and list all stored files. This is useful in scenarios where workflows need to persist files beyond temporary execution, such as saving generated reports, images, or documents for later retrieval or sharing.
Practical examples:
- Uploading a generated PDF report to permanent storage for archival.
- Retrieving a stored image file by its ID to send it via email.
- Deleting outdated files from storage to free up space.
- Listing all stored files to display available resources or manage them programmatically.
Properties
| Name | Meaning |
|---|---|
Choose a File Storage Operation (permfilesop) |
The action to perform on permanent storage files. Options: "Add a New File", "Get a Stored File", "Delete a Stored File", "List All Your Files". |
Binary File Data (fileBuffer) |
Base64 encoded binary data of the file to be added. Required when adding a new file. |
File ID (fileId) |
Identifier of the file to get or delete. Can be obtained from the "List All Your Files" operation. Required for "get" and "del" operations. |
URL (getAsUrl) |
Boolean flag indicating whether to retrieve the stored file as a URL instead of raw data. Applicable only for the "get" operation. Defaults to false. |
Code Variables (codeVariablesUi) |
A collection of code variables that can be defined with a variable name or ID and a corresponding value. These variables are linked to code editor functions and can be used to pass dynamic values during execution. |
Output
The node outputs a JSON array containing the results of the performed operation:
- For Add a New File: The output will typically include metadata about the newly stored file, such as its assigned file ID and possibly other attributes confirming successful upload.
- For Get a Stored File: The output contains the file data either as raw content or as a URL if requested.
- For Delete a Stored File: The output confirms deletion status.
- For List All Your Files: The output is an array listing all files currently stored, including their IDs and metadata.
If the node handles binary data, it expects base64-encoded input for uploads but does not explicitly output binary data; instead, it may provide URLs or JSON metadata.
Dependencies
- Requires an API key credential for authentication with the external service providing the storage functionality.
- The node depends on an external API endpoint structured as
storage/perm/{operation}, where{operation}corresponds to the chosen file storage operation. - No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Common Issues:
- Providing invalid or missing file IDs when attempting to get or delete files will result in errors.
- Uploading improperly base64-encoded file data will cause failures during the "add" operation.
- Requesting a file as a URL when the service does not support URL generation for that file type may lead to unexpected results or errors.
- Error Messages:
- Errors related to authentication usually indicate missing or invalid API credentials.
- "File not found" errors occur if the specified file ID does not exist.
- Malformed input errors may arise if required parameters like
fileBufferorfileIdare missing or incorrectly formatted.
- Resolutions:
- Verify API credentials are correctly configured.
- Use the "list" operation to confirm valid file IDs before "get" or "del".
- Ensure file data is properly base64 encoded before uploading.
Links and References
- n8n Expressions Documentation — for using expressions in variable names or IDs.
- Refer to the external service's API documentation for detailed information on file storage endpoints and supported operations (not included in the source).