0-CodeKit icon

0-CodeKit

A toolbox of no-code utilities

Actions40

Overview

The Storage: JSON Bin Storage operation in the 0-CodeKit n8n node provides a set of utilities to manage JSON data bins. It allows you to add, update, retrieve, delete, and list JSON objects stored as "bins" via an external service. This is useful for workflows that require temporary or persistent storage of structured data, such as caching API responses, sharing state between workflow executions, or managing small datasets without setting up a full database.

Practical examples:

  • Storing user session data between workflow runs.
  • Caching results from expensive API calls.
  • Sharing configuration or lookup tables across different parts of a workflow.

Properties

Name Meaning
Choose a JSON Bin Operation Selects the action to perform on the JSON bin. Options:
- Add a New JSON Bin
- Delete a Stored JSON Bin
- Get a JSON
- List All Your JSON Bins
- Update a JSON Bin
JSON or JSON String The JSON object or string to store or update in the bin. Required when adding or updating a bin.
Bin ID of the JSON The unique identifier of the JSON bin. Required when getting, deleting, or updating a specific bin.

Output

The output structure depends on the selected operation:

  • Add a New JSON Bin / Update a JSON Bin:
    Returns details about the created or updated bin, typically including the bin's ID and the stored JSON content.

  • Get a JSON:
    Returns the JSON object stored in the specified bin.

  • Delete a Stored JSON Bin:
    Returns a confirmation of deletion, often with the bin ID or a success message.

  • List All Your JSON Bins:
    Returns an array of metadata for all bins, such as their IDs and possibly creation/update timestamps.

Note: The output is always in the json field of each returned item.

Dependencies

  • External Service: Requires access to the CodeKit API (or a compatible backend) for storage operations.
  • API Key: You must configure the codeKitApi credential in n8n for authentication.

Troubleshooting

Common issues:

  • Missing or invalid API key:
    Error messages may indicate authentication failure. Ensure the codeKitApi credential is correctly set up in n8n.

  • Invalid Bin ID:
    If you provide a non-existent or malformed Bin ID, you may receive errors like "Bin not found" or "Invalid ID". Double-check the Bin ID value.

  • Malformed JSON input:
    When adding or updating a bin, ensure the JSON is valid. Errors may include "Invalid JSON format".

  • Insufficient permissions:
    If your API key does not have permission for certain actions, you may see "Unauthorized" or "Forbidden" errors.

How to resolve:

  • Verify credentials and permissions.
  • Check that all required fields are filled and valid.
  • Use the correct Bin ID for get, update, or delete operations.

Links and References

Discussion