onfleet: add 28 doc-sourced samples

[garethx]

New provider: Onfleet, the last-mile delivery platform (Hookdeck source type ONFLEET). This is the last stage of the add-a-source pipeline. Before it came the skill (hookdeck/webhook-skills#223), the registry row (hookdeck/webhook-registry#93, plus the citation fix in #95) and the check record (hookdeck/webhook-registry-checks#21).

• Bodies: 28 complete example deliveries, verbatim from docs.onfleet.com/reference/webhook-payload-examples, read from the page's ReadMe .md mirror. Every body is the same flat 8-key envelope (triggerId, triggerName, taskId, workerId, adminId, actionContext, data, time, plus trigger-specific fields like etaSeconds / status). None is elided. In each file, body.triggerName equals the filename and topic.
• Fields that don't apply arrive as null, and the samples keep them. Onfleet: "all other properties not relevant to the trigger may be provided as null". For example, workerDuty has taskId: null and SMSRecipientOptOut has data: {}.
• Each example is joined to the trigger table by triggerId, then checked by triggerName. The fence labels on the examples page are informal (the taskEta block is labelled taskETA), so they aren't used for naming.
• Not included:
  • Trigger 30. The trigger table calls it predictedTaskDelay, but its published example carries "triggerName": "taskPredictedDelay". Both are Onfleet's own docs, and which spelling arrives on the wire is unknown, so neither is exported. The registry records the conflict as a gap.
  • Two taskUpdated variants ("with unavailable photo ids", "with uploaded photo and signature id"). Only the plain taskUpdated example is exported, one body per topic.
  • Trigger IDs 11 and 21 are absent from Onfleet's table, so 29 triggers minus trigger 30 leaves these 28.
• topic_identifier: triggerName, the top-level body field. Onfleet sends it "so you may overload the same url on your application as required". It resolves flat in requestReceiver.ts, so a future capture will be named correctly.
• Headers: only content-type: application/json is synthesized. X-Onfleet-Signature is an HMAC-SHA512 over the raw body keyed with the customer's org secret, so docs can't supply it.
• Version: latest. Onfleet has no webhook version scheme: no version header, and no version field in any body.
• Provenance: latest is sourced_via: docs, sourced_on: 2026-10-16. Each file carries source.type: vendor-documentation and the page URL.

Checklist:

• There's no existing providers/onfleet and no scripts/onfleet harness, so no captures are displaced. Existing files changed: 0.
• Regenerating the registry harvest (harvest_onfleet.py at webhook-registry b0a47d3, current main) into a scratch tree is byte-identical to the committed samples-doc/ and to these files.
• yarn compile passes: 154 → 155 providers, 28 onfleet topics, no collisions.
• yarn test: 14/14 passed.
• Registry verify.py: FAIL (0), 202 providers.

Evidence and non-assertions are in hookdeck/webhook-registry#93. Both registry PRs are already merged, so there is no merge-order dependency.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
webhook-samples	Ready	Preview	Oct 19, 2026 9:15am UTC