Logistics — dispatch + delay alerts
Assign incoming jobs to drivers and alert on at-risk deliveries.
This is an illustrative scenario, not a real customer. The numbers and narrative below are a worked example of how this process would run on G8 — accurate to the product, but not a measured case study.
00 / Before and after
Before — manual
A dispatcher watches a tracking dashboard and a shared inbox at the same time, assigns jobs by gut feel, and only notices delays once a customer calls to complain. Nights and weekends are blind spots.
After — on G8
Each inbound event runs the flow: it picks an eligible driver, sends the assignment, and watches the ETA. When a delivery crosses the delay threshold, it raises an alert to the ops channel automatically.
01 / The G8 lifecycle, applied
From description to running flow
- 01 / Blueprint
Describe dispatch and escalation
Ops describes the process: on a new job, select an available driver and notify them; on a status update, compare ETA to the promised window and escalate if it slips. G8 compiles the Blueprint.
- 02 / Contract
Bound assignment and alerting
The contract allows sending assignments and posting delay alerts, blocks any change to pricing or billing, and requires approval before reassigning a job that is already in transit.
- 03 / Simulate
Replay events safely
Simulation replays sample job and tracking events and shows which driver would be picked and which alerts would fire — with nothing actually sent — so ops can sanity-check the logic.
- 04 / Run
React to events in real time
Live, the webhook trigger runs the flow per event. Routine assignments execute straight through; an in-transit reassignment pauses for an approval before it changes anything.
- 05 / Monitor
See errors and waits at a glance
Monitor surfaces failed runs and any run waiting on a human, so a stuck reassignment or a connector error is visible immediately rather than discovered by a customer call.
02 / Connectors and approvals
Connectors used
- TelegramSend the job assignment to the driver.
- SlackRaise a delay alert in the operations channel.
- HTTPRead tracking status and ETAs from the carrier API.
Approvals and blocks
- Reassigning a job that is already in transit is approval-required.
- Any change to pricing or billing is blocked by the contract.
03 / The illustrative outcome
Illustrative: delays surface from the data instead of from an angry phone call, and after-hours dispatch no longer depends on someone watching a dashboard.
Model your own process.
Describe it, contract it, simulate it, and watch it run — with humans on the risk.
Start a flow