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.
Show artifact verifications
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.
Complete workflow
Inbound Artifact Verification
5 pinned recipes
Use Inbound Artifact Verification in Recued for signature, checksum, minisign, and integrity. It includes 8 built-in actions and 4 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 “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.
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 “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One artifact” in Recued. Open one artifact from the list that names it, and read everything recorded about that artifact on one page.
The board
One row per artifact, with each check as its own column. That is deliberate: a single green tick would hide which check actually carried the weight.
Status is registered (not yet checked), verified (every applicable check passed and at least one ran), or failed.
⚠ registered and failed are different things and neither means "fine". An artifact sitting at registered has had nothing done to it.
⚠ A false in a check column can mean the check did not apply. Read it with Checks — the number that actually ran. An artifact with Checks = 0 was recorded failed precisely because nothing was checked.
⚠ This is a record of a past verification, not a live one. If the file changed since, this board will not know. Re-run Verify an inbound artifact to re-check.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (15 steps)
status
trim
Trim whitespace from setting status
filter_by_status
compare
Check if status has data
all_rows
recued-core.inbound-artifact-verification.artifact.search
Search artifact on inbound artifact verification
skip: step.filter_by_status equal true
filtered_rows
recued-core.inbound-artifact-verification.artifact.search
Search artifact on inbound artifact verification
skip: step.filter_by_status equal false
rows
coalesce
Use the first available value from: filtered rows records, all rows records,
row_count
count
Count items in rows
verified_rows
filter
Filter by condition
failed_rows
filter
Filter by condition
unchecked_rows
filter
Filter by condition
verified_count
count
Count items in verified rows
failed_count
count
Count items in failed rows
unchecked_count
count
Count items in unchecked rows
board_table_rows
map
Extract from each item
board_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
▼
Output
summary
card
table
board_table
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
limit
setting
=
50
status
setting
=
Uses (1 operation)
Pack operation
Search artifact on inbound artifact verification
recued-core.inbound-artifact-verification.artifact.search
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Read
Pack
Inbound Artifact Verification
read-only
Read: artifact.search · No approval