Your automation had a plan. What did the records actually show?
A draft acceptance test is not a passing test. Compare your proposed criteria with the source, workflow execution and destination receipt snapshots you actually have. This lab runs four existing local tool blocks in one sequence and exports a redacted review of what still needs human verification.
Six proposed scenarios, no automatic sign-off.
Repeated delivery observations versus merchant events.
Source, execution and receipt evidence.
Fixed next checks without raw identifiers.
One local review, not another disconnected spreadsheet
Start with the fictional example, or paste the Automation Acceptance JSON you already downloaded. Paste authorized, pseudonymous CSV snapshots or select local UTF-8 .csv files below; either way, data remains in your browser. No Shopify, n8n or CRM account is accessed. The analysis runs entirely in your browser; it cannot access Shopify, n8n or a CRM account.
Accepts the exported moruneva.automation-acceptance.v1 draft, or its plain 13-field scope object. Unsupported approval claims and mismatches in generated checks are rejected. The original text is not cryptographically authenticated.
delivery_id,event_id,topic
event_id,execution_id,status
event_id,receipt_id
An authorized source snapshot, not presumed complete
No live account access. Use invented or explicitly authorized pseudonymous records.
What you get — and what you still cannot conclude
All six acceptance scenarios receive an observation signal and a specific missing-proof question. None is automatically marked accepted or passed. The export contains only approved categories, source row counts, missing field names and fixed next checks. In contrast, the original Acceptance Builder's JSON contains your plan descriptions; do not share it casually.
Even perfectly matching identifiers cannot prove the actual CRM object is correct, the time window is complete, the customer authorized the work or the client approved release. Never use these aggregates to replay a payment, issue a refund or delete an order.
For authoritative verification, inspect Shopify's delivery troubleshooting, n8n's execution history, and the final destination system you are authorized to inspect. Native dashboards and a spreadsheet may be sufficient for one-off work.
Read the original worked example → · Need an incident-only view? → · Privacy and limits →
Help test whether this saves real work
After using the same authorized, pseudonymous case in your usual dashboard or spreadsheet and in this free workbench, compare how many minutes each approach took. Record what you still had to verify manually. A faster first attempt alone does not prove reliable outcomes or recurring value.
Share optional, privacy-safe field feedback by email → Your email app opens a draft; nothing is sent automatically. Do not attach source files, customer identifiers, credentials or confidential client information. No tracking or customer upload is added to this page. Read the privacy notice.