You will know every intended record reached its destination only by reconciling a defined source set against destination evidence. A successful-run label is not a substitute for checking identifiers, expected values and unresolved exceptions.
Define what belongs in the comparison
n8n describes workflows as connected nodes and includes executions among its core workflow topics. Execution evidence can support investigation, but completeness is a separate acceptance question for your process.
As editorial advice, define the source boundary before running the comparison: an explicit batch, a fixed identifier list or a clearly specified time window. For an Indian team using daily reports, state the cutoff in IST and clarify how later changes will be treated.
Also define legitimate exclusions. A record rejected because a required field is missing should remain visible as an exception, not silently disappear from the expected total.
Create a source-to-destination reconciliation sheet
Use these fields for each batch:
- Batch identifier and source cutoff.
- Number of source records in scope.
- Source identifiers expected at the destination.
- Identifiers confirmed present exactly once.
- Missing identifiers.
- Duplicate identifiers.
- Records present with incorrect required values.
- Explicit exclusions and reasons.
- Unresolved exceptions, owners and review deadlines.
Keep totals alongside identifier-level evidence. Counting rows alone cannot distinguish one missing record from an extra copy of another. If the destination uses different identifiers, define and verify the mapping rather than relying on names or row positions.
Evaluate a hypothetical eight-record transfer
Suppose a hypothetical Indore training team sends synthetic records TEST-301 through TEST-308 to a test register. The destination contains eight rows, but TEST-304 is absent and TEST-306 appears twice.
A count-only check passes incorrectly. Identifier reconciliation reports seven unique expected records present, one missing identifier and one duplicate row.
Now suppose TEST-308 has the wrong course code. Presence checking alone also misses that error, so include the course code in this example’s required-value comparison.
Evaluate the transfer against three rules: every expected identifier is present, each appears once, and each required value matches the agreed transformation. The batch remains unresolved until missing, duplicate and incorrect-value exceptions are addressed or explicitly accepted by the responsible owner.
Close exceptions rather than hiding them
Stop downstream reporting if unresolved differences could change the reported result. Next, investigate each exception using the available run and destination evidence before deciding whether a replay is safe.
If comparing access through the automation catalog, check access format and save terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence or data-delivery guarantees.
Sources and scope
Source material checked 29 October 2026; features/policies may change. The n8n workflow documentation establishes the workflow model and execution topics. The reconciliation sheet and hypothetical acceptance rules are editorial advice, not built-in reporting claims.