Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
The node provides a utility operation to generate a hash from a given input string. This is useful in scenarios where you need to create unique identifiers, checksums, or securely store hashed versions of sensitive data such as passwords or tokens. For example, you might use this node to hash user input before saving it to a database or to verify data integrity by comparing hashes.
Properties
| Name | Meaning |
|---|---|
| String | The input string to hash |
Output
The output contains a JSON field with the generated hash value corresponding to the input string. The exact structure typically includes a key holding the hash result (e.g., hash), which can then be used in subsequent workflow steps. There is no indication that binary data is outputted.
Dependencies
- No external services or API keys are required for this operation.
- The hashing logic is implemented internally within the node's codebase.
Troubleshooting
- Empty Input: If the input string is empty or missing, the node may throw an error or return an empty hash. Ensure the "String" property is provided and not empty.
- Unsupported Characters: If the input string contains unusual or non-UTF characters, verify that the hashing function supports them or sanitize input accordingly.
- Unexpected Output: If the output hash does not match expectations, confirm the hashing algorithm used and ensure consistent input formatting.
Links and References
- General information on hashing algorithms: https://en.wikipedia.org/wiki/Cryptographic_hash_function
- Common use cases for hashing in workflows: https://n8n.io/integrations/builtin/n8n-nodes-base.utility