0CodeKit icon

0CodeKit

A toolbox of no-code utilities

Actions108

Overview

The node provides cryptographic utilities, specifically allowing users to hash a given text message using various hashing algorithms. This operation is useful for scenarios where data integrity verification, password hashing, or generating unique identifiers from text inputs are required. For example, you might use this node to create a SHA256 hash of a user's input string to store securely or to generate an HMAC signature for API authentication.

Properties

Name Meaning
Code Variables Allows defining multiple code variables by specifying their variable name or ID and corresponding value. These variables can be used in custom code contexts within the broader node functionality (not directly related to hashing).
Message The text string that you want to hash.
Secret Key A secret key string used for HMAC-based hash types to provide keyed-hash message authentication.
Hash Type The hashing algorithm to apply on the message. Options include: MD5, SHA1, SHA3, SHA224, SHA256, SHA384, SHA512, RIPEMD160, and their HMAC variants such as HmacMD5, HmacSHA1, HmacSHA224, HmacSHA256, HmacSHA384, HmacSHA512, HmacRIPEMD160, HmacSHA3.

Output

The output JSON contains the result of the hashing operation. Typically, it will include a field with the hashed string representation of the input message according to the selected hash type. The exact structure depends on the underlying service response but generally includes the computed hash value.

This node does not output binary data; its output is textual hash strings.

Dependencies

  • Requires an API key credential for authentication with the external "0CodeKit" service.
  • The node sends requests to the "crypto/hash" endpoint of the external service to perform the hashing operation.
  • No additional environment variables are explicitly required beyond the API key credential.

Troubleshooting

  • Common issues:

    • Providing an empty or invalid message string may cause errors or unexpected results.
    • Using an HMAC hash type without supplying a valid secret key will likely fail.
    • Selecting an unsupported or misspelled hash type option could cause the request to fail.
    • Network or authentication failures with the external API service will prevent successful hashing.
  • Error messages:

    • Errors related to missing required parameters like "Message" or "Secret Key" indicate incomplete configuration.
    • Authentication errors suggest problems with the provided API key credential.
    • Unexpected response or parsing errors may occur if the external service changes its API or returns malformed data.

To resolve these issues:

  • Ensure all required fields are filled correctly.
  • Verify the API key credential is valid and has necessary permissions.
  • Confirm network connectivity to the external service.
  • Check the spelling and casing of the selected hash type.

Links and References

Discussion