Missing
Expected source record: source-missing
Matching destination ids: None
Match count: 0
No destination match found.
Independent post-execution verification of automation outcomes
OutcomeDelta
Synthetic Demo
Meta Lead Ads → n8n → HubSpot
This demo uses synthetic records and does not connect to Meta, n8n, or HubSpot.
Scenario Summary
Source records6
Destination records6
Reconciliation window5 minutes
Matching rulelead_id → external_lead_id
Asserted fieldsemail, first_name, campaign
Source → Destination Comparison
SOURCE DATA
| id | occurredAt | lead_id | first_name | campaign | |
|---|---|---|---|---|---|
| source-clean-1 | 2026-01-15T10:00:00.000Z | lead-clean-1 | clean.one@example.com | Avery | Spring Preview |
| source-missing | 2026-01-15T10:01:00.000Z | lead-missing | missing@example.com | Blake | Spring Preview |
| source-duplicate | 2026-01-15T10:02:00.000Z | lead-duplicate | duplicate@example.com | Casey | Spring Preview |
| source-field-mismatch | 2026-01-15T10:03:00.000Z | lead-field-mismatch | mismatch@example.com | Devon | Spring Preview |
| source-delayed | 2026-01-15T10:04:00.000Z | lead-delayed | delayed@example.com | Emery | Spring Preview |
| source-clean-2 | 2026-01-15T10:05:00.000Z | lead-clean-2 | clean.two@example.com | Finley | Spring Preview |
DESTINATION DATA
| id | occurredAt | external_lead_id | first_name | campaign | |
|---|---|---|---|---|---|
| destination-clean-1 | 2026-01-15T10:01:00.000Z | lead-clean-1 | clean.one@example.com | Avery | Spring Preview |
| destination-duplicate-a | 2026-01-15T10:03:00.000Z | lead-duplicate | duplicate@example.com | Casey | Spring Preview |
| destination-duplicate-b | 2026-01-15T10:04:00.000Z | lead-duplicate | duplicate@example.com | Casey | Spring Preview |
| destination-field-mismatch | 2026-01-15T10:04:00.000Z | lead-field-mismatch | observed-mismatch@example.com | Devon | Spring Preview |
| destination-delayed | 2026-01-15T10:10:00.000Z | lead-delayed | delayed@example.com | Emery | Spring Preview |
| destination-clean-2 | 2026-01-15T10:06:00.000Z | lead-clean-2 | clean.two@example.com | Finley | Spring Preview |
Ready to reconcile
Click “Run Reconciliation” to compare the source and destination records.
Reconciliation Overview
OutcomeDelta compared 6 expected source records with 6 observed CRM records and found 4 business-outcome discrepancies.
A successful workflow run is not proof that the expected business state exists downstream.
Clean2
Missing1
Duplicate1
Field Mismatch1
Delayed1
Detected Discrepancies
Duplicate
Expected source record: source-duplicate
Matching destination ids: destination-duplicate-a, destination-duplicate-b
Match count: 2
Field Mismatch
Expected source record: source-field-mismatch
Matching destination ids: destination-field-mismatch
Match count: 1
email: mismatch@example.com →email: observed-mismatch@example.com (source absent: false; destination absent: false)
Delayed
Expected source record: source-delayed
Matching destination ids: destination-delayed
Match count: 1
Source timestamp: 2026-01-15T10:04:00.000Z
Destination timestamp: 2026-01-15T10:10:00.000Z
Actual delay: 6 minutes (360000 ms)
Allowed delay: 5 minutes (300000 ms)
Would this catch something you currently check manually?
OutcomeDelta is an early validation prototype. We’re looking for automation agencies and consultants who manage real client workflows and want to test independent source-to-destination reconciliation.
Test OutcomeDelta on one of my workflowsPrototype validation
For prototype testing, please do not send production credentials or sensitive customer data. If we test your dataset later, we’ll initially ask for anonymized or synthetic exports only.