0-CodeKit

Overview

The Storage → Temporary Storage operation in this custom n8n node allows you to temporarily store binary file data (such as images, documents, or any other file) by uploading it in base64 format along with a specified filename. This is useful for workflows where you need to process, transfer, or temporarily hold files between steps—such as converting formats, extracting data, or passing files to other services.

Practical examples:

• Uploading a user-submitted file for temporary processing before sending it to another service.
• Storing an image or document received from an API for further manipulation within the workflow.
• Temporarily holding a generated report or export before emailing or archiving it.

Properties

Note: There is also an "Upload Name" property, but it is only relevant for the "Permanent Storage" operation and not used in "Temporary Storage".

Output

The output will be a JSON object containing information about the result of the temporary storage operation. While the exact structure depends on the backend response, typical fields may include:

{
  "success": true,
  "fileId": "unique-temp-id",
  "fileName": "yourfilename.ext",
  "message": "File stored temporarily"
}

• success: Indicates if the operation was successful.
• fileId: A unique identifier for the temporarily stored file (used for retrieval or further actions).
• fileName: The name under which the file was stored.
• message: Status or informational message.

Note: The node does not output binary data directly; it returns metadata about the storage action.

Dependencies

• External Service: Requires access to the CodeKit API/service that handles the actual storage.
• API Key/Credentials: You must configure the codeKitApi credential in n8n for authentication.
• n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common Issues:

• Invalid Base64 Data: If the "Binary File Data" is not valid base64, the API may reject the request.
• Missing File Name: Omitting the file extension can cause issues when retrieving or using the file later.
• Authentication Errors: If the codeKitApi credential is missing or incorrect, you'll receive authentication errors.

Error Messages:

• "error: Invalid base64 string": Ensure your input is properly base64-encoded.
• "error: Missing required parameter 'fileName'": Provide a valid filename with extension.
• "401 Unauthorized": Check your API credentials in n8n.

Links and References

• n8n Documentation: Custom Nodes
• Base64 Encoding Reference
• (If available) Documentation for your specific CodeKit API instance.