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 versatile toolbox of no-code utilities grouped by various resources and operations. Specifically, for the Storage resource with the Temporary Storage operation, it allows users to upload binary file data temporarily. This is useful in workflows where files need to be stored transiently for processing or passing between nodes without permanent storage.
Common scenarios include:
- Temporarily storing an uploaded file before further processing (e.g., image manipulation, PDF conversion).
- Passing binary data between workflow steps without saving it permanently.
- Quickly caching files during multi-step automation.
Example: Uploading a base64-encoded text file named "Test.txt" to temporary storage so that subsequent nodes can access or manipulate it.
Properties
| Name | Meaning |
|---|---|
| Code Variables | A collection of code variables defined in the code editor for selected functions. Users can select variable names or IDs and assign string values to them. Useful for dynamic scripting within the node. |
| Binary File Data | The binary file content encoded as a base64 string. This is the actual file data to be stored temporarily. |
| File Name | The name of the file being uploaded. Important to include the file extension to preserve the file type (e.g., .txt, .jpg). |
| Upload Name | Similar to File Name but used specifically when adding files in permanent storage operations (not applicable for temporary storage). |
Note: For the Temporary Storage operation under Storage resource, the relevant properties are Binary File Data and File Name.
Output
The node outputs JSON data representing the result of the storage operation. For temporary storage, this typically includes metadata about the stored file such as an identifier or confirmation of successful upload.
If the node handles binary data, the output may also include references or IDs to access the stored binary content in subsequent workflow steps.
Dependencies
- Requires an API key credential for authentication to the external service providing the storage functionality.
- The node depends on an external API endpoint structured as
storage/tempfor temporary file uploads. - No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Issue: Upload fails due to missing or invalid binary data.
- Resolution: Ensure the binary file data is correctly base64 encoded and provided in the "Binary File Data" property.
- Issue: File type not preserved after upload.
- Resolution: Include the correct file extension in the "File Name" property.
- Error: Authentication errors.
- Resolution: Verify that the API key credential is correctly configured and has necessary permissions.
- Error: Unexpected response or empty output.
- Resolution: Check network connectivity and API service status; ensure input parameters match expected formats.
Links and References
- n8n Expressions Documentation — for using expressions in variable names.
- General API documentation for the external service (not included in source) would provide details on storage endpoints and usage.