MEATHEADS/MARKETING

All workflows

Dispatch, field work and deliveries

12 workflows in this area, grouped into 7 builds. Each one is built and has run; none of them is running for a business yet. Pick the ones that match how your office works and see what it takes to deploy.

Built · proved in test

Verify delivery stop lists against planned routes

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

When a delivery stop list is received then Flag stop list that doesn’t match planned route

Acts when the stop count diff is more than 0. Otherwise it logs that the stop counts match the planned route, and stops.

Reads
stop list id, route id, stop count, planned stop count, driver name
Evidence
Proved in test: n8n execution 1476, 12 of 20 nodes ran in 489 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 1476
  • rule does not apply — execution 1477
  • missing field halts — execution 1478

The other builds:

  • Flag shipping documents that don’t match shipment — reads document id, shipment id, document weight, shipment weight, submitted at · execution 1165, 636 ms

Found by reading the published duties of Driver/Sales Workers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Log shipment details when a delivery is completed

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

When a delivery or shipment is completed then Log completed delivery details

Acts every time the trigger fires.

Reads
delivery id, shipment id, completed at, destination address, recipient name, item count
Evidence
Proved in test: n8n execution 1285, 9 of 11 nodes ran in 319 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 1285
  • missing field halts — execution 1286

The other builds:

  • Log shipment details when packages dispatch — reads shipment id, tracking number, destination address, weight lbs · execution 1287, 432 ms
  • Schedule and track shipments through to delivery — reads shipment id, origin, destination, requested ship date, carrier name · execution 1383, 438 ms

Found by reading the published duties of Recycling Coordinators, Driver/Sales Workers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Schedule carrier delivery when order is ready

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 6.9 million people across 15 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

The other builds:

  • Send finalized order details to fulfillment team — reads order id, customer name, item summary, order total, finalized at · execution 1401, 461 ms

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

Book cargo space with carrier when shipment finalized

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

When shipment dimensions, weight, and date are finalized then Notify team to book cargo space

Acts every time the trigger fires.

Reads
shipment id, weight, cubic feet, ship date, carrier name
Evidence
Proved in test: n8n execution 1001, 11 of 18 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. 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 1001
  • missing field halts — execution 1002

The other builds:

  • Notify departments of incoming shipments automatically — reads shipment id, destination department, item description, expected arrival · execution 1309, 572 ms

Found by reading the published duties of Cargo and Freight Agents in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Log recipient and delivery details for packages

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

When a package or message is accepted for delivery then Log recipient and delivery details

Acts when the recipient address is filled in. Otherwise it logs that the package has no recipient address on file, and stops.

Reads
package id, recipient name, recipient address, recipient phone, delivery instructions
Evidence
Proved in test: n8n execution 1276, 10 of 13 nodes ran in 335 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 1276
  • rule does not apply — execution 1277
  • missing field halts — execution 1278

Found by reading the published duties of Couriers and Messengers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Deliver work assignment instructions to worker

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

When a work assignment is created or dispatched then Notify worker of new assignment

Acts every time the trigger fires.

Reads
assignment id, worker name, instructions, scheduled start, location
Evidence
Proved in test: n8n execution 1085, 11 of 18 nodes ran in 645 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 1085
  • missing field halts — execution 1086

Found by reading the published duties of Excavating and Loading Machine and Dragline Operators, Surface Mining, Automotive Body and Related Repairers in the U.S. Department of Labor’s O*NET database.

Built · proved in test

Generate a driving route to the destination

Done by about 3.9 million people across 6 job roles, several times a day.

When a destination is provided for a trip then Send generated route to driver

Acts when the destination address is filled in. Otherwise it logs that no destination address was provided for the trip, and stops.

Reads
trip id, driver id, origin address, destination address, requested at
Evidence
Proved in test: n8n execution 1191, 12 of 20 nodes ran in 421 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 1191
  • rule does not apply — execution 1192
  • missing field halts — execution 1193

Found by reading the published duties of Heavy and Tractor-Trailer Truck Drivers, Light Truck Drivers in the U.S. Department of Labor’s O*NET database.

See what fits your business