Data flow architecture between Recruiting, TruxFlow, and Dispatch
RECRUITING TRUXFLOW DISPATCH
────────── ─────── ────────
Driver Apps ──────────────► Driver ──────────────► Drivers Base
(7.4.) /onboard + Docs (2.1.)
│
├─────────► Truck ──────────────► Units Base
│ + Docs (2.2.)
│
└─────────► Trailer ──────────────► Trailers Base
+ Docs (2.5.)
REVERSE SYNC (Dispatch → TruxFlow):
Units Base ──────────────► Truck.status
(Status-Unit /truck/ Driver.operationStatus
Operation) operation
Units Base ──────────────► Truck.dispatchStatus
(Dispatch /truck/ Driver.dispatchStatus
Status) dispatch
POST /api/webhooks/airtable/onboard
Creates:
├── Driver (with CDL, medical dates)
├── Contractor (via getContractorDataFromDriver)
├── Truck (if unitNumber provided)
└── Trailer (if trailerNumber provided)
Links:
├── Driver → Truck (truckAssignment)
├── Trailer → Truck (trailerAssignment)
└── Truck.owner → Contractor
Creates:
└── Driver only
Notes:
├── No truck (uses company truck)
└── No contractor needed
Creates:
├── Contractor (from Owner* fields)
├── Truck (if unitNumber provided)
└── Trailer (if trailerNumber provided)
Links:
├── Trailer → Truck (trailerAssignment)
└── Truck.owner → Contractor
Notes:
└── No Driver (owns equipment only)
dispatchStatus - Set by dispatchersoperationStatus - Cascades from truckStatus-Unit Operation - Truck status| Airtable Status | TruxFlow Truck |
|---|---|
| Active | OPERATING |
| InActive | NOT_OPERATING |
| Approved Off | TIME_OFF |
| Broken Down | BROKE_DOWN |
| Situation | SITUATION |
| Home Time | TIME_OFF |
| Airtable Status | Driver Operation |
|---|---|
| Active | On Duty |
| InActive | Not Available |
| Approved Off | Approved Off |
| Broken Down | Broken Down |
| Home Time | Home Time |
recordId → Record ID from trigger/root/airtable-onboard-script.jsSECRET, ORG_ID