Front desk, calls and lookups

Notify customers when their order status changes

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

When an order’s status changes to a new state → then Notify customer of new order status

Acts every time the trigger fires.

Reads

order id, customer contact, previous status, new status, updated at

Evidence

Proved in test: n8n execution 1307, 11 of 18 nodes ran in 550 ms.

Forward messages and work orders to recipient

Done by about 246,000 people across 3 job roles, several times a day.

When A message, work order, or complaint arrives with a named recipient → then Forward the item to recipient’s queue

Acts when the recipient name is filled in. Otherwise it logs that the item has no named recipient, and stops.

Reads

item id, item type, recipient name, recipient queue, content, received at

Evidence

Proved in test: n8n execution 1183, 12 of 20 nodes ran in 523 ms.

Answer customer questions about policies and locations

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 494,000 people across 4 job roles, several times a day.

When A customer asks about a policy, service, or location → then Send standard answer to the customer

Acts when the question topic is filled in. Otherwise it logs that the question does not name a recognized topic, and stops.

Reads

inquiry id, customer name, question topic, question text, received at

Evidence

Proved in test: n8n execution 973, 12 of 20 nodes ran in 672 ms.

Page or relay messages to the recipient

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 1.3 million people across 3 job roles, several times a day.

When message or call arrives for a specific person → then Page or relay the message to the recipient

Acts every time the trigger fires.

Reads

message id, recipient name, recipient contact, message text, received at

Evidence

Proved in test: n8n execution 1328, 11 of 18 nodes ran in 520 ms.

Send requested brochures or catalogs to customers

Done by about 1.3 million people across 2 job roles, several times a day.

When a customer requests a brochure or catalog → then Send requested brochure to customer

Acts every time the trigger fires.

Reads

request id, customer name, customer address, item requested, requested at

Evidence

Proved in test: n8n execution 1411, 11 of 18 nodes ran in 545 ms.

Verify ID or credentials at checkpoint

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

When someone presents a credential at a checkpoint → then Flag credential below required level

Acts when the level gap is less than 0. Otherwise it logs that the credential meets the required level, and stops.

Reads

credential id, checkpoint id, holder name, credential level, required level

Evidence

Proved in test: n8n execution 1479, 12 of 20 nodes ran in 445 ms.

Retrieve county land values for comparable properties

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.

When a property valuation is requested → then Retrieve county land values for comparables

Acts when the comparable count is more than 0. Otherwise it logs that no comparable properties were listed on the request, and stops.

Reads

property id, county, comparable count, requested by, request date

Evidence

Proved in test: n8n execution 1365, 10 of 13 nodes ran in 327 ms.

Notify security staff when a threat is reported

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

When A threat or security incident is reported → then Contact security staff about the threat

Acts every time the trigger fires.

Reads

report id, reporter name, location, threat description, reported at

Evidence

Proved in test: n8n execution 1312, 11 of 18 nodes ran in 650 ms.

Answer and route incoming phone calls

Done by about 4.4 million people across 2 job roles, several times a day.

When an incoming phone call rings → then Route call to requested extension

Acts when the requested extension is filled in. Otherwise it logs that the caller did not request a specific extension, and stops.

Reads

call id, caller number, requested extension, call time

Evidence

Proved in test: n8n execution 967, 12 of 20 nodes ran in 461 ms.

Record customer orders in the order system

Done by about 1.4 million people across 5 job roles, several times a day.

When a customer submits a product order → then Log the order in the order system

Acts every time the trigger fires.

Reads

order id, customer email, item name, quantity, order total

Evidence

Proved in test: n8n execution 1342, 9 of 11 nodes ran in 427 ms.

Record or look up a routine transaction entry

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

When a routine transaction needs entry or lookup → then Log the transaction entry

Acts every time the trigger fires.

Reads

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

Evidence

Proved in test: n8n execution 1350, 9 of 11 nodes ran in 421 ms.

Answer customer questions about fees and policies

Done by about 1.5 million people across 2 job roles, several times a day.

When a customer asks about a listed fee or policy → then Send the fee answer to the customer

Acts when the fee on file is true. Otherwise it logs that the fee code is not on file, and stops.

Reads

request id, customer email, fee code, fee amount, fee on file

Evidence

Proved in test: n8n execution 970, 12 of 20 nodes ran in 431 ms.

Look up and return requested information

Done by about 490,000 people across 2 job roles, several times a day.

When a request for specific information is received → then Requested information returned

Acts when the record found is true. Otherwise it logs that no matching record was found for the request, and stops.

Reads

request id, requester email, info type, record found, requested at

Evidence

Proved in test: n8n execution 1301, 12 of 20 nodes ran in 534 ms.

Connect switchboard calls to requested extensions

Done by about 38,000 people across 2 job roles, several times a day.

When a signal light indicates a call to connect → then Connect call to requested extension

Acts when the requested extension is filled in. Otherwise it logs that no extension was requested on the signal, and stops.

Reads

call id, line number, requested extension, signal time

Evidence

Proved in test: n8n execution 1065, 10 of 13 nodes ran in 325 ms.

Search property listings matching given criteria

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

When search criteria are entered for property listings → then Send matching listings to the customer

Acts when the match count is more than 0. Otherwise it logs that no listings matched the search criteria, and stops.

Reads

search id, customer email, location, max price, match count

Evidence

Proved in test: n8n execution 1390, 12 of 20 nodes ran in 488 ms.

Pull the applicant’s credit history automatically

Done by about 599,000 people across 2 job roles, daily.

When a credit check is requested for an application → then Credit history report retrieved

Acts when the credit check required is true. Otherwise it logs that the application does not require a credit check, and stops.

Reads

application id, applicant name, application type, credit check required, requested at

Evidence

Proved in test: n8n execution 1334, 10 of 13 nodes ran in 369 ms.