Actions132
- AI Actions
- Extract Text From Document
- Check Content Policy
- Detect Adult Content
- Detect Brand
- Detect Color
- Detect Email Type
- Detect Faces
- Extract Entities
- Extract Contact Information
- Extract Customizable Information From Text
- Fuzzy Text Matcher
- Generate Image
- Generate JavaScript Code
- Generate Python Code
- Detect Language
- Detect Mood
- Extract Text From PDF
- Recognize Objects in Image
- Extract Text From Image
- Redact Sensitive Information From PDF
- Remove Background Image
- Summarize Text
- Transcribe
- Translate Text
- Image Actions
- Business Actions
- Convert Actions
- Generate Actions
- Crypto Actions
- Operator Actions
- Storage Actions
- Scheduler Actions
- Text Actions
- Chart Actions
- Code Actions
- Calculate Actions
- Date and Time Actions
- PDF Actions
- Compress PDF File
- Count PDF Pages
- Create Empty PDF
- Decrypt PDF
- Convert DOCX to PDF
- Draw Image on PDF
- Draw Text on PDF
- Encrypt PDF
- Convert HTML to PDF
- Convert Markdown to PDF
- Manage PDF Metadata
- Merge PDF Files
- Add PDF Pages
- Remove PDF Pages
- Resize PDF Pages
- Rotate PDF Pages
- Convert PDF to Base64
- Convert PDF to Image
- Split PDF File
- Add Image Watermark to PDF
- Add Text Watermark to PDF
- Shortened URL Actions
Storage → Temporary Storage
AI-generatedOverview
The node provides a utility to temporarily store binary file data. It accepts base64-encoded file content along with a filename and sends this data to a temporary storage endpoint. This is useful in workflows where you need to hold files briefly for processing, transfer, or intermediate steps without permanent storage.
Practical examples include:
- Uploading a file from one system and temporarily storing it before sending it to another service.
- Holding generated reports or images temporarily during multi-step automation.
- Passing files between nodes that require a temporary accessible location.
Properties
| Name | Meaning |
|---|---|
| File Data | Binary file data encoded as a base64 string. |
| File Name | The name of the file including its extension (e.g., "Test.txt") to preserve file type. |
Output
The node outputs JSON data representing the response from the temporary storage API after uploading the file. The exact structure depends on the external service but typically includes metadata such as a temporary URL or identifier for the stored file.
If the node supports binary data output, it would represent the stored file or a reference to it, but here the focus is on JSON response indicating successful temporary storage.
Dependencies
- Requires an API key credential for authentication with the external 0CodeKit service.
- The node makes HTTP POST requests to the
/storage/tempendpoint of the 0CodeKit API (https://prod.0codekit.com). - Proper network access and valid credentials are necessary for operation.
Troubleshooting
Common issues:
- Invalid or missing base64 file data can cause upload failures.
- Incorrect file names without extensions may lead to improper handling downstream.
- Authentication errors if the API key credential is missing or invalid.
- Network connectivity problems preventing access to the external API.
Error messages:
- Authentication errors usually indicate invalid or missing API credentials; verify and update them.
- Validation errors related to file data or file name suggest checking the input format and ensuring required fields are provided.
- HTTP errors like timeouts or 5xx responses indicate server-side or network issues; retry or check service status.
Links and References
- 0CodeKit API Documentation (for detailed API usage and endpoints)
- n8n documentation on working with binary data