Security
Checksum File
Adds each file's checksum — CRC-32, MD5 or SHA-256 — reading the files from any place the file nodes can read.
When to use it
Use it to verify downloads against a published checksum, to spot files that changed since the last run, or to find duplicate files in a folder.
In a pipeline
Input FolderChecksum FileFilter Rows
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| File path column | select | — | Default: the path an Input Folder gives |
| Algorithm | select | — | md5 |
| Output column | text | — | Checksum |
Example
Verify downloaded files
- Algorithm=SHA-256
| File Name |
|---|
| release.zip |
| File Name | Checksum |
|---|---|
| release.zip | 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08 |
Worth knowing
- Leave File path column blank to use the path an Input Folder or Google Drive list provides.
- Files are read as a stream, so large files are fine. Reading changes nothing, so previews are safe.
- A file that cannot be read gets a blank checksum and is counted in the node's note.
- Compare with a published value using Filter Rows, or with last run's output using Join.