01
INSPECT$0
Reference pack
Three connected workflows, replay SQL, anonymous fixtures, a recovery runbook, and a rerunnable verifier.
Free to inspect. No email or upload required.
NEW TO N8N · THREE HONEST STARTING POINTS · NO PRODUCTION CREDENTIALS
Start with the
smallest useful step.
Use the free reference when you want an example, the $19 kit when you want to work through it yourself, or the $29 written review when you still do not know what to fix first.
- $0 inspect first
- $19 do it yourself
- $29 written review
- 0 credentials collected
RATE CON → DRIVER DEVICE → CLOUD ARCHIVE
Three receipts,
or one silent dispute.
This handoff is not complete when every node turns green. It is complete when the same logical load is claimed once, the dispatch reaches the intended device, and the archived record can be traced back to the exact document that was sent.
Use a sanitized workflow export and synthetic load examples. Do not send driver details, customer records, credentials, or production documents.
- 01 · Intake claimNormalize one load key and define what a duplicate Rate Con must do before any dispatch begins.
- 02 · Device receiptSeparate “API accepted” from “intended driver device received,” including timeout and retry behavior.
- 03 · Archive receiptStore a record identifier or checksum that maps the archived file to the exact dispatched document.
- 04 · Replay gateProve a rerun after a partial failure cannot send twice or archive the wrong document.
SITE RECORD → APPROVAL → INVOICE → DISPUTE RECEIPT
Verified history
needs a failure test.
A job history is reliable only when one logical work event stays linked across field evidence, approval, invoice state, and the final dispute record—even after retries, partial failures, or a corrected entry.
Use one sanitized workflow export and synthetic job examples. Do not send contractor identities, customer records, addresses, credentials, production photos, or payment data.
- 01 · Event identityDefine one stable job-event key so retries cannot create a second visit, log, approval request, or invoice action.
- 02 · Evidence receiptRecord which sanitized site artifact was accepted, rejected, or superseded without treating an upload response as proof of the business outcome.
- 03 · State handoffProve approval and invoice state refer to the same logical work event rather than a valid-looking record from another branch.
- 04 · Dispute replayReconstruct the tested chain after a partial failure while preserving corrections and preventing duplicate side effects.
TRIGGER → NORMALIZE → ACT → RECEIPT
Quote the outcome,
not an unknown build.
Define one trigger, one exact business outcome, the irreversible actions in between, and the evidence that proves completion. That is enough to choose a fixed scope without sharing a live account.
Use a sanitized node list, redacted workflow export, or synthetic payload. Do not send credentials, customer records, private URLs, production transcripts, or payment data.
- 01 · TriggerName the event that starts the process and what a duplicate or missing delivery must do.
- 02 · OutcomeState the one record, notification, document, or handoff that must be correct at the end.
- 03 · Side effectsMark every external write, send, booking, or update that cannot be repeated blindly.
- 04 · ReceiptDefine the replay-safe evidence that distinguishes accepted, completed, failed, and ambiguous states.
EVIDENCE BEFORE PAYMENT
Reference work, not a fabricated customer result.
The public Builderlog reference contains three n8n workflow JSON files, anonymous fixtures, replay SQL, an acceptance receipt, a recovery runbook, and two verifiers.
Current stored results: 41/41 structural checks and 11/11 workflow or topology cases. All three JSON files were accepted by the n8n 2.31.0 beta-line CLI importer on Node 22. This proves packet integrity and importer acceptance—not buyer production execution.
WHERE STATIC SCANNERS STOP
Inspect the graph.
Then prove the run.
A static workflow scan can flag configuration, cost, and obvious graph risks. Builderlog does not pretend that inspection proves runtime behavior. The paid scopes are for the boundary that still needs evidence after a scan.
- Concurrent duplicateTwo deliveries race before either writes its result.
- Silent triggerNo execution exists, so an execution-error workflow cannot alert.
- Ambiguous retryA timeout hides whether the irreversible side effect already happened.
- Green but wrongThe schema is valid while the workflow updates the wrong logical record.
- Acceptance receiptThe handoff preserves what was tested, what passed, and what remains buyer-specific.
CHOOSE THE DECISION YOU NEED
Inspect free →
02
ADAPT$19
Solo reliability kit
Buyer #1 receives the Pro.7 contract kit with sixteen starter cases and the finite launch update window. The next completed buyer pays $29; the six-stage ladder ends at $69.
7-day file-access support for missing, corrupt, or inaccessible listed files.
03
DECIDE$29
Beginner automation review
One anonymized task or workflow, three plain-language priority fixes, one acceptance test, and a clear next step.
Full refund if the listed report is not delivered within 24 hours of complete intake.
SAFE DELIVERY BOUNDARY
Your credentials stay with you.
Do not send passwords, private URLs, customer lists, payment information, or production records. Use a sanitized export, a redacted process brief, and synthetic examples. Builderlog delivers files and evidence; the buyer connects credentials in their own environment.
START SMALL