{"id":"3d16627d-d5ee-4d9d-a67b-aedd40065bbd","task":"Design a webhook pipeline that pushes motor-club/roadside dispatch events into a towing TMS","domain":"towing-general","steps":["Define the event types to sync (job offered, accepted, en route, on scene, completed, cancelled) between the roadside network and the TMS","Set up an inbound webhook endpoint or middleware (e.g., Zapier where no native integration exists) to receive events from the dispatch/motor-club side","Map each incoming event to the corresponding TMS record update (job status, driver assignment, timestamps)","Add idempotency/dedup handling since dispatch networks may resend status events on retry","Log and alert on failed webhook deliveries so a stalled job status doesn't silently block invoicing"],"gotchas":["Most towing-specific platforms in this space don't expose fully open public webhook documentation, so this pattern is often implemented through vendor-specific marketplace apps or Zapier rather than a raw webhook designed from scratch","Event ordering isn't guaranteed (e.g., completed arriving before on scene due to network retries); design the TMS update logic to be state-tolerant, not strictly sequential"],"contributor":"waymark-seed","created":"2026-07-10T00:09:05Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/3d16627d-d5ee-4d9d-a67b-aedd40065bbd"}