MEATHEADS/MARKETING

All job roles

Digital Forensics Analysts

10 of these workflows come from what this role does day to day. The whole role accounts for 12.0% 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

Log hardware benchmark results against spec threshold

Done by about 1.8 million people across 6 job roles, daily.

When a hardware performance test finishes running then Log benchmark result against spec threshold

Acts every time the trigger fires.

Reads
test id, device id, benchmark score, spec threshold, test type
Evidence
Proved in test: n8n execution 1258, 9 of 11 nodes ran in 352 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 1258
  • missing field halts — execution 1259

Found by reading the published duties of Computer Network Support Specialists, Computer User Support Specialists in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Retrieve the matching record on request

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

When a request for specific information is received then Deliver requested record

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

Reads
request id, requester name, record reference, record found, requested at
Evidence
Proved in test: n8n execution 1374, 12 of 20 nodes ran in 526 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 1374
  • rule does not apply — execution 1375
  • missing field halts — execution 1376

Found by reading the published duties of Penetration Testers, Bioinformatics Technicians in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Publish submitted content updates to the website

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

When updated content is submitted for the website then Publish the submitted content to the page

Acts every time the trigger fires.

Reads
page id, content, submitted by, submission id, submitted at
Evidence
Proved in test: n8n execution 1332, 9 of 11 nodes ran in 454 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 1332
  • missing field halts — execution 1333

Found by reading the published duties of Web Developers, Web and Digital Interface Designers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

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.
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 1448
  • rule does not apply — execution 1449
  • missing field halts — execution 1450

Found by reading the published duties of Appraisers of Personal and Business Property, Database Administrators in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Convert GIS files to the needed format

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

When a data file needs to be in a different format then Log GIS file converted to target format

Acts when the format match is False. Otherwise it logs that the file is already in the required format, and stops.

Reads
file id, current format, target format, file size mb
Evidence
Proved in test: n8n execution 1071, 10 of 13 nodes ran in 311 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 1071
  • rule does not apply — execution 1072
  • missing field halts — execution 1073

Found by reading the published duties of Geographic Information Systems Technologists and Technicians in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Alert team when system performance drops

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

When a system performance metric reading is recorded then Flag the performance anomaly to the systems team

Acts when the value over threshold is more than 0. Otherwise it logs that the metric is within its normal threshold, and stops.

Reads
metric id, metric name, system id, metric value, threshold
Evidence
Proved in test: n8n execution 961, 12 of 20 nodes ran in 429 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 961
  • rule does not apply — execution 962
  • missing field halts — execution 963

Found by reading the published duties of Computer Systems Analysts, Computer User Support Specialists in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Install the requested software package automatically

Done by about 2.8 million people across 10 job roles, several times a day.

When a software package install is requested for a target machine then Install package on target machine

Acts when the license available is true. Otherwise it logs that no license seat is available, and stops.

Reads
request id, package name, target machine, license available, requested by, requested at
Evidence
Proved in test: n8n execution 1214, 10 of 13 nodes ran in 449 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 1214
  • rule does not apply — execution 1215
  • missing field halts — execution 1216

Found by reading the published duties of Health Informatics Specialists, Computer Network Support Specialists in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Alert security team to suspicious activity

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

When a security monitoring rule detects an anomalous event then Flag the suspicious event to the security team

Acts every time the trigger fires.

Reads
event id, rule name, source ip, detected at, severity
Evidence
Proved in test: n8n execution 959, 11 of 18 nodes ran in 459 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 959
  • missing field halts — execution 960

Found by reading the published duties of Information Security Analysts, Web Developers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Back up data automatically on a schedule

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

On a schedule Every day at 2am then Backup copy created

Acts every time the trigger fires.

Reads
system name, data source, scheduled time, backup size mb, destination path
Evidence
Proved in test: n8n execution 993, 9 of 11 nodes ran in 334 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 993
  • missing field halts — execution 994

Found by reading the published duties of Computer Network Support Specialists, Telecommunications Engineering Specialists in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Flag project milestones as on-schedule or delayed

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

On a schedule Runs daily to check milestones whose due date passed then Flag the milestone as delayed past its due date

Acts when the completed is False. Otherwise it logs that the milestone was completed by its due date, and stops.

Reads
milestone id, project id, milestone name, due date, completed
Evidence
Proved in test: n8n execution 1156, 12 of 20 nodes ran in 540 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 1156
  • rule does not apply — execution 1157
  • missing field halts — execution 1158

Found by reading the published duties of Information Technology Project Managers in the U.S. Department of Labor’s O*NET database.

See what fits your business