Package automation output before handing it to another person
LOCAL EXPORT COMPATIBILITY · NOT A MANAGED CONNECTOR
An automation can produce a file whose exact output becomes unclear after later edits.
Try it
Pass completed output bytes from your existing automation to importExport. Choose UDS for a snapshot, verify it immediately, and distribute the browser-ready copy through a channel you authorize. A later output can be packaged separately and compared by source hash. The comparison explicitly does not prove a parent-child revision chain. If a webhook is part of your own system, validate it there before passing bytes into this local adapter.
node packages/udify/src/cli.mjs import automation-output source-file result.uds UDS node packages/udify/src/cli.mjs verify result.uds
Limits
No public webhook receiver, workflow hosting or automatic sending is activated. The adapter does not authenticate the producing system.
Does comparison prove which output came first?
No. Device time is self-declared; this comparison reports byte and metadata differences, not trusted chronology.