MEATHEADS/MARKETING

All job roles

Solar Sales Representatives and Assessors

6 of these workflows come from what this role does day to day. The whole role accounts for 13.6% of its rated work in fixed-rule activities, measured by the U.S. Department of Labor’s own importance and frequency ratings — the rest of the job needs judgment or a person. Nothing here replaces anybody; it takes the repetitive part off their desk.

Built · proved in test

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.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Applies?
  8. Notify Owner
  9. Pair Result
  10. Delivered?
  11. Wait Before Retry
  12. Retry (once)
  13. Pair Retry Result
  14. Retry Delivered?
  15. Record Seen
  16. Log: Done
  17. Log: Missing Fields
  18. Log: Duplicate
  19. Log: Not Applicable
  20. Log: Delivery Failed

Checked in test:

  • acts on it — execution 1159
  • rule does not apply — execution 1160
  • missing field halts — execution 1161

Found by reading the published duties of Compliance Managers, Claims Adjusters, Examiners, and Investigators in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Schedule carrier delivery when order is ready

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

When an order is marked ready for delivery then Notify team to schedule carrier delivery

Acts every time the trigger fires.

Reads
order id, ready at, delivery address, requested delivery date
Evidence
Proved in test: n8n execution 1385, 11 of 18 nodes ran in 455 ms.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Notify Owner
  8. Pair Result
  9. Delivered?
  10. Wait Before Retry
  11. Retry (once)
  12. Pair Retry Result
  13. Retry Delivered?
  14. Record Seen
  15. Log: Done
  16. Log: Missing Fields
  17. Log: Duplicate
  18. Log: Delivery Failed

Checked in test:

  • acts on it — execution 1385
  • missing field halts — execution 1386

Found by reading the published duties of Floral Designers, Pharmacy Technicians in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Flag credit applications that mismatch bureau records

Done by about 1.7 million people across 4 job roles, several times a day.

When a customer submits a credit application then Flag credit application for bureau mismatch

Acts when the score mismatch is more than 0. Otherwise it logs that the reported score matches bureau records, and stops.

Reads
application id, customer name, reported credit score, bureau credit score, submitted at
Evidence
Proved in test: n8n execution 1138, 12 of 20 nodes ran in 612 ms.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Applies?
  8. Notify Owner
  9. Pair Result
  10. Delivered?
  11. Wait Before Retry
  12. Retry (once)
  13. Pair Retry Result
  14. Retry Delivered?
  15. Record Seen
  16. Log: Done
  17. Log: Missing Fields
  18. Log: Duplicate
  19. Log: Not Applicable
  20. Log: Delivery Failed

Checked in test:

  • acts on it — execution 1138
  • rule does not apply — execution 1139
  • missing field halts — execution 1140

Found by reading the published duties of Gambling Change Persons and Booth Cashiers, Sales Representatives, Wholesale and Manufacturing, Technical and Scientific Products in the U.S. Department of Labor’s O*NET database.

Built · proved in test

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.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Store Record
  8. Record Seen
  9. Log: Done
  10. Log: Missing Fields
  11. Log: Duplicate

Checked in test:

  • acts on it — execution 1342
  • missing field halts — execution 1343

Found by reading the published duties of Counter and Rental Clerks, Parts Salespersons in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Log completed transactions in the sales record

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

When a sales transaction is completed then Log completed transaction in sales record

Acts when the payment confirmed is true. Otherwise it logs that the payment has not been confirmed yet, and stops.

Reads
transaction id, customer name, amount, payment confirmed, transaction date
Evidence
Proved in test: n8n execution 1241, 10 of 13 nodes ran in 440 ms.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Applies?
  8. Store Record
  9. Record Seen
  10. Log: Done
  11. Log: Missing Fields
  12. Log: Duplicate
  13. Log: Not Applicable

Checked in test:

  • acts on it — execution 1241
  • rule does not apply — execution 1242
  • missing field halts — execution 1243

Found by reading the published duties of First-Line Supervisors of Retail Sales Workers, First-Line Supervisors of Non-Retail Sales Workers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

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.
What it does, step by step
  1. Trigger
  2. Normalize
  3. Required Fields?
  4. Load Recent
  5. Dedupe Gate
  6. First Time?
  7. Store Record
  8. Record Seen
  9. Log: Done
  10. Log: Missing Fields
  11. Log: Duplicate

Checked in test:

  • acts on it — execution 1443
  • missing field halts — execution 1444

Found by reading the published duties of Sales Representatives of Services, Except Advertising, Insurance, Financial Services, and Travel, Sales Representatives, Wholesale and Manufacturing, Technical and Scientific Products in the U.S. Department of Labor’s O*NET database.

See what fits your business