Actions111
- Item Actions
- Webhook Actions
- Collection Actions
- File Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Extension Actions
- Field Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
The "Verify Hash" operation under the Utility resource is designed to check whether a given string matches a provided hash. This is useful in scenarios where you need to validate passwords, tokens, or any data that has been hashed for security purposes. For example, you might use this node to verify user credentials, confirm file integrity, or authenticate webhook payloads.
Properties
| Name | Meaning |
|---|---|
| String | The source string you want to verify (e.g., a password or plain text). |
| Hash | The hash value you want to compare against the source string. |
Output
- The output will be a JSON object indicating whether the provided string matches the given hash.
- Example output structure:
{ "match": true }match: A boolean value (trueorfalse) indicating if the verification was successful.
Dependencies
- No external services or API keys are required for this operation.
- No special n8n configurations or environment variables are necessary.
Troubleshooting
- Common Issues:
- If the "String" or "Hash" fields are left empty, the node may throw an error indicating missing required properties.
- If the hash algorithm used to generate the hash does not match the one expected by the node, verification will fail.
- Error Messages:
- "Missing required property 'String' or 'Hash'": Ensure both fields are filled.
- "Hash verification failed": Double-check that the hash and string correspond and that the correct hashing method was used.