Use “Register an inbound artifact” in Recued. Record a file you have received so it can be verified. Keyed on its path, so re-registering the same file converges on the same row instead of creating a second one.
Register an inbound artifact
Use “Register an inbound artifact” in Recued. Record a file you have received so it can be verified. Keyed on its path, so re-registering the same file converges on the same row instead of creating a second one.
Complete workflow
Inbound Artifact Verification
4 pinned recipes
Use Inbound Artifact Verification in Recued for signature, checksum, minisign, and integrity. It includes 8 built-in actions and 3 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Verify an inbound artifact” in Recued. Run every applicable check against a file on disk — version fingerprint against the sender's published checksum, a detached Minisign signature against a public key you already hold, archive integrity, and a member listing — and record each result separately.
Use “Show artifact verifications” in Recued. List received artifacts with each check's result shown separately. It reads information without changing data in the connected service.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Registering
Record the file's path, who sent it, and what kind of file it is. Then run Verify an inbound artifact.
Archive kind decides which checks apply later:
file— a plain file. Checksum and signature only.tar— adds a member listing.tar.gz— adds a listing and a gzip integrity test.
⚠ registered means NOT YET CHECKED, and it is deliberately a different word from failed. Nothing about registering implies the file is sound.
⚠ Get the checksum and the public key from somewhere other than the artifact. A checksum shipped inside the same archive, or a key taken from the same email as the file, proves nothing — whoever altered one could alter the other. Use the sender's website, a key you exchanged previously, or a channel the sender does not control.
⚠ The path is recorded and re-checked at verify time. If the file moves, re-register it; the verify recipe refuses when the path it is given does not match the row, so a verdict can never be attributed to a different file than the one that was checked.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (19 steps)
label
trim
Trim whitespace from setting label
path
trim
Trim whitespace from setting path
supplier
trim
Trim whitespace from setting supplier
kind_trimmed
trim
Trim whitespace from setting kind
kind
lowercase
Convert kind trimmed to lowercase
digest_trimmed
trim
Trim whitespace from setting expected sha256
expected_sha256
lowercase
Convert digest trimmed to lowercase
kind_known
compare
Check if kind is one of file,tar,tar.gz
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
existing
?
existing_rows
default
Apply default
existing_count
count
Count items in existing rows
artifact_exists
compare
Check if existing count is greater than 0
artifact_create
?
skip: step.artifact_exists equal true
artifact_id
coalesce
Use the first available value from: artifact create record id, existing rows 0 id
artifact_recorded
compare
Check if artifact id has data
artifact_guard
guard
Stop if artifact recorded equals
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
kind
setting
=
file
path
setting
=
[object Object]
label
setting
=
[object Object]
supplier
setting
=
expected sha256
setting
=