Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Records runtime compatibility canary
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
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 “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 “One artifact” in Recued. Open one artifact from the list that names it, and read everything recorded about that artifact on one page.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (1 steps)
require_runtime
core.records.require-runtime
Require runtime records
Uses (1 operation)
Pack operation
Require runtime records
core.records.require-runtime