Customer records and data accuracy

Flag transaction records with mismatched data

Done by about 6.1 million people across 17 job roles, several times a day.

When a financial transaction record is submitted → then Flag the transaction for review

Acts when the amount variance is more than 0. Otherwise it logs that the recorded amount matches the expected amount, and stops.

Reads

transaction id, recorded amount, expected amount, account name, submitted at

Evidence

Proved in test: n8n execution 1174, 12 of 20 nodes ran in 649 ms.

Flag records that don’t match source data

Done by about 4.9 million people across 12 job roles, several times a day.

When a record is submitted or updated → then Flag record for accuracy review

Acts when the values match is False. Otherwise it logs that the record’s fields match the source data, and stops.

Reads

record id, field value, source value, reviewed by, reviewed at

Evidence

Proved in test: n8n execution 1159, 12 of 20 nodes ran in 549 ms.

Flag data entries that don’t match source

Done by about 3.2 million people across 9 job roles, several times a day.

When a data record is entered or updated → then Flag entry for source mismatch

Acts when the values match is False. Otherwise it logs that the recorded value matches the source document, and stops.

Reads

record id, recorded value, source value, entered by, entered at

Evidence

Proved in test: n8n execution 1141, 12 of 20 nodes ran in 629 ms.

Flag calculations that don’t match expected results

Done by about 270,000 people across 5 job roles, several times a day.

When a calculation is submitted for review → then Flag calculation for review

Acts when the value variance is more than 0. Otherwise it logs that the computed result matches the expected value, and stops.

Reads

calculation id, computed value, expected value, submitted by, submitted at

Evidence

Proved in test: n8n execution 1135, 12 of 20 nodes ran in 532 ms.

Update customer record when new info arrives

2 builds of this one. The same workflow, fitted to what each business calls it and the field it checks — listed in the teardown below.

Done by about 936,000 people across 8 job roles, several times a day.

When new customer information is received → then Log the updated contact info on the record

Acts when the email matches is False. Otherwise it logs that the email already matches what’s on file, and stops.

Reads

customer id, submitted email, record email, submitted at, customer name

Evidence

Proved in test: n8n execution 1445, 10 of 13 nodes ran in 335 ms.

Update customer account records after transactions

Done by about 1.6 million people across 3 job roles, several times a day.

When a customer account transaction occurs → then Log transaction to account record

Acts every time the trigger fires.

Reads

account id, transaction id, transaction amount, transaction type, transaction date

Evidence

Proved in test: n8n execution 1443, 9 of 11 nodes ran in 333 ms.

Log completed service to customer file

Done by about 1.6 million people across 11 job roles, several times a day.

When a service for a customer is completed → then Log service to customer file

Acts every time the trigger fires.

Reads

service id, customer id, service type, completed at, duration minutes, notes

Evidence

Proved in test: n8n execution 1236, 9 of 11 nodes ran in 324 ms.

Update database record with corrected information

Done by about 816,000 people across 4 job roles, several times a day.

When new or corrected information arrives for a record → then Update the database field

Acts when the values match is False. Otherwise it logs that the current and new values already match, and stops.

Reads

record id, field name, current value, new value, source system, received at

Evidence

Proved in test: n8n execution 1448, 10 of 13 nodes ran in 430 ms.

Flag employee records that don’t match source data

Done by about 153,000 people across 1 job role, daily.

When employee information is submitted or updated → then Flag mismatched employee record

Acts when the value match is False. Otherwise it logs that the submitted value matches the source of record, and stops.

Reads

employee id, field name, submitted value, source value, submitted at

Evidence

Proved in test: n8n execution 1144, 12 of 20 nodes ran in 531 ms.

Update case records when status changes

Done by about 155,000 people across 1 job role, several times a day.

When an assigned case’s status changes → then Record the case status change

Acts when the status same is False. Otherwise it logs that the status has not changed since the last update, and stops.

Reads

case id, previous status, new status, status changed at, assigned to

Evidence

Proved in test: n8n execution 1437, 10 of 13 nodes ran in 334 ms.

Create customer record when enrollment form is submitted

Done by about 526,000 people across 5 job roles, daily.

When customer submits an enrollment or registration form → then Create registration record

Acts every time the trigger fires.

Reads

form id, customer id, program id, submitted at, registration status

Evidence

Proved in test: n8n execution 1077, 9 of 11 nodes ran in 358 ms.

Enter final grades into the official gradebook

Done by about 155,000 people across 5 job roles, daily.

When A final grade is determined for a course → then Enter grade into gradebook

Acts every time the trigger fires.

Reads

grade record id, customer id, course id, final grade, graded at

Evidence

Proved in test: n8n execution 1098, 9 of 11 nodes ran in 335 ms.

Update contact record when new info arrives

Done by about 66,000 people across 1 job role, more than weekly.

When new or updated contact information is received → then Record the updated contact field

Acts when the values match is False. Otherwise it logs that the submitted value matches what’s on file, and stops.

Reads

contact id, field changed, new value, previous value, received at

Evidence

Proved in test: n8n execution 1440, 10 of 13 nodes ran in 342 ms.